When You’re the Bottleneck: Why Delegation Isn’t a Skills Problem
A leader I worked with had built a function the company admired. Strong team, low attrition, work that consistently landed. By every external measure, he was doing it right. But everything moved through him. Every decision routed back to his desk. Drafts came in and left rewritten in his hand. His calendar had become a series of approvals.
He knew the language for this — hire well, set expectations, let go, trust the team. He had hired well. He did trust them. And still, when the work reached him, he could not put it down.
This pattern gets misdiagnosed constantly. It is treated as a time problem, a delegation-skills problem, sometimes a trust problem. It is usually none of those. Underneath sits a belief — that his worth depends on personally delivering — and that belief has become load-bearing in how he sees himself. That is why it does not yield to technique. It is not a habit you can manage around. It built his career before it began to cap him.
What delegation actually asks
Ask him to hand over the work and a quieter question surfaces: if I give this away, what am I supposed to do? How do I deliver value?
It sounds like resistance. It is not. At this level, when you stop producing the work yourself, it genuinely is unclear what your value is — and no one tells you. He is not clinging out of ego. He is looking at the space where his old source of worth used to be and finding nothing obvious in it. “Trust your team” does not touch the question he is actually asking.
That is why every framework — RACI charts, decision rights, clearer role definitions — helps only at the margins. None of it answers the question. The work he will not release is doing something for him: it is the last place his value still feels certain.
The tell
There is a behaviour that gives this away. He delegates, sincerely. Then, somewhere in the middle, he reaches back in. Rewrites the document. Joins the call he had handed off. Takes the escalation himself.
Each instance has a reasonable explanation. This one was too important; that client is sensitive; the timing was tight. But the pattern is the explanation. When a leader keeps reclaiming the work he meant to release, the work is steadying him — and reclaiming it is how he avoids the exposure of being responsible for outcomes he no longer controls.
This is where it stops being sustainable. The job grows too large for one pair of hands. Leaders who cannot make the shift do not fail loudly. They plateau, the organisation slows to their personal throughput, and their best people, underused, start to look elsewhere.
What has to move
The work is not talking him out of the question. It is helping him find the new answer: that his value has moved — to judgment, to sequencing, to the people he grows, to the calls only he can make. And then sitting with the harder part. For a long time, that will not feel like delivering value. It will feel like doing nothing. The gap between where his value has actually moved and where it still feels located is the real terrain.
This is what coaching reaches that better systems cannot. Not a sharper method — a belief made visible enough to question. For the leader I worked with, the change was quiet. He did not become hands-off. He could feel the pull to reclaim a piece of work and recognise it before acting on it. That recognition created a gap, and in the gap he could choose. Over time the function stopped depending on his presence in every decision, and his best people grew into the room he had finally left for them.
If you recognise yourself here
If you are the bottleneck in your own function and the usual advice has not moved it, the question worth sitting with is not how to delegate better. It is what the work is still doing for you — and where your value has actually gone. Get in touch for a direct conversation about it.
