Why you keep taking the work back

You handed it over. It came back at seventy percent of what you needed. You fixed the rest yourself on a Thursday night, and you told yourself that was quicker than another round of edits.

It probably was, that week. Do it for a year and you have built something you cannot get out of.

Most leaders describe this as a time problem. It almost never is.

The arithmetic is not what is stopping you

You already know the sums. Explaining a task costs more than doing it, the first time. By the fourth time it costs nothing at all. Anyone who has run a team for a year has worked this out.

So if time were the obstacle, you would have solved it by now. You solve harder scheduling problems than this most weeks. Why has this one held out?

Because handing work over means the outcome depends on judgement you cannot see from the inside. If it goes badly, it goes badly with your name on it.

What you are actually protecting

What are you afraid will happen if you let this one go? The honest answer is usually undramatic.

Often it is that the work will come back adequate rather than good, and someone whose opinion matters to you will see it. Sometimes it is that a relationship you built slowly will get handled quickly by someone who did not build it.

And sometimes it is more personal than that. Being the one who gets this right is part of how you understand yourself. That is very common in people who were promoted for being excellent at the work, and it does not go away just because your title changed.

How it reads from the other side

You experience taking the work back as a rescue. Nobody on the receiving end experiences it that way. Have you ever asked one of them how it landed?

What they see is that something was given to them, then quietly removed and repaired. Often no one tells them what was wrong with it. What they take from that is simple enough: they are trusted with the doing, not the deciding.

Capable people adjust to that fast. They stop stretching. They start checking with you before making calls they are perfectly able to make, because checking is cheaper than being corrected.

Then you look at your team and conclude they lack initiative. Which is the evidence you were afraid of finding, and you helped produce it.

Hand over the decision, not just the task

The practical shift is smaller than it sounds. Most of us delegate the task and keep the decision. Try it the other way round.

Say what good looks like before the work starts, in enough detail that they could judge it themselves. Disappointing delegated work is usually disappointing because the standard lived in your head and nowhere else.

Then say what you will check, and when. Two checkpoints agreed at the start feel like support. The same two arriving unannounced feel like surveillance.

And be specific about the edges of the decision. What can they spend, who can they commit, what has to come back to you? Vagueness here is not generosity. It leaves people to find the line by crossing it.

Something has to be allowed to go wrong

None of that works unless you let something fail.

Not something catastrophic. You get to choose the ground. Pick a piece of work with a real consequence, small enough that you can absorb it, visible enough that they learn from it. Then keep your hands off it.

People do not build judgement by watching yours. They build it by making a call, living with what follows, and being asked afterwards what they would do differently. Intercept every mistake and you are not protecting anyone. You are keeping them junior.

So try one question this week. What is on your plate because it genuinely needs you, and what is there because handing it over would mean sitting with the risk of it coming back imperfect?

The second list is usually longer than we expect. Take one thing off it and leave it alone for a month.