Delegation is the skill leaders most often believe they lack, and the belief usually rests on hard evidence: they handed something off, it came back wrong, they had to redo it, and they quietly concluded it's faster to do it themselves. Repeat that a few times and you get the classic leadership bottleneck — a capable person drowning in work they can't let go of, surrounded by people who could help if only the handoffs worked. But the conclusion is wrong. The problem almost never lives where they think it does.
When delegated work comes back wrong, the instinct is to blame the doing — the person wasn't good enough, didn't try hard enough, missed the point. Occasionally that's true. Far more often, the failure happened before any work started, at the moment of the request. The handoff was vague, so the person did their honest best against a target that was never clearly defined — and produced something reasonable that wasn't what the leader had in their head. The work didn't fail. The request did.
Here's the worked example every leader will recognise. A manager, busy, says to a capable report: “Can you pull together something on our competitor pricing?” The report spends two days building a detailed spreadsheet comparing list prices across the market. The manager wanted a one-page strategic read on where the firm was exposed and what to do about it. Neither person did anything wrong — but the manager now has the evidence that “I can't delegate this,” and the report has learned that delegated work is a guessing game. The actual fault was a request that never specified what “done” looked like, so a competent person filled the gap with the wrong picture.
When delegated work comes back wrong, the failure usually happened before any work started.
A request you can delegate to carries three things the vague version leaves out. It names the conditions of satisfaction — what specifically would count as this being done well (“a one-page summary of our three biggest pricing exposures, with a recommendation”). It names the deadline — a real by-when, not “soon.” And it secures a genuine commitment — the person actually agrees to it, with the room to push back, renegotiate, or say it isn't possible by then. Miss any of the three and you've not delegated; you've gambled.
Notice how much of this is about clarity at the front, not control at the back. Leaders who can't delegate often respond to wrong-output by hovering harder next time — more check-ins, more oversight — which is exhausting and signals distrust and still doesn't fix the root cause. The fix isn't tighter monitoring of the doing. It's a clearer definition of done before the doing starts. Get the request right and you can step back with confidence, because the target is shared; get it wrong and no amount of supervision rescues it.
One more piece completes a clean handoff, and it’s the antidote to hovering: agree the check-in up front, as part of the request, rather than dropping in unannounced whenever anxiety strikes. “Let’s catch up Thursday on where it’s heading” is a planned waypoint both people signed up to; it supports the work without signalling distrust. Compare that to the leader who, having handed something off, then messages twice a day for updates — that’s not delegation, it’s supervision with extra steps, and it teaches the person that they don’t really own the work after all. A single agreed checkpoint gives you the visibility you need and the person the autonomy they need, which is the whole point of delegating in the first place. The difference people experience as trust isn’t the absence of check-ins; it’s whether the check-in was agreed or sprung on them.
The leader who masters the handoff escapes the bottleneck that caps so many careers. Their team does more, and does it right the first time, because people aren't guessing at what was wanted. Crucially, those people also grow — a clear request with a real commitment is something a person can own and be accountable for, which is how delegation develops people rather than just offloading tasks. The leader who never cracks this stays the bottleneck, doing work three levels below them, telling themselves they're surrounded by people who can't be trusted with anything important — when what's actually true is that they've never handed anything over clearly enough to be done well.
So if delegation keeps failing, stop looking at the people doing the work and look at the moment you hand it over. Were the conditions of satisfaction explicit? Was there a real deadline? Did the person actually commit, freely? Fix the request, and most of what you'd written off as “I can't delegate” quietly resolves itself.