How to delegate effectively is usually taught as a question of letting go: trust your team, stop doing everything yourself. That advice is right and not very useful, because most managers already know they should delegate. What goes wrong is subtler. The work is handed over, and then, one small question at a time, it comes back.
This article covers why delegation is harder than it looks, the classic explanation of how work drifts back to the manager, how to hand over outcomes rather than tasks, and how to match the amount of freedom to the person.
Why delegating is harder than it looks
Three things make delegation feel like a bad trade in the moment.
Explaining takes longer than doing. For any single task, doing it yourself is faster. The return on delegation comes the second, third and tenth time, which is easy to discount when you are busy today.
The quality fear. Someone else will do it differently, and possibly worse, at least at first. For people promoted because they were good at the work, watching it done less well is uncomfortable.
Identity. Many new managers still think of themselves as the person who does the work. Handing it over can feel like losing the thing that made them valuable. It is the shift from doing to enabling others to do, and it is one of the hardest in any career, as the article on what makes a good leader describes.
None of these is irrational. They are simply short-term views of a long-term decision.
Delegation rarely fails when the work is handed over. It fails when the work quietly comes back.
Who has got the monkey?
The most famous explanation of how delegation fails is a 1974 Harvard Business Review article by William Oncken Jr. and Donald Wass, "Management Time: Who's Got the Monkey?", which became one of the magazine's best-selling reprints.
Their image is simple. Every problem is a monkey, and it sits on someone's back. An employee stops the manager in the corridor: "We have a problem with the supplier." The manager, wanting to help, says "Let me think about it and get back to you." In that moment the monkey has jumped. The employee walks away lighter. The manager now owns the next move, and the employee is waiting on them.
Repeat that a dozen times a week and the manager is working late on their team's problems while the team waits for answers. Oncken and Wass's prescription was to make sure the next move stays with the person who brought the problem: "What do you recommend? Come back with a proposal by Thursday."
How to delegate effectively: hand over the outcome, not the steps
Much delegation is really instruction: a list of tasks, in order, with the manager still holding all the decisions. That is not delegation. It is remote control, and it guarantees the questions will keep coming.
Real delegation hands over a result, and with it the authority to decide how to get there. A good handover covers five things:
- The outcome: what done looks like, as specifically as you can describe it.
- Why it matters: the context that lets the person make good calls you did not foresee.
- The constraints: budget, deadline, things that must not happen.
- The authority: what they can decide alone and what they need to check.
- The check-ins: when you will look at progress together.
The second item is the one most often missing. Without the why, the person can only follow instructions. With it, they can adapt when something unexpected happens, which is exactly when you would otherwise get the call.
Check yourselfA manager believes she has handed a decision over to a colleague, yet he keeps checking with her before each step. What do you think is going on, and what one sentence might fix it?Show the answerHide the answer
Most likely a level mismatch. She thinks she handed over 'decide and tell me'; he thinks he is at 'look into it and report back', so checking in is what he believes he was asked to do. Saying the level out loud, 'I would like you to decide this one and just let me know', removes the confusion.
Levels of delegation
Delegation is not all or nothing. A useful way to think about it is as a range of how much freedom the person has, from following instructions to acting fully on their own.
| Level | What the person does | Suits |
|---|---|---|
| 1. Do as instructed | Follows a defined method | New tasks, new people, high risk |
| 2. Look into it and report back | Gathers information, you decide | Unfamiliar areas |
| 3. Recommend | Proposes an option, you approve | Building judgement |
| 4. Decide and tell me | Acts, then informs you | Proven competence |
| 5. Decide and act | Owns it fully | Trusted, experienced people |
The point of naming the level is that most delegation problems are level mismatches. The manager thinks they have handed over level four; the employee thinks they are at level two and keeps checking in. Saying the level out loud, "I would like you to decide this one and just let me know", removes the confusion.
How this is taught inside Astra Trainer
The Leadership & Management direction in the Leadership, Career & Influence world is built around the job after the title: courses such as Why People Follow, Leadership Styles, How Groups Actually Work and Motivation cover what makes people take ownership rather than wait for instructions.
Delegation sits at the centre of that, because it is where a manager's style shows up in someone else's working week. Lessons take about five minutes and a guide walks you through anything strange.
Match the level to the person, and the task
The right level depends on who is doing the work and how familiar they are with this particular task. That is the core of situational leadership, a model developed by Paul Hersey and Ken Blanchard in 1969, which argues that the right management style depends on the person's competence and commitment for the specific task in front of them.
The last part matters. An experienced analyst may be at level five for reporting and level two for presenting to the board. Treating someone as uniformly junior frustrates them; treating them as uniformly senior sets them up to fail on the unfamiliar parts.
Start lower on new tasks and move up deliberately, telling the person when you do. "You have handled the last three supplier issues well, so from now on just decide and let me know" is both delegation and recognition in one sentence.
Check-ins without micromanaging
The fear of losing sight of delegated work is what drives micromanagement: frequent unplanned questions, requests for updates, looking over shoulders. The fix is to agree check-ins in advance.
Set them at the handover: a short review at the end of week one, a look at the draft before it goes out, a note when the key decision is made. Between those points, stay out. The person knows when you will look and can plan around it, and you know you will not be surprised at the end.
Check-ins should be about the outcome and the obstacles, not about redoing the work. If the approach differs from yours but will get the result, let it stand. Correcting style rather than substance is the fastest way to teach someone to stop taking initiative. When something does need correcting, the principles in how to give constructive feedback keep the conversation on the work.
Try it on the last task you handed over
Ticked: 0 of 5
Each unticked line is a place where questions tend to flow back to you. The second is the one most often missing, and it is what lets people adapt when something unexpected happens.
What not to delegate
Some things stay with the manager. Performance conversations about someone's own work. Decisions that depend on confidential information the person cannot see. Anything where the team needs to hear directly from you, such as a difficult change or bad news.
Crises are a special case. In the first hours, it is usually right to take direct control. Once the immediate problem is contained, hand the follow-up back, so the crisis does not become a permanent reason to hold everything.
A worked example
A team lead is asked to prepare the quarterly customer report, which she has always written herself. Her first attempt at delegating it is a list: pull these three data sets, make these charts, use last quarter's template. Her colleague produces exactly that, and every judgement call, which accounts to highlight, how to explain a dip, comes back to her as a question.
The second time, she hands over the outcome instead: "The report needs to show leadership where we are gaining and losing customers, and why. You decide what to highlight. Show me a draft by the 10th, and we will review it together before it goes out." She names the level as recommend, level three, for this first quarter. The questions drop to two. By the third quarter she moves it to level four, decide and tell me, and reads the report when everyone else does.
Why delegation is a habit to build
Every manager knows delegation is good. The difficulty is the reflex, in a busy moment, to say "leave it with me" and take the monkey. Changing that reflex takes practice more than understanding.
Astra Trainer is built around that kind of practice. Quizzes follow each topic and each course ends with a ten-question final exam, while daily quests, points and a streak keep five-minute lessons going, with a streak shield for the day that goes wrong. A Circle gives you a small group with a shared weekly goal and live sessions, which is where other managers tend to point out the monkeys you have not noticed collecting.
What to take from this
Delegation rarely fails at the handover. It fails when problems drift back to the manager, which Oncken and Wass described in 1974 as monkeys jumping from one back to another.
Hand over the outcome, the reason it matters, the constraints and the authority, not a list of steps.
Name the level of freedom, match it to the person's experience with that specific task, and raise it deliberately. Agree check-ins in advance so you can stay informed without hovering.
Which is why the most useful answer to how to delegate effectively is one question, asked every time someone brings you a problem: what do you recommend?
Test yourself
Question 1 of 3
An employee stops a manager in the corridor with a supplier problem. In Oncken and Wass's terms, which reply keeps the monkey on the employee's back?
How do you delegate effectively?
Hand over the outcome rather than a list of steps, explain why it matters, set the constraints, say clearly how much the person can decide alone, and agree check-in points in advance. Then leave the work with them between check-ins.
Why do managers find it hard to delegate?
Explaining a task takes longer than doing it once, others may do it differently at first, and many managers still see themselves as the person who does the work. These are short-term costs of a decision that pays off over time.
What does who has got the monkey mean?
It comes from a 1974 Harvard Business Review article by William Oncken Jr. and Donald Wass. A monkey is the next move on a problem. When a manager says they will think about an employee's problem, the monkey jumps to the manager, and the employee is left waiting.
What should a manager not delegate?
Performance conversations about a person's own work, decisions that rely on confidential information, and messages the team needs to hear directly from the manager, such as significant change or bad news. In a crisis, direct control at first is usually right.
Where can I learn people management in short lessons?
The Leadership & Management direction inside the Leadership, Career & Influence world of Astra Trainer covers why people follow, leadership styles, motivation and how groups work, in five-minute lessons with quizzes. The first lesson needs no card.
Where this leads. What Is a Mini MBA, and Is It Worth Doing? places managing people alongside the other areas of the business syllabus, and explains the order to learn them in.
