Everything I delegate comes back broken: why, and how to fix it
By Brendan Levin. 15+ years in senior operating roles, including Managing Director of a VC-backed fintech.
Key takeaways
- Broken handoffs are a structure problem, not a talent problem.
- Delegating a task keeps the thinking with you, so the output drifts.
- Delegate the outcome plus a definition of done, plus the decision rights to reach it.
- This is different from the decision-bottleneck problem, and the two compound.
Why does everything I delegate come back broken?
You handed off the task but kept the definition of done in your head. Without the standard and the decision rights to reach it, the person on the other end fills the gaps with guesses, and the output drifts from what you pictured. It is not that they ignored you. It is that the picture of "good" never left your head, so they were working toward a target only you could see. The work comes back broken because it was always going to, the moment you delegated the doing and kept the thinking.
It is not a people problem
The reflex is to conclude the team is not good enough, then to take the work back, which trains them to stop trying. That feels like quality control, but it is the surest way to guarantee the next handoff comes back broken too. The cause is almost always a missing structure around the handoff, not a missing skill. This is operational, not psychological: you fix it by adding the structure around the work, not by coaching the person harder or hiring your way out of it.
The fix: delegate the outcome, not the task
Hand over the result you want, a clear definition of done, and the decision rights to get there, then resist re-specifying it halfway. The hard part is not the handover, it is staying out of it once the person owns it. Every time you reach back in to adjust the spec, you pull the ownership back to your side of the table and the output drifts again. You are transferring ownership, not lending out your hands. This is the Momentum Engine’s Delivery pillar in practice: work that moves through the team instead of through you.
What is a definition of done?
A definition of done is a short, explicit description of what good looks like and how you will both know it is met. It names the result, the standard, and the handful of checks that actually matter, in plain language the person can hold themselves to. It is the single highest-leverage thing you can add to a handoff, and most broken delegation is just its absence: the standard stayed in your head, so the only way to discover it was to get it wrong and bring it back to you.
How is this different from being the bottleneck?
Being the bottleneck is about decision rights: every choice routes to you, so nothing resolves without your ruling. Broken delegation is about ownership and the definition of done: the work routes out but comes back wrong. They are siblings and they compound, because a leader who holds all the decisions usually also holds the standard, so both the choices and the output funnel back through one person. Fix one and the other gets lighter, but each needs its own structural move.
Want to see why the work keeps coming back, and what to hand over differently? The free Executive Momentum Diagnostic maps where your week goes and names your first domino.
Take the free diagnosticCommon questions
Why does everything I delegate come back broken?
Because you handed off the task but kept the definition of done in your head. Without an explicit standard and the decision rights to reach it, the person fills the gaps with guesses, and the output drifts from what you pictured. It feels like the team is not good enough. Almost always it is a missing structure around the handoff, not a missing skill.
How do I delegate when it feels faster to do it myself?
It is faster this time and slower every time after. Doing it yourself trains the team to bring you everything and keeps the thinking with you, so nothing ever comes back finished. The way out is to spend the extra twenty minutes once: hand over the outcome, write a short definition of done, and name the decision rights. That investment is what stops the work routing back.
What is a definition of done?
A short, explicit description of what good looks like and how you will both know it has been met. It names the result, the standard, and the few checks that matter, in plain language. It is the single highest-leverage thing you can add to a handoff, because most broken delegation is simply its absence, the standard living in your head instead of on the page.
How do I stop redoing my team’s work?
Stop handing off the doing and start handing off the outcome. Give the result you want, a definition of done, and the decision rights to get there, then resist re-specifying it halfway. Redoing the work feels like quality control but it is really ownership staying with you. Transfer the ownership and the work comes back finished, not back to your desk.
Is this the same as being a bottleneck?
Related but distinct. Being the bottleneck is about decision rights: every choice routes to you. Broken delegation is about ownership and the definition of done: the work routes out but comes back wrong. They are siblings and they compound, because a leader holding the decisions usually also holds the standard, so both the choices and the output funnel back through one person.