What is Delegation?
Delegation
Delegation is handing someone a specific piece of work along with the authority to decide how to do it, not only the instructions for doing it.
Delegation is a manager handing a specific piece of work to someone else, along with the authority to decide how it gets done. It differs from assigning a task. Assigning tells someone what to do and how. Delegating tells them what outcome is needed and lets them own the method, the schedule inside agreed limits, and most of the small decisions along the way.
RACI charts map who is Responsible, Accountable, Consulted, and Informed across an entire project. Delegation is the specific decision inside that structure: a manager choosing, task by task, what to hand off, to whom, and how much authority comes with it. A task can show one person as Responsible on a RACI chart while the manager still reviews every step, which is assignment wearing delegation's label. Real delegation means the Responsible person also holds the working decisions.
For a manager running a team of 4 to 25 people, delegation is one of the few skills that scales without adding headcount. A manager who delegates well can typically support 15-20 direct reports; one who does not tops out closer to 5-8, because every decision routes back through them.
Delegation vs Assigning a Task
Assigning and delegating look similar on a task board: a name goes in the owner field either way. The difference is in what moves with the name.
- Assigning: the manager already decided what to do and how; the task itself is the instruction, and the manager reviews and adjusts steps along the way
- Delegating: the manager hands over the outcome and the boundaries; the person decides the steps, the tools, and most of the schedule inside them
- A task can start as assigned and become delegated once someone has done it enough times to be trusted with the how
- Delegating everything to someone new on day one sets them up to fail; assigning everything forever caps how much a team can grow
Deciding What to Delegate
Not every task is a good delegation candidate. A simple test: does the task require a decision only you can make, or does it require time you happen to be spending on it because nobody else has been asked? Most recurring work falls into the second category.
| Task type | Delegate it? | Why |
|---|---|---|
| Recurring, well-defined work (status reports, routine client updates) | Yes, fully | Repeats often enough to be worth someone else learning it once |
| Work that builds a skill someone on the team needs next | Yes, with a checkpoint | The growth is the point, not only clearing your plate |
| A one-time decision with real financial or legal consequence | No, or delegate with a required sign-off | The cost of a wrong call outweighs the time saved |
| Work only you have the full context for | Not yet | Delegate after documenting the context, not before |
Delegation and RACI
RACI and delegation solve related but different problems. RACI is a project-wide map: for every task, who is Responsible, who is Accountable, who is Consulted, who is Informed. Delegation is the moment-by-moment decision a manager makes about how much of that Responsible role gets handed off, and how much stays with them.
The Accountable party, usually the manager, still answers for the outcome. That does not change with delegation. What changes is who makes the decisions along the way, and how often the manager needs to be consulted before the person can move.
How to Brief Delegated Work
A delegation that fails in the first week usually fails at the briefing, not at the execution. Five things belong in every delegation conversation:
- The outcome: what done looks like, described as a result, not a checklist of steps
- The boundaries: budget, deadline, who else needs to be consulted, what decisions require your sign-off
- The context: why this matters and how it connects to the larger project, so decisions in the gray areas go the right way
- The checkpoint: one agreed point to check in before the deadline, not a series of status requests
- The authority: say directly that they own the decisions inside the boundaries, so they do not default back to asking permission for everything
Levels of Delegation
Delegation is not all-or-nothing. Management researcher Jurgen Appelo's delegation framework describes several levels between telling someone exactly what to do and handing them full ownership. A simplified four-level version covers most cases:
| Level | What it means | When to use it |
|---|---|---|
| Tell | You decide, they execute exactly as instructed | New to the task, high stakes, or the first time doing it |
| Sell | You decide, but you explain the reasoning | Same as Tell, plus you want buy-in for a decision already made |
| Consult | They propose a plan, you approve or adjust before they start | Experienced with the task type, moderate stakes |
| Delegate | They decide and execute, then report once it is done | Track record on similar work, stakes the team can absorb if something goes wrong |
How to Avoid Taking Delegated Work Back
The hardest part of delegation is not the handoff. It is what happens in the days after, when the work is not going exactly the way the manager would have done it and the temptation is to step back in.
- Judge the outcome, not the method: if the result meets the agreed bar, a different process to get there is not a problem to fix
- Use the checkpoint you already agreed on, not a new one you invented because you are anxious about progress
- Let small mistakes play out inside the boundaries you set; that is what the boundaries are for
- If you take a task back, say so directly and explain why, rather than quietly redoing it and letting the person find out later
- Track how often you take work back across the team; a pattern across several people points at the boundaries you set, not at the people you delegated to
Reverse Delegation: When the Work Comes Back to You
Delegated work has a way of finding its way back to the manager's desk without ever being formally taken back. Management writer William Oncken called this dynamic the monkey on your back: someone hits a snag, brings you the problem instead of a proposed solution, and leaves the conversation having handed the next step to you instead of the other way around.
The fix is procedural, not personal. When someone brings a stuck task, ask what they think the next step is before offering one yourself. If they genuinely do not know, help them think it through, then send them off to do it rather than doing it for them. The task, and the next move, stays on their side of the desk.
In Melororium
Assign owners and track delegated work in Melororium
Common mistakes with delegation
What teams get wrong most often, and what to do instead.
- 1
Delegating the task but keeping the decision
Handing someone the work while still requiring approval on every step. The task moved; the ownership did not, so nothing about the manager's workload changes.
- 2
No clear definition of done
Handing off a task with a vague outcome and no boundaries. The person guesses at what good looks like, gets part of it wrong, and the manager treats a briefing gap as a performance problem.
- 3
Taking work back after the first mistake
Redoing something the moment it does not go exactly as planned. It solves the immediate problem and teaches the person, and everyone watching, that delegation here is not real.
- 4
Delegating only the tasks nobody wants
Offloading the tedious work while holding onto every meaningful decision. It looks like delegation on a task board and builds no real capability on the team.
Frequently asked questions
What's the difference between delegation and assigning a task?
Assigning tells someone what to do and how to do it; the manager keeps the decisions. Delegating hands over the outcome and lets the person make the decisions needed to get there, inside agreed boundaries.
How much detail should a delegation briefing include?
Enough for the person to succeed without checking back on every step: the outcome, the boundaries, the context, and one checkpoint. A step-by-step script is assigning, not delegating.
What if the person you delegated to makes a mistake?
Treat it as a coaching moment inside the boundaries you set, not proof that delegation failed. If the mistake had real consequences, the checkpoint should have caught it before it did; that's a boundary problem, not a delegation problem.
Should you delegate a whole project or individual tasks?
Depends on track record. A first delegation to someone new works better as one bounded task with a clear checkpoint. Full project ownership is something people earn by handling smaller pieces well first.
How is delegation different from RACI?
RACI maps roles across an entire project: who is Responsible, Accountable, Consulted, and Informed on every task. Delegation is the specific decision a manager makes about how much real authority the Responsible person gets.
