How to Delegate Effectively: The Part Most Managers Get Wrong

Most managers believe they delegate. What they usually do is allocate — hand over a task while keeping every decision about it. The person does the work, brings it back, and the manager decides. That is useful for throughput and develops nobody, and it is why so many managers stay the bottleneck they were promoted to remove.

The difference between allocation and delegation is decision rights. Not who does the work — who decides.

Five levels, and picking the right one

State the level explicitly when you hand something over. Most delegation failures are a mismatch between the level the manager intended and the level the person heard.

1. Do exactly this. No judgement required. Appropriate for genuinely procedural work, and for someone very new.
2. Look into it and report back. They gather, you decide. The right level for genuinely consequential decisions and for building someone's context.
3. Recommend an option. They analyse and propose, you approve. The most under-used level and the best development step, because they have to form a view.
4. Decide and tell me before you act. They own it, you retain a veto you will rarely use. Where most capable people should be operating.
5. Decide and act. Full ownership. You hear about it in the normal course of things.

If you never move anyone past level 2, nobody develops and everything routes through you. If you jump someone to level 5 on something consequential, you have abdicated rather than delegated.

What to say when you hand it over

Four things, and the third is the one people skip:

• The outcome, not the method. What done looks like.
• The constraints. Budget, deadline, who must be consulted, what is off the table.
• The level. Say which of the five. "Come back to me before you commit us to anything" is a sentence that prevents most delegation accidents.
• Why them. Thirty seconds of context — why this person, why now, what they get from it — changes it from a task being offloaded into something being entrusted.

The four reasons managers do not delegate

"It is quicker to do it myself." True once. False by the fourth time, and the compounding runs against you.

"They will not do it the way I would." Correct, and mostly irrelevant. If the outcome is right, the method difference is yours to live with. Reserve your intervention for outcomes, not style.

"I do not want to dump work on them." Usually your discomfort, not theirs. Being given something that stretches you is how people grow, and being protected from it is how they stall.

"It is too important to risk." Sometimes true. More often it means the right level is 2 or 3, not that it cannot be delegated at all.

Checking in without taking it back

The moment that undoes most delegation is the check-in. Ask "how is it going" and you get a status update. Ask "what have you decided" and you reinforce that the decision is still theirs.

If something is going wrong, resist the reflex to take it back. Ask what options they are considering. Taking it back once teaches the whole team that difficult things return to you under pressure — and from then on they will bring you problems rather than proposals.

Agree the check-in points when you hand it over, not opportunistically. Unscheduled check-ins read as supervision regardless of intent.

When it goes wrong

It will. The question is what you do publicly.

If you delegated the decision, you own the outcome upward. Saying "my team made a call that did not work" in front of your own manager is the fastest way to ensure nobody takes a decision again. Own it outside, work through it inside.

And separate the two failures when you review it: did they make a reasonable decision that turned out badly, or an unreasonable one? Those need completely different conversations, and conflating them punishes judgement rather than error. If the conversation is going to be a hard one, our guide to difficult conversations at work covers the structure.

Frequently asked questions

How do I delegate when the team is already at capacity?

You do not, without removing something. Delegation is not a capacity solution; adding work to a full plate is just a slower failure.

Should I delegate things I enjoy?

Often yes, and it is uncomfortable. The work you enjoy is frequently the work that developed you.

What if they come back constantly with questions?

Usually a sign the level was unclear or the context was thin. Ask what they think the answer is before answering.

How do I know if I am delegating enough?

If you went on leave for two weeks, how much would stop? That is the real measure.

Our CPD courses include management development mapped to professional body requirements, and our guide to your first management role covers the wider transition.