Years ago I handed a team the rebuild of a billing service. Big project. Real money riding on it. I stood in front of them and said the words every leadership book had trained me to say.
"You own this. I trust you. Come find me if you need me."
Then I walked away and felt good about myself. Felt modern. Felt like the kind of leader people write case studies about.
Four months later the project was late, the team was cooked, and two of my best engineers had refreshed their profiles. I had handed them autonomy. What they received was a locked room with the lights off.
The Room With No Lights
Here is the part I got wrong, and I got it wrong for years.
I thought empowerment was a decision. Make the call, say the words, step back. Done. One conversation and the org chart rearranges itself around trust.
Empowerment is not a decision. It is infrastructure. It is the boring, unglamorous work of building the conditions where someone else's judgment has a chance of being right.
I skipped all of it. I gave them the outcome and none of the scaffolding. When they hit their first real fork in the road, they had no way to know which branch I would have taken, and no safe way to ask. So they guessed. Then they guessed again. By the time the guesses compounded into a missed date, the story inside the team was simple and brutal: we were set up to fail.
They were right.
Autonomy Comes With Strings Nobody Writes Down
John Cutler nailed this in a piece on empowerment and delivery. Most tech companies run a hybrid. The language is team independence. The mechanics are a manager acting as gatekeeper, filter and escalation valve.
His framing of the unwritten bargain has stuck with me:
"We'll grant your team autonomy, but you, the manager, are responsible for ensuring that autonomy doesn't create chaos, need escalation, or disrupt executive focus."
Read the translations he lists, because I have said all three out loud:
- "You're empowered. But if things go sideways, it's on you."
- "You should take initiative. But don't challenge the strategy."
- "We trust the team, as long as you don't cause problems upstream."
Cutler points out where the language came from. Mission command, borrowed from the military. Militaries do decentralize execution... and they also invest enormous effort in clarity of intent, shared context, trust, and the ability to escalate without penalty. They run drills for the moment comms drop and the plan stops matching the ground.
I served. I remember the briefings. Nobody ever said "you own this" and walked out of the room.
Tech took the vocabulary and left the training behind.
What I Skipped
Four things. Every one of them is work I was too busy to do, and every one is cheaper than a failed rebuild.
Context
Not the goal. The reasoning underneath the goal. Why this project matters more than the other seven. Which customer conversations drove it. What the CFO believes about the number. Which constraints are physics and which are preference.
A team with the outcome and no reasoning will optimize for the outcome as stated. A team with the reasoning will notice when the stated outcome stops making sense... and tell you.
Boundaries
Autonomy with no edges is not freedom. It is fog.
Say the edges out loud. This budget. This deadline. These three decisions come to me, and here is why. Everything else is yours, and I will not second-guess it after the fact.
Engineers do not resent boundaries. They resent invisible ones... the sort you find by crossing them.
Air Cover
The first time an executive leans on your empowered team, everyone learns whether the empowerment was real. If you fold, the autonomy evaporates in one meeting and no speech gets it back.
Air cover is the price of the words. Pay it in public.
A Way to Escalate Without Bleeding
My billing team hit a data-model decision worth a month of rework. They sat on it for three weeks.
Why? Because I had made asking expensive. I had framed ownership as a test. Coming back with a question meant admitting they were not up to the thing I had publicly trusted them with.
Cutler lists the sanctioned channels for dissent in most companies: the twice-a-year engagement survey, the all-hands Q&A, a Slido board, or taking a real risk to reach a skip level. None of those work at the speed of a Tuesday afternoon architecture decision.
If raising a hand costs status, nobody raises a hand. The information you need most stops moving toward you.
The Numbers Behind the Feeling
Gallup's global engagement data puts US engagement at 31% and the global figure at 20%. Same research finds managers account for at least 70% of the variance in team engagement.
Seventy percent. The manager is the weather.
My own survey research found 99.5% of respondents had experienced one or more types of bad boss. I write about the patterns over at Step It Up HR. Almost none of those bosses thought of themselves as the problem. Plenty of them believed they were the empowering kind... the hands-off kind, the trusting kind.
Hands-off and empowering are not the same word. One is a gift. The other is an absence.
We Brief Our AI Agents Better Than Our People
Watch a good engineer set up an AI coding agent this year. They write a spec. They define the boundaries of the repo it is allowed to touch. They give it the context files, the conventions, the tests. They build a review loop. They set a budget and a stopping condition.
Now watch the same engineer's manager assign a quarter of work to a human being. "You own this. I trust you."
The 2025 DORA research landed on a finding worth sitting with: AI works as an amplifier, magnifying an organization's existing strengths and weaknesses. The returns come from the underlying system, not the tools.
Delegation behaves the same way. Hand real ownership to a team with context, boundaries and air cover, and you get leverage no headcount plan matches. Hand the same ownership to a team without those things, and you amplify confusion at speed.
The engineers already know how to specify work well. They do it for machines every day. The gap is nobody applies the same rigor to the humans.
Four Questions Before You Say The Words
Before you tell anyone they own something, answer these. Out loud, to them.
- What does good look like, and who decides? If the answer lives only in your head, you have not delegated. You have set a scavenger hunt.
- Which decisions are theirs, and which are mine? Name the second list. Keep it short and keep it honest.
- What happens when they get it wrong? Say it before it happens. Everybody assumes the worst answer by default.
- How does a hard question reach me in under an hour, at zero cost to their standing? If your answer is "my door is always open"... you do not have an answer.
Get through those four and step back. Now stepping back means something.
Empowerment Is Work, Not a Speech
The billing rebuild shipped eventually. I sat down with the two engineers who were halfway out the door and asked what I had done to them. One of them said something I have carried for a decade.
"You didn't give us the project. You gave us the blame for it in advance."
I had spent four months proud of my restraint. From where they sat, restraint looked like abandonment with better branding.
Trust is not the absence of involvement. It is a different kind of involvement... front-loaded, deliberate, and mostly invisible once it works.
So look at whatever you handed off last quarter. Did you build the room before you handed over the keys, or did you hand someone a dark room and call it freedom?
One of those gets you a team. The other gets you a resignation with a painfully polite subject line.