Topic
Delegation: How to Hand Over Work So It Actually Holds
Effective delegation means handing over an outcome — not just a task — with a clear standard, sensible constraints and the right check-ins, so the work comes back finished rather than bouncing back to you. Done well, it raises a team's capacity and lowers the manager's role as bottleneck.
2 guides in this topic
Delegation is the highest-leverage skill a growing manager has, and the one most often done badly. Hand over too little and you become the bottleneck every decision routes through. Hand over carelessly and the work bounces straight back to you, half-done and late.
The difference between delegation that holds and delegation that doesn't is rarely effort — it is clarity. The person taking the work needs to know the outcome they own, the standard it must meet, the constraints they must respect, and when you will check in. Get those right and you can step back without the work drifting.
Why managers under-delegate
The instinct to keep work is understandable. It feels faster to do it yourself, the standard feels safer in your own hands, and handing over badly once teaches you that delegation "doesn't work here." So decisions concentrate. Gallup's research on management has repeatedly found that managers account for the large majority of the variance in team engagement, and one of the clearest ways a manager drags that number down is by becoming the person every choice waits on. The cost is rarely a single missed deadline; it is a ceiling on how much the whole team can carry.
"If the work cannot move without you in the room, you do not have a team — you have a queue." — The Control Standard
Delegation that holds vs delegation that bounces
Good delegation transfers judgement, not just hands. That is the difference between handing over a task and handing over an outcome: a task tells someone what to do; an outcome makes them responsible for whether it actually works. When you transfer the result, four things have to travel with it — the outcome, the standard, the constraints, and the check-ins. Drop any one and the work tends to come back.
The failure mode at the other end of the scale is keeping too much, until you are the bottleneck the team waits on. That is usually a structural problem, not a personality one: no shared standard, no clear decision rights, no agreed check-ins. The fix is to stop routing work and start leading it, and to apply the coaching test before you take a decision back — asking whether you are building the person's judgement or quietly replacing it.
Where to start
These guides cover how to delegate outcomes rather than tasks and how to stop being the bottleneck your team waits on. If you want a quick read on where work is currently routing through you, the free Drift Report is a five-minute place to start.
Guides in this topic
How to Delegate Outcomes, Not Just Tasks
To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.
GuideHow to Stop Being the Bottleneck Your Team Waits On
You become the bottleneck when too many decisions and too much context route through you alone. The way out is to make your expectations predictable, push decision rights down with clear guardrails, and let people act from their remit rather than waiting for instruction — so work moves when you're not in the room.
Related
How to Delegate Outcomes, Not Just Tasks
To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.
GuideHow to Stop Being the Bottleneck Your Team Waits On
You become the bottleneck when too many decisions and too much context route through you alone. The way out is to make your expectations predictable, push decision rights down with clear guardrails, and let people act from their remit rather than waiting for instruction — so work moves when you're not in the room.
TermBus Factor
The bus factor is the number of people who would have to be lost — "hit by a bus" — before a project stalls because critical knowledge or access went with them. A bus factor of one means a single person is a single point of failure. Raising it is a core goal of good ownership and delegation.
TermRouting vs Leading
Routing vs leading is the distinction between processing your team's work one item at a time — answering questions, making small decisions, unblocking people — and acting on the system that produces that work: its standards, decision rights, and handoffs. Routing feels productive; only leading compounds.
TermThe Coaching Test
The coaching test is a single question for telling coaching apart from rescuing: after being coached, does the person perform better when you are not in the room? If yes, it was coaching. If the problem got solved but the person is no more capable, it was useful — but not coaching.