Bottleneck

What efficient leaders accidentally create

Your team is waiting on you again.

Not for something they can’t do.
For something they could do — if you let them find out.

You tell yourself it’s a small thing.

One decision, this week, that stayed with you instead of moving to them. It felt efficient. Faster than explaining, faster than watching them get it half-right first.

It’s never one decision, though. It’s a pattern you don’t see because each instance looks reasonable on its own.

Here’s what it costs, month by month, if you don’t resolve it.

Month one, the work travels fast — because you’re still deciding almost everything, and you’re quick. It looks like efficiency.

Month three, something shifts. Your people stop bringing you their best ideas or resolutions because they don’t know what would work and what wouldn’t. Something always seems to be missing.

Month six, you’re in a room, and someone says, “What do you think we should do next?” — something they were fully capable of knowing what’s next on their own.

You feel a flicker of frustration — “why can’t they share the next best move” — and you don’t yet see that you trained them to seek. Every next step you gave took them further away from figuring it out.

This is the part that’s hard to sit with: the muscle you’re strengthening every time you resolve something quickly isn’t team ownership; it’s your own certainty.

By month twelve, you’ve built a team that executes well, while you burn the midnight candle to clear the bottleneck.

None of this happened because you did not trust them. It happened because letting them be slow, and sometimes wrong, felt like a cost you weren’t willing to pay.

This shows up most strongly in leaders who’ve built their whole careers on being the one who gets it right — the ambitious, the hyper-achievers, the perfectionists. For them, it was never about trust. It was about letting go.

What would it cost you to let go intentionally, just once, and watch them get it wrong?