August 26, 2026
Delegation Isn't Tested at the Handoff
Someone gets stuck on work you handed them. They come to your desk and say some version of: I'm not sure how to handle this.
What you do in the next ten seconds decides whether you delegated anything at all.
The easy move is to take it back. You know the answer. They're blocked. Solving it yourself takes four minutes and solves the immediate problem. Almost every manager does this, and most never notice it as a decision, because it doesn't feel like one. It feels like being helpful.
It has a name: reverse delegation. And it's where most delegation quietly dies.
What taking it back actually costs
The obvious cost is your time, which you were trying to save. That's the smaller half.
The real cost is that you've taught something. The lesson is that getting stuck is a reliable way to hand work back. Nobody articulates it, and the person almost certainly isn't being manipulative, but the pattern gets learned anyway. Do it enough times and your team brings you their problems instead of their progress, which is precisely the situation you were delegating to escape.
There's a second-order effect worth naming. Once someone learns that stuck work returns to you, the threshold for "stuck" drops. It has to. Why spend two hours struggling if forty minutes gets it escalated?
The alternative, which is slower once
Coach instead of solving. Concretely, that means two questions before you offer anything:
What have you already tried? And what do you think the next step is?
Ask both, then wait. The waiting is the hard part, because the silence is uncomfortable and you already have the answer sitting in your mouth. Most of the time the person knows more than they're giving themselves credit for, and your job is to make them say it out loud rather than say it for them.
Sometimes they genuinely don't know, and then you teach. That's fine. That's different from doing it for them, and it stays different as long as they're the one who ends up doing the work.
The part that comes before
Reverse delegation is often the visible symptom of something that went wrong earlier.
Delegation done properly has three parts moving together. Responsibility is the assignment and its intended outcome. Authority is the actual power to act and decide, with real boundaries like budget. Accountability means the person genuinely answers for how it turns out.
Hand over responsibility without authority and people get stuck constantly, not through incompetence but because they keep hitting decisions they aren't permitted to make. Then they come back to you, and it looks like reverse delegation when it's really a design flaw in the handoff.
So when someone returns stuck, it's worth asking yourself before you answer: is this person missing knowledge, or are they missing permission? Those need opposite responses, and confusing them is expensive in both directions.
Why managers avoid all of this
The stated reasons are familiar. It takes too long to explain. My people aren't ready. It's faster to do it myself.
Underneath, the honest versions are usually different. What if they mess it up and I'm still accountable? If someone else can do my job, do I still matter? Research on this is fairly blunt: the biggest barrier to delegation is almost always the manager, not the team. That's worth sitting with before concluding your team isn't ready.
Delegation was never really tested at the handoff. It's tested the first time someone gets stuck, and you find out then what you actually handed over.
This comes from the Delegation session of the curriculum I teach. The full lesson covers what delegation isn't (participation, task assignment, dumping, abdication), how to structure the handoff conversation, and the pitfalls worth naming in advance: Delegation.