A leader delegates a piece of work. Two weeks later they are back inside it. They rewrote the deck, they joined the call they were not needed on, they answered the client directly because it was faster. The stated reason is almost always the same: the quality was not there yet, and the timing did not allow for a learning curve.

Sometimes that is accurate. Often it describes the symptom rather than the cause.

What tends to have happened is that the task moved and the responsibility did not. The person received the work but not the authority to be wrong about it. And a piece of work you are not allowed to be wrong about has not really been delegated. It has been lent out, on the condition that it comes back in the shape the leader would have produced.

The task and the accountability are not the same thing

Handing over the task is administratively simple. You explain what needs doing, agree a deadline, share the context.

Handing over the accountability is a different act. It means that when something goes badly, the other person is the one who noticed, the one who decided what to do, and the one who has to explain it. The leader finds out afterwards, and lives with a version of the outcome they did not personally control.

Most delegation failures happen in the gap between the two. The leader hands over the task, keeps the accountability, and then experiences a slow accumulation of anxiety that resolves itself the only way it can, by taking the work back.

The team reads this accurately, and adjusts. They stop making calls and start bringing options. They pre-check. They send the draft early “just to be safe”. Within a few months the leader has more escalations, not fewer, and concludes that the team is not ready for more responsibility. The team, meanwhile, has learned that ownership here is provisional and that being wrong is expensive.

Why intelligent leaders keep doing it

Rarely because they think they are the only competent person in the room. The reasons that come up are more specific.

The outcome is still attributed to them. In most structures it genuinely is. The leader is accountable upwards for a result they are being asked to stop controlling. That is not paranoia. Anyone who has been held responsible for something they did not touch understands the pull.

The standard is unarticulated. The leader knows what good looks like but has never had to describe it, because they have always produced it themselves. What comes back is different, and different reads as worse. Some of it genuinely is worse. Some of it is just not theirs.

The work is load bearing for identity. Being the person who can handle the difficult account, the hard slide, the sensitive conversation, is often what got the leader here. Handing that over is not a workflow change. It is giving up the part of the job that reliably confirms they are good at it.

Reclaiming feels like support. Stepping in reads internally as helping. It reads externally as a verdict.

The point where it becomes visible

Watch what happens after a mistake. That is where the real arrangement shows.

If a delegated piece of work goes wrong and the leader takes it back permanently, everyone now knows the terms: you own this until it is difficult. If it goes wrong and the leader stays out, asks what the person is going to do, and lets them do it, the delegation was real. This single moment teaches the team more than any amount of stated empowerment.

Which is why the useful preparation is not “how do I delegate better”. It is deciding, before anything goes wrong, what level of failure you are willing to absorb without reclaiming. Not in principle. Specifically. A missed deadline, yes. A client seeing a weaker version, probably. A visible error in front of the board, no. Once that line exists, the leader can stop monitoring for quality and start monitoring for the line, which is a far smaller job and a far less corrosive one.

Worth sitting with

  • When you took that work back, what were you protecting: the outcome, the client, or your own standing?
  • What is the largest mistake you could absorb without reclaiming the work? Say the actual number or the actual event.
  • Does your team know where that line is, or are they guessing?
  • If you never took another piece of delegated work back, what would you have to change about how you are held accountable?

The uncomfortable version of the question is this. If the work came back done differently from how you would have done it, but the result was fine, would you be able to leave it alone? Many leaders discover that the answer is no, and that the issue was never capability in the team.