Delegating Tasks: Why the Work Keeps Coming Back, and the Handover That Stops It

You gave the Acme report to Sam, one of your four reports, three weeks ago. Since then Sam has asked you which quarter's numbers to use, whether the churn slide belongs in it, whether it goes out Tuesday or Thursday, and whether it is fine to pull Riley in for the charts. You answered each one in under a minute, and felt like a responsive manager doing it.

The report is still yours. It has Sam's name on it and your judgment inside it. That is what delegating tasks looks like when the work moves and the decisions stay behind.

One sentence at the handover caused all of it.

The sentence that caused this was said at handover, and it sounded generous. "Just check with me before anything goes out." Or the softer version: "Let me know if you have any questions." Both hand over the work and keep the judgment. What comes back is not the work. It is a queue.

Delegating tasks is a conversation problem. Here is what the handover has to contain, and what to say the fourth time someone brings you a decision they could have made.

Why does the work keep coming back to you?

A piece of work is never one thing. It is a task plus fifteen small judgment calls: which number, which format, who else to involve, what to do when something you assumed turns out to be false. If all fifteen route through you, you have not delegated the work. You have delegated the typing and kept the job.

There is a quick test. Write down the work, list the decisions it actually contains, and put a name next to each one. If your name is next to more than two, you already know why it keeps coming back.

The cost never shows up on your calendar. It shows up as a day that was busy while nothing you own moved.

The other person notices before you do. Once a couple of their calls get corrected, forming an opinion looks expensive and asking looks free. So they ask. That is how you end up describing someone as needing a lot of hand-holding, when you built the hand-holding into the handover.

If your own plate is full of work handed down to you, delegating better will not fix that by itself. Saying no to your boss is the other half of the same skill.

Delegate the outcome, not the steps

A handover that holds has three parts. What done looks like. The constraints, meaning the short list of things that are not up for grabs. And which decisions are now theirs. The third part is the one almost everybody skips, and it is the one doing the work.

If you cannot say what done looks like in one sentence, you are not ready to hand the work over. The round trips you are about to have are not evidence that the person is not ready. They are you outsourcing a decision you had not made yet.

Name the level of authority out loud

Most of the friction in delegating tasks comes from a question neither person asks: how much authority came with this. You assume it was obvious. They assume checking is the safe move. So they check, you get quietly annoyed at being checked with, and nobody says the thing.

There are three levels. Naming which one applies takes four seconds.

Decide it and tell me after. They act, you find out when it is done. This is the right level for most work and almost never the default, which is the whole problem.

Decide it, but check with me before it goes out. They do the thinking and reach a conclusion. You see it once, before it becomes public or expensive. Use this when the audience is external, or the person is new to this kind of call.

Bring me two options and a recommendation. You keep the decision. Use it when the call is genuinely yours: money above a line, anything that affects someone's job, anything you cannot walk back. Notice the shape even here: they arrive with a recommendation, not with the question.

Levels attach to the decision, not to the person. Sam might be at the first level on anything client-facing and the third on pricing. Say which one you mean at handover, and say it again when a new kind of decision shows up. "That one is yours, you do not need me for it" is a complete sentence.

The boomerang moment

This is where delegation is won or lost. Someone is at your desk with a question they could answer. Reverse delegation almost never arrives as a request to give the task back. It arrives as "quick question" four times a week, each one small enough to answer.

That last line is the one that changes anything. Without it you have answered one question well. With it you have moved a whole category off your desk.

The hand-back fails in one specific way. "Figure it out" is not this. That is abandonment with a management vocabulary on it. The difference is that you stay in the conversation. You give the missing information, the constraint, the context only you have. You just do not give the decision.

Checkpoints instead of hovering

Managers tend to think the choice is between hovering and being surprised at the end. It is not. It is between visibility you scheduled and anxiety you did not.

Put the checkpoints in at handover. Two is usually right on a three-week piece: one early enough that direction can still change, one before anything goes out. Say what you will look at each time. Between those dates, do not ask. If you cannot stand not asking, your checkpoints are in the wrong place.

The checkpoint belongs in the one-on-one you already have, and the question is not "how's it going." That gets you a status update. Ask what they have decided since you last talked, what they are stuck on, and what they need from you by name. The questions worth asking in a one-on-one do more for delegation than any tracking system.

Let it be done differently from how you would do it

Different is the price of delegation, and most of the time different is just different. The line has three parts: the outcome you agreed on, the constraints you named, and whether a wrong call can be reversed cheaply. If it lands the outcome, respects the constraints, and any mistake can be undone in a day, it goes, even when the structure is not the one you had in your head.

When you do step in, say which of the three you are stepping in on. "That is the churn slide, and the churn slide was a constraint" is a reason. "I would have done it differently" is taste, and taste applied late is what kills ownership.

The one time you took it back

Delegation usually dies in one moment. The night before the deadline you pulled the deck back, rewrote it, and sent it yourself. You told yourself it was a one-off, and you probably never mentioned it again.

They learned something exact from that. Ownership here is on loan, and it can be recalled at the last minute with no warning. The rational response is to check everything with you, early and often. So the next handover produces more boomerangs, not fewer, and from where you sit it looks like the person got less capable.

The repair is to name it once, out loud.

If the work genuinely was not good enough, that is a different conversation, and it belongs on the calendar with evidence, not in a silent rewrite at eleven at night. The underperformance conversation is its own job.

This does not work if the person cannot yet make the call you are handing over. Delegating a decision to someone who has never seen it go wrong is not delegation, it is a coin flip with your name on it. The fix is not to take the decision back: it is to say which call is theirs this month and which one is yours until they have watched you make it twice.

Saying it is not the same as reading it

The hand-back is four words. "What would you do?" On the page it looks like nothing. At 5:40 on a Thursday, with someone at your desk and the answer already in your head, four seconds of being helpful beats it almost every time.

That is what makes delegating tasks a practiced skill rather than a known one. You already know you should not answer. Knowing does not survive mild time pressure and the pull of being useful. What survives is having said "what would you do" out loud enough times, to someone who pushes back with "you know this way better than I do," that it comes out flat and friendly instead of like a test.

The handover is the same. Read it and it is obvious. Say it with a person you like waiting for you to finish, and you will hear yourself add "but obviously just check with me if anything comes up." Handed over the work, kept the decision, one more time.