By Andreas Pettersson, Founder, Leaders ADAPT
You handed it off on Monday. On Thursday it's back on your desk, wearing a question. "Can you take a quick look before I send it?"
You look. You fix two things. You send it yourself. The task came back, and nobody called it that.
That's reverse delegation: a delegated task returning to the manager who assigned it. The cause is the handoff, not the employee. In the Delegation Protocol I teach, you delegated a task when you meant an outcome, and you skipped the one check-in that keeps work from boomeranging, the 25% Rule. Here's why the task came back and the six sentences that send it home.
Quick answer: Reverse delegation happens when a task assigned to an employee returns to the manager, usually as a question, a review request, or a decision the manager ends up making. It is prevented by delegating an outcome rather than a task, stating the authority level out loud, and scheduling one check-in when the work is about 25 percent complete.
What is reverse delegation?
Reverse delegation is the return of a delegated task to the manager who assigned it, so that the manager, not the employee, ends up doing the thinking, the deciding, or the work.
The idea has an older name: in "Management Time: Who's Got the Monkey?" (Harvard Business Review, 1974), William Oncken Jr. and Donald Wass described every problem an employee hands back as a monkey that jumps from their back onto yours. Upward delegation is the same thing seen from the org chart.
It rarely arrives as "I'm giving this back." It arrives as a review request, a decision in disguise, or a quick sync where they leave with your answer. Each moves the monkey.
Why does delegated work come back to the manager?
Every page on this topic says reverse delegation is bad. Almost none asks why, and the honest answer sits on the leader's side of the desk. Four causes.
You delegated a task, not an outcome
The root cause. Compare "Send the monthly report to the board" with "Make sure the board has complete visibility into our performance and feels confident about our trajectory." The first has one right way to do it, yours. The second has many, and they pick.
When you delegate tasks, people remain waiters taking your order. When you delegate outcomes, they become owners building something. Waiters bring the order back for confirmation. Owners don't.
You skipped the first three letters of SCQA
Situation, Complication, Question, Answer. Most leaders jump straight to the Answer: "We need to improve onboarding, can you take a look?" Without the Situation (30 percent of new hires leave inside sixty days) and the Complication (exit interviews point at week one), the person can't make one judgment call alone. So every judgment call walks back to you. The task vs outcome problem and the missing context problem are one problem.
You never named the authority level or the check-in date
Ambiguous authority kills ownership. If they don't know whether they can decide and tell you after, decide and tell you before, or only recommend, they'll pick the safest option: asking you. With no check-in on the calendar, the only check-in available is you, whenever.
That's not a process. That's an open door with your name on it. Decision rights get said out loud, and the decision rights ladder is how I make them explicit.
You solved it in the 1:1
The status update 1:1 is where most reverse delegation actually happens. They bring the problem, you fix it in ninety seconds because you can, and they leave with your answer. You trained them. If your one-on-one meetings feel like a queue of decisions, that queue is the symptom.
I learned this the expensive way. Somewhere between thirty and seventy people at Arcules, the company I ran as one of Canon's youngest CEOs, managers sat between me and the work, and my 1:1s became 1:1s about their 1:1s.
I couldn't just delegate well anymore. I needed my managers to delegate well. Fixing that took my week from 60 hours to 45 while the company grew past 150 people.
Is reverse delegation the employee's fault?
Mostly no. When a handoff gets missed, the failure is upstream, not downstream. Your delegation wasn't good enough. Unclear delegation isn't kindness. It's cruelty. It sets people up to fail, then blames them for missing an expectation you never stated.
A founder I coach told me his team couldn't handle the client calls. I asked how many he had taken that week. Nineteen. How many of those nineteen only he could have taken? Two.
That's not a capability problem on the team. That's a capability problem in the calendar. The calls kept coming back because he kept catching them. Not a team pushing work up, a leader pulling it back down.
If you're the founder and the whole company's work returns to you, that's a different diagnosis, covered in founder coaching for the founder who can't delegate.
What they say, what it means, what you say back
The field guide for when the task lands on your desk again.
| What the employee says | What it usually means | What you say back |
|---|---|---|
| "Can you take a quick look before I send it?" | They want you to carry the risk. No authority level was stated. | "You own it. Send it. Update me after, for visibility, not approval." |
| "I think I can do that." | Think means will not commit. | "I need you to commit or tell me you can't. Which is it?" |
| "I was waiting on finance." / "Nobody told me." | Reasons in place of ownership. | "Reasons aren't results. If something blocks you, escalate the day it blocks you." |
| "There are a lot of dependencies here." | The excuse is being built before the work starts. | "What would need to be true for you to own this completely?" |
The six sentences that send a boomeranged task home
Say them in order. Most tasks go home by sentence three.
1. "What outcome did we agree you own?" Resets the frame from task to outcome. If they can't answer, you didn't delegate an outcome. Restate it in one sentence.
2. "Give me the situation and the complication, then the question you need answered." SCQA run in reverse. Half the time they answer their own question while saying it out loud.
3. "What would you do if I weren't here?" The sentence I teach every manager with a reverse delegator on their team. Then be quiet. Their way at good enough beats your way at perfect.
4. "Which level is this: decide and tell me after, decide and tell me before, or recommend and I decide?" If you never set the level, set it now. Most handbacks are Level 1 work treated as Level 3.
5. "What's the one blocker I can remove without taking the work back?" The check-in script from the 25% Rule. Remove a blocker. Don't absorb the task.
6. "Tell me what you'll do next and which day I'll hear from you." Said, heard, understood, committed. A head nod is not comprehension, and soon is not a date. Put the date in your calendar, not your head.
How do you prevent reverse delegation?
Two tools from the Delegation Protocol do the job.
The 3-Minute Delegation Conversation. Four timed blocks. Context, 60 seconds: Situation and Complication. Outcome, 45 seconds: what success looks like, not the steps.
Authority level, 30 seconds: Level 1, 2, or 3, out loud. Verification, 60 seconds: repeat back what I asked, why it matters, and whether you're committed. Three minutes upfront saves three weeks of confusion later.
The 25% Rule. Check in once, when the work is about 25 percent done: Wednesday on a five day task, the end of week one on a month long one. The script is support, not oversight: how is it going, any blockers I can remove, anything you need from me.
Not "can I see your work so far." At 25 percent a wrong direction is still correctable. At 90 it's too late. At 5 the check-in is micromanagement, the other failure mode, covered in how to stop micromanaging without losing control.
Then measure it. Every Friday, mark what stayed delegated against what boomeranged. Three out of four staying home is the pass mark. When delegated work comes back twice from the same person, reread your handoff.
The delegation training page walks through the levels, the free delegation assessment scores where your handoffs leak, and founders scaling past a leadership team will want founder to CEO delegation systems.
What is the difference between reverse delegation and asking for help?
The test is where the ownership sits when the conversation ends.
Asking for help: they bring a specific blocker, a proposed answer, and a request for something only you can supply. They leave still owning the outcome.
Reverse delegation: they bring the problem, you supply the thinking, and they leave with your answer. The outcome has moved.
A status update 1:1 hides the second kind: "what are you working on" invites a list of things you can fix. A calibration 1:1 asks what they'd do about it.
Most boomerangs start at the handoff itself. The four handoff moves in how to delegate so the work stays delegated close the gap before it opens, and the sourced figures on how rarely managers delegate well are collected in delegation statistics.
Reverse delegation FAQ
What is reverse delegation in management?
Reverse delegation in management is when a task or decision assigned to an employee moves back to the manager who assigned it. It usually appears as a request for review, a decision handed upward, or a problem raised without a proposed solution. The manager ends up doing the thinking or the work while the employee waits.
What is upward delegation?
Upward delegation is another name for reverse delegation, describing work that moves up the reporting line rather than down. An employee hands a task, a decision, or a problem to their manager, and the manager takes it on. The term emphasizes direction: the work travels against the intended flow of the organization chart.
How do you respond when an employee hands a task back?
Respond by asking rather than answering. Ask what outcome they own, what the situation and complication are, and what they would do if the manager were unavailable. Confirm the authority level they hold and offer to remove a specific blocker without taking over the task. Close by asking what they will do next and on which day they will report back.
Is reverse delegation always a bad thing?
Not always. Some work should come back, such as a decision above the employee's authority level, a risk only the manager can accept, or a resource only the manager can release. The problem is repeated returns, where the employee brings problems without proposals and the manager supplies the solution each time. One escalation is normal; a pattern signals unclear ownership.
How often should you check in on delegated work?
One planned check-in at roughly 25 percent completion is a common rule, which falls midweek on a one week task and at the close of week one on a month long project. At that point a wrong direction can still be corrected without starting over. Checking in at 5 percent is generally experienced as micromanagement, and waiting until 90 percent leaves no room to correct.
What did Oncken and Wass mean by the monkey on your back?
In "Management Time: Who's Got the Monkey?" (Harvard Business Review, 1974), William Oncken Jr. and Donald Wass used the monkey as a metaphor for the next move on a problem. When an employee describes a problem and the manager agrees to think about it, the next move jumps to the manager. The article argues the next move should stay with the employee.
The task came back because the handoff was a task
Reverse delegation isn't a personality trait on your team. It's a receipt for the handoff you actually made. A task with no context, no authority level, and no check-in date will come back, and it should, because nobody could own it. An outcome with a Situation, a Complication, a stated level, and a Wednesday on the calendar stays put.
Run the audit this week. Every time something lands back on your desk, ask sentence one before you touch it. The ones that don't go home tell you what was missing from the original three minutes.
Delegation that sticks isn't about trusting more. It's about saying more at the start so you can say less later.
The Delegation Protocol that keeps work delegated
The six sentences fix a boomerang after it happens. The Delegation Protocol inside The 5-Minute Leader is built so reverse delegation doesn't happen: the 70% Test for choosing what to hand off, SCQA for framing it, the 3-Minute Delegation Conversation with its three authority levels, SHUA/R-C for verifying the handoff landed, the 25% Rule, and a first week that ends with the Friday count.
It also names the four red flags that tell you, in the handoff conversation, that this one is coming back. You've met two of them in this post. The quietest one isn't here, and I'd bet it's sitting in your team right now.
