Resist reverse delegation (the "monkey back" problem)
When a report brings you their monkey, don’t take it — send it back with the next step owned.
Why it works
William Oncken and Donald Wass described "management time" being captured by reports who escalate responsibility back to the manager. When a manager accepts a task that was delegated, they model that upward escalation works and incentivize it. The manager becomes the bottleneck; the report becomes a supplicant. Resisting this requires a specific conversational move: returning the next action explicitly to the person who brought it.
How to do it
- When someone says "we have a problem" and looks at you, ask "what’s your recommended next step?"
- If they say "I don’t know," say "think about it and come back with an option by [time]" — don’t fill the gap yourself.
- When you do take action on something delegated, call it out explicitly so it’s a deliberate exception, not a pattern.
- After any meeting where you absorbed someone’s task, move it back to their name before the week is out.
Evidence
The "Who’s got the monkey?" HBR article (Oncken & Wass, 1974) is one of the most-reprinted Harvard Business Review pieces, suggesting wide practitioner resonance. The mechanism maps onto organizational research on escalation of commitment and managerial overload. (clinical)
The monkey metaphor is practitioner wisdom; controlled studies on reverse delegation as an isolated phenomenon are not available.
Sources
- Oncken & Wass (1974), Management Time: Who’s Got the Monkey?, Harvard Business Review
- Oncken, W., Jr., & Wass, D. L. (1974). Management Time: Who's Got the Monkey? Harvard Business Review, 52(6), 75-80. (Reprinted 1999.)
Common mistake
Taking the task while saying "this is the last time" — which is precisely what incentivizes the behavior to continue, because it proved the strategy worked once.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Delegation Levels, Made Practical
- Name the delegation level explicitly at the start of every task
State clearly whether you want a recommendation, a decision with notification, or a decision without notification — before the work begins.
- Match the delegation level to the person’s current competence and confidence
Over-delegate to someone who isn’t ready and they fail; under-delegate and they stagnate.
- Push recommendations up, not problems
Require reports to bring a recommendation alongside any problem — it’s a delegation practice, not just a time-saver.
- Clarify what people can decide without asking
Define the fence: what decisions can anyone on the team make without checking in?
- Debrief after delegated tasks to build for the next level
A delegation debrief is not a performance review — it is a joint analysis of what you both learned.
Related concepts
- The Eisenhower Matrix and Delegation
Urgency versus importance, effective delegation, and how to protect the quadrant that matters most
- Psychological Safety in Teams
What psychological safety actually is, how leaders build it, and where the evidence is real
- The GROW Coaching Model, Made Practical
The four stages, the questions that move each stage, and where the model is strong