Delegation: how to do it properly (and why managers avoid it)

Delegation is the skill managers say they know they should use more, and the one they cut first when busy. That is unfortunate, because the busier you are the more it is the answer.

What delegation actually is

Delegation is passing on responsibility for something that is properly yours, along with enough authority to act on it, while remaining accountable for the outcome.

Three parts of that sentence do the work:

• Properly yours. Handing someone a task already in their job description is allocation, not delegation.
• Enough authority to act. Without this you have created a messenger, not a decision-maker, and you have kept all of the work while adding a hand-off.
• Remaining accountable. You cannot delegate accountability. If it goes wrong it is still yours, which is why the boundaries have to be explicit.

The five levels of delegation

Most delegation failures are actually mismatched expectations about how much authority came with the work. Naming the level fixes this in one sentence.

Say the number, or say the sentence. "Investigate it and come back with a recommendation" is a completely different instruction from "sort it out", and teams cannot read minds.

How to delegate well: seven steps

1. Pick the right task. Good candidates: things that recur, things that develop someone, things somebody else could do better than you. Bad candidates: your own performance conversations, confidential matters, and anything you are delegating purely because you dislike it.
2. Pick the right person, honestly. Capability and capacity. Delegating to your most reliable person every time is not delegation, it is favouritism with extra steps, and it will burn them out.
3. Explain the outcome and the why. People make far better decisions when they understand the purpose than when they only have the instruction.
4. State the level and the boundaries. Budget, deadline, who they can speak to, what must come back to you.
5. Agree checkpoints, not surveillance. Two or three defined points beat unpredictable interruptions. Checkpoints are also your evidence trail.
6. Let them do it their way. If the outcome is right and the method is safe, resist correcting the method. Every correction you make is authority taken back.
7. Review and credit. Feedback both ways, and public credit for the result. Taking credit for delegated work is the fastest way to guarantee nobody volunteers again.

The honest reasons managers do not delegate

• "It's quicker to do it myself." True the first time, false by the fourth. The arithmetic only works if you never intend to do it again.
• "They won't do it as well as me." Probably right initially. The question is whether you can afford a temporary dip in quality in exchange for permanent capacity.
• "It's the part of the job I enjoy." The most honest reason and the least discussed. Recognise it rather than dressing it up as necessity.
• "If I delegate everything, what am I for?" A real anxiety, particularly for newly promoted technical specialists. The answer is that you are for the things only you can do: direction, difficult conversations, and developing the people.
• No slack. Sometimes the reason is structural — a team running at 100% has no room to learn. That is worth escalating rather than absorbing.

Goleman's pacesetting style is the pattern to watch for here: the manager who models exemplary standards, cannot hand anything over, and ends up with a passive team and no time.

Delegation in a UK workplace: a worked example

A conveyancing team leader runs a caseload of her own plus a team of six. She is the only person who prepares the monthly file-audit report, which takes a day and a half.

She delegates it to a paralegal at level 2 for the first month (gather the data, draft the commentary, bring it to me), level 3 for the next two (draft it and tell me your conclusions before it goes out), and level 4 thereafter. She writes down what "good" looks like — the three questions the report must answer — and gives him access to the case management reports he needs, which is the authority part.

Month one costs her more time than doing it herself. By month four she has a day a month back, the paralegal has a genuinely developmental piece of work for his own portfolio, and the report is better because he spots patterns in files she never reads.

How to evidence delegation in your ILM portfolio

Delegation is a core assessment area, and it evidences well because it produces artefacts.

Level 3 — Unit 303 Managing the performance of others and Unit 315 Developing a high performing team. Suitable evidence:

• A reflective account of one delegation: who, why them, what level of authority, how you supported it, what you would change.
• Workplace documents — the brief you wrote, the checkpoint notes, the resulting report.
• A witness testimony from the person you delegated to, describing what they were given and how they were supported. This is far more convincing than your own account.

Level 5 — Unit 503 Managing people, plus Unit 516 Managing resources where you are delegating resources rather than tasks, and Unit 505 Coaching and mentoring in a leadership role where the delegation was explicitly developmental. At Level 5 evaluate it: what did delegating change about your own use of time, and what does the evidence show about the effect on the person?

Where to go next

• Team leader responsibilities
• Coaching vs mentoring — the developmental conversation that makes delegation stick.
• Reflective account examples