Delegation at Work: Meaning and How to Delegate Tasks
Author: Kevin Baur BSc
Published on
Contents
- What is delegation?
- Delegating vs assigning, dumping, covering and handing over
- Why delegation matters and why it is hard
- Which tasks to delegate and which to keep
- The 7 levels of delegation
- How to delegate tasks in 6 steps
- Delegation checklist for the briefing
- Reverse delegation: who's got the monkey?
- Common delegation mistakes
- The bottom line
Almost every manager has said it: by the time I explain this, I could have done it myself. The first time, that is true. The tenth time, it is not, and eventually half the team waits on one person who has no time left. This guide explains what delegation means, what you hand over and what you keep, which tasks to delegate, the seven levels of delegation and how to delegate tasks in six steps.
What is delegation?
Wikipedia defines delegation as the process of distributing and entrusting work to another person. In management, it means a manager passes work, decisions and responsibility to people in their team. Asana puts it in everyday terms: you reassign work to team members because it fits their work and priorities better than yours.
The word has a second common meaning, a group of people sent to represent others, such as a trade delegation. This guide is only about delegating tasks at work.
Two principles from the Wikipedia article matter most in practice:
- Parity of authority and responsibility: the authority you hand over has to match the responsibility. If someone is asked to pick a supplier, they also need the right to sign the order and a budget. Responsibility without authority is meaningless.
- Absoluteness of responsibility: you can delegate authority, but not your ultimate responsibility. The manager stays accountable for the outcome.
Delegating vs assigning, dumping, covering and handing over
| Term | What is passed on | Who decides | How long |
|---|---|---|---|
| Delegating | A task, the authority for it and responsibility for the result | The person who takes it on, within agreed limits | One task or ongoing |
| Assigning a step | One specific instruction | The manager | Once |
| Dumping | An unwanted task with no goal, limits or authority | Unclear | Until it goes wrong |
| Covering | The running work of someone who is away | The cover, usually within tighter limits | While the person is away |
| Handing over | A whole role with all its tasks and the knowledge behind them | The successor | Permanently |
Why delegation matters and why it is hard
Wikipedia lists the main reasons to delegate: to free up your own time, to have the most qualified person make the decision, to get another perspective and to develop someone else's abilities. It also links delegation with trust, motivation, task performance and job satisfaction. Harvard Business Review author Jesse Sostrin describes the shift from doing to leading as one of the hardest transitions a new manager makes.
So why do so many managers delegate too little? The same article names the usual fears: that mistakes will be made, that the work will not meet their own standard, losing touch with skills they enjoy and the risk of staying responsible for something they no longer control. There is also a practical reason. The knowledge of how a task really works often lives only in one head, and writing it down takes time.
Which tasks to delegate and which to keep
A common starting point is the Eisenhower matrix, which sorts tasks by importance and urgency. In that method, urgent but unimportant tasks are delegated, while important tasks are done personally. Use it as a rough guide rather than a rule, because in small or flat teams there is often no one obvious to delegate to.
| Category | Typical tasks |
|---|---|
| Easy to delegate | Recurring routine work, tasks someone on the team does better, tasks that help someone grow, research and preparation |
| Delegate with care | Client meetings, budget decisions, high risk projects: only with clear limits and check points |
| Keep | Leadership work such as setting goals, one to one meetings, performance reviews, confidential people matters and decisions in an acute crisis |
The 7 levels of delegation
Delegation is not a switch between doing everything and handing everything over. Management 3.0's Delegation Poker describes seven levels. Say openly which level you mean before work starts.
| Level | What it means |
|---|---|
| 1 Tell | I decide and tell them. |
| 2 Sell | I decide and try to convince them. |
| 3 Consult | I ask for input, then decide. |
| 4 Agree | We decide together. |
| 5 Advise | I advise, they decide. |
| 6 Inquire | They decide, and I ask about it afterwards. |
| 7 Delegate | I hand the decision over completely. |
With a new task and a less experienced person, start around level 3 or 4 and move up step by step. Management 3.0 makes the same point: delegation is a gradual process that depends on context.
How to delegate tasks in 6 steps
1. Choose and define the task
Write down exactly what is being handed over and what is not. A task with a clear start and end is a better first step than a whole area of responsibility.
2. Pick the right person
Who can already do it, who should learn it, who has capacity right now? A skills matrix shows at a glance who knows what and where a task depends on one person.
3. Agree on the outcome, limits and authority
Describe the result you need, not every move. Set the deadline, the budget and the level of delegation. If others need to be consulted or informed, record it in a RACI matrix.
4. Pass on the knowledge
This is where most delegation breaks down. The goal and deadline are quick to say, but the how lives in your head: the exceptions, the client who calls on Fridays, where the template is, what went wrong last time. Write it down as a short SOP or checklist and let the person sit in on the first run, for example through job shadowing.
5. Tell others and set check points
Let everyone involved know who is responsible now. Agree on fixed times for updates instead of checking in at random. That keeps you accountable without micromanaging, which Wikipedia names as a typical result of poor delegation.
6. Give feedback and credit
Review the result, even if it looks different from how you would have done it. Give credit for good work. Next time, you can move up a level.
Delegation checklist for the briefing
- What needs to be done, and what is explicitly out of scope?
- Why does it matter, and what will the result be used for?
- Who owns it, and who must be consulted or informed?
- How much can they decide alone, at which level?
- With what: which documents, access, contacts and budget?
- By when is it due, and when are the check points?
- What if something unexpected happens?
Reverse delegation: who's got the monkey?
In a classic Harvard Business Review article, William Oncken and Donald Wass describe how the problems of team members keep ending up on the manager's back, pictured as monkeys. This is often called reverse or upward delegation: a decision that belongs to the team member travels back up to the manager. It tends to happen when the authority is unclear or when the person lacks the knowledge to decide alone. The fixes are steps 3 and 4: clear limits and enough know how to move forward without asking.
Common delegation mistakes
- The task without the authority: every small decision comes back to you.
- No clear outcome: the result does not fit, and both sides are frustrated.
- Knowledge stays in your head: exceptions and contacts are missing, and the task bounces back.
- Constant checking: if you control every step, you have not delegated.
- Always the same person: your most reliable people burn out, and new pockets of tribal knowledge appear.
When a role moves to someone else for good, delegation is not enough. You need a full handover. The guide to the employee handover document shows how to structure one, and a job description shows what the role covers in the first place.
The bottom line
Good delegation means the right task to the right person, with a clear outcome, real authority and the knowledge the task needs. Your accountability stays, the work moves. Start small, agree on the level openly and move up step by step. And write the knowledge down while the person who has it is still around.
Frequently asked questions
- What is delegation in simple words?
- Delegation means giving a task to someone else along with the authority they need to do it and responsibility for the result. At work, managers usually delegate to team members to free up their own time and to help people develop.
- What should you not delegate?
- Keep leadership work such as setting goals, one to one meetings and performance reviews, confidential people matters and decisions in an acute crisis. Your ultimate accountability for a delegated task cannot be handed over either.
- Who is responsible when a task is delegated?
- The person who takes on the task is responsible for doing it within the agreed limits. The manager stays accountable for the outcome, because they chose the person, set the goal and agreed on the check points.
- What are the levels of delegation?
- Management 3.0 describes seven levels: tell, sell, consult, agree, advise, inquire and delegate. They range from the manager deciding alone to handing the decision over completely. Agreeing on the level up front avoids misunderstandings.
- What is reverse delegation?
- Reverse delegation happens when a decision that belongs to a team member is pushed back up to the manager. Harvard Business Review's classic article on the topic calls it the monkey on the manager's back. Clear authority and enough knowledge to decide alone help prevent it.