Early in my career, I ran every decision through myself first. Every ticket, every architecture call, every "should we ship today or wait." I told myself it was diligence. It wasn't. It was fear wearing a lanyard.
I had a junior engineer on my team who kept coming to me with the same question dressed in different clothes: "What do you think we should do here?" And every time, I told him. Fast, confident, done. I felt useful. He felt smaller. Neither of us noticed the pattern until a senior colleague pointed it out: "You're training him to need you. You think you're helping. You're not."
It stung because it was accurate.
The Habit Nobody Names
Most leaders don't decide to hoard decisions. It happens one small rescue at a time. Someone hesitates, you fill the silence with an answer, and the team learns the fastest path to a decision runs through your desk. Do this for a year and you've built an org chart with one working brain and forty sets of hands.
Roland Butcher, the former England and West Indies cricketer turned coach, put it plainly when talking about developing young players: making juniors decide develops leaders faster than any training course. Not "helps." Faster. He wasn't talking about software teams, but the mechanism is identical. Skill grows at the point of decision, not at the point of instruction. A player told what to do learns obedience. A player forced to choose, under real stakes, learns judgment.
Software teams work the same way. Nobody develops technical judgment by reading a runbook someone else wrote for them. They develop it by making the call, watching what happens, and carrying this memory into the next call.
What the Research Shows
I went looking for numbers because a good story isn't proof of anything by itself.
A Wharton Executive Education analysis cites a study of more than 7,000 employees: workers who felt a low level of empowerment sat at the 24th percentile of engagement. Workers who felt genuinely empowered sat at the 79th percentile. Not a small gap. The difference between a team showing up and a team showing up early.
The same piece references Zenger Folkman research showing only 4% of employees are willing to increase effort when empowerment is low, against 67% when it's high. Sixty-three points of discretionary effort, sitting on the table, unclaimed, because a leader wouldn't let go of the steering wheel.
I read this figure twice. Sixty-three points. The entire margin between a mediocre team and a team people fight to get onto.
The same analysis cites Gallup research showing businesses with highly engaged teams outperform peers by nearly 150% in earnings per share. Leaders who hoard decisions aren't running a tight ship. They're running a slower one, and paying for it in a currency nobody puts on the org chart.
Handing Over the Keys, Not the Advice
Here's where most delegation guidance goes soft. Leaders say "empower your team" and then keep every decision carrying real risk. Real handover means giving someone a decision where the outcome touches a customer, a deadline, or money, then staying quiet while they make it.
Uncomfortable on purpose. If it were comfortable, it wouldn't be a real handover. You'd be delegating the decisions you didn't want anyway.
I started doing this deliberately a few years back. Instead of answering "what do you think," I started answering with "what do you want to do, and why." First few times, my engineer looked at me like I'd stopped doing my job. In a sense I had. My job wasn't to hold every answer anymore. It was to hold the space where someone else's answer would grow.
Letting Them Fail Is the Point, Not the Risk
The part everyone skips over: sometimes the decision goes wrong. The junior calls it, and it doesn't hold up. Here's where a leader's nerve gets tested, not their generosity.
Garry Ridge, the longtime CEO who built WD-40's culture around what he calls "learning moments" instead of failures, has spent years making the case: reframing the language changes the behavior. Call it a failure and people hide it. Call it a learning moment and people bring it to you the next morning, already halfway to the fix.
I've watched a mistake handled two different ways on two different teams. On one, the leader asked "who approved this?" On the other, the leader asked "what did we learn, and what do we change?" Only one of those teams kept making decisions after this. The other one went quiet, and quiet teams stop growing leaders. They stop growing, period.
It Isn't Only a Work Habit
I noticed the same pattern at home before I noticed it at work, if I'm honest with myself. Watching my grandson wrestle with a decision, a puzzle, a choice about which way to build something, I'd catch myself stepping in with the answer before he'd even asked for it. Faster for me. Cheaper for him, in the one way it truly counts. Every time I did it, I handed him a solved problem instead of a solvable one.
Kids and junior engineers aren't the same, but the mechanism holding both back is identical: an adult in the room unwilling to tolerate watching someone else struggle for thirty extra seconds. Struggle isn't the enemy. Rescue too early is. I've had to catch myself with my grandson the same way I caught myself with this engineer, biting back the answer long enough to ask "what do you think you should try?"
The Real Cost of Hoarding
Keep every decision and you're not protecting the outcome. You're protecting your own comfort at the outcome's expense. And you're quietly telling your best people their judgment doesn't count until it matches yours, a strange message to send someone you hired for their judgment in the first place.
I think about this engineer often. He's a lead now, at a different company, making decisions nobody runs past anyone. I'd like to say I saw this coming the day my colleague called me out. I didn't. I stopped answering so fast, and space opened up where his judgment used to have nowhere to go.
Where to Start Monday Morning
No program required here. One decision this week you'd normally make, handed to someone else instead, with the outcome genuinely uncertain. Then sit with your hands still while they make it.
If it goes well, say so plainly and move to the next one. If it goes sideways, ask what they learned before you ask what went wrong. The order of those two questions tells your team everything about whether decisions are safe to make around you.
Whose decision are you still making which shouldn't be yours anymore?