How to Delegate as a Manager

Short answer: To delegate as a manager, hand over the outcome and the decision rights, not just the task. Pick work someone else can do at 80 percent of your quality or better, brief them on what done looks like and the limits they cannot cross, agree when you will check in, then let them own the rest. You stay accountable for the result and the guardrails. You stop being the bottleneck for every step.

Key takeaways

Why managers fail to delegate

Almost every manager knows they should delegate more. Far fewer actually do it, and the reason is rarely laziness. Delegating well feels slower and riskier in the moment than just doing the thing yourself. You already know how. You can finish it in twenty minutes. Teaching someone else takes an hour today and might still come back wrong. So the urgent task wins, again, and your calendar quietly fills with work that should belong to other people.

The common failure modes are worth naming because you can see yourself in at least one of them:

• The expert trap. You got promoted because you were good at the work, so you keep doing the work. Your value now is multiplying other people's output, not maximising your own.
• Perfectionism. You believe only you can do it to standard. Sometimes true. Usually it means you have never let anyone get to standard, because that requires letting them be worse for a while first.
• No time to teach. Delegation is an investment that costs time now and pays back over weeks. If every week is pure firefighting, the investment never gets made and the fires never stop.
• Fear of looking redundant. If your team can run without you, what are you for? This fear is backwards. A manager whose team runs without them is exactly what a good manager is for.
• Reverse delegation. You hand off a task, it gets hard, the person brings it back, and you take it. Now you are doing their job and yours.

Notice the pattern: none of these are solved by a better to-do list. They are solved by a decision to trade short-term speed for medium-term capacity, and then by practising the handoff until it stops feeling dangerous.

What to delegate and what to keep

Not everything should leave your desk, and the manager who delegates the wrong things does as much damage as the one who delegates nothing. Use a simple filter.

Delegate this

• Recurring work. Anything you do weekly or monthly that follows a pattern. Teach it once, free yourself repeatedly.
• Work someone can do at 80 percent of your quality. The last 20 percent is rarely worth your time, and they will close the gap with reps.
• Stretch assignments. Tasks slightly above someone's current level. This is how people grow, and growth is delegation that compounds.
• Things you are mediocre at. Someone on your team is probably better than you at something you have been clinging to. Let them have it.

Keep this

• Direction and priorities. Where the team is going and what matters most is your call to make and communicate.
• Hiring, firing, and pay. Decisions that shape who is on the team stay with you.
• Sensitive people situations. Conflict, performance problems, and morale are managerial work, not tasks to pass down.
• Expensive, irreversible decisions. The one or two calls a quarter where being wrong is costly and hard to undo. Delegate the analysis, keep the decision.

A useful test: if a task is frequent, teachable, or developmental, it should go. If it is rare, sensitive, or irreversible, it should stay. Most of what fills a manager's day falls in the first bucket, which is exactly why most managers are busier than they should be.

How to delegate in five steps

Good delegation is a short, deliberate handoff, not a one-line message and a hope. Run these steps every time and it becomes second nature.

1. Choose the right person and the right size. Match the task to someone whose skill is close to it, and size the slice to their proven track record. New or unproven, give a smaller piece with tighter support. Experienced, hand over the whole thing.
2. Brief the outcome, not the steps. Describe what done looks like, why it matters, and how success will be judged. Resist scripting the how. The how is theirs to figure out, and that is where ownership starts.
3. Set the guardrails. Name the constraints that cannot be crossed: budget, deadline, who to loop in, decisions that need your sign-off. Inside the guardrails they decide. Outside them they check with you. This is how you keep control without hovering.
4. Agree checkpoints up front. Decide together when you will review progress, before any work starts. Scheduled check-ins replace anxious drop-ins, and they let you catch a drift early without snatching the work back.
5. Step back, then debrief. Let them run. When it is done, talk about what worked and what was hard, so the next handoff is bigger. Resist the urge to fix it silently. Silent fixes teach nothing and breed dependence.

Common delegation traps

• Dumping, not delegating. Tossing a task with no context, no guardrails, and no checkpoint, then being annoyed it came back wrong. That is abdication wearing delegation's clothes.
• Delegating the task but keeping the authority. If they have to come to you for every small decision, you have not delegated anything. You have added a relay step to your own work.
• Taking it back at the first wobble. The moment it gets shaky you grab it, telling yourself it is faster. You just taught the whole team that bringing you problems makes problems disappear. They will keep bringing them.
• Over-checking. Asking for updates so often that the person spends more time reporting than doing. Trust the checkpoints you agreed and wait for them.
• Delegating only the boring work. Hand off all the drudgery and keep all the interesting parts, and your best people will leave. Stretch and visibility have to flow down too.

Delegation is a behaviour, not a checklist

Here is the part the listicles skip. You can read every rule above, nod at all of it, and still freeze the next time a real task is sitting in front of you and the clock is running. Delegation is not knowledge you acquire. It is a behaviour you build, and you only build it by doing it under pressure, when the result genuinely matters and you cannot do everything yourself.

That gap between knowing and doing is exactly what experiential learning is for. Reading about handing off decisions changes nothing. Being forced to hand off decisions, watching what happens, and feeling the cost of holding on too long is what rewires the habit. This is the idea behind the Put The Player First framework, the method behind the games we design: put people in a real decision environment, let the behaviour show up, then turn what happened into change in the debrief.

One of our simulations is built almost perfectly for this. Chaos in the Kitchen is a business simulation where you run a kitchen under pressure: prioritising, triaging, making trade-offs, and owning decisions on incomplete information while service events keep landing. Managers who hoard every call get buried. The ones who delegate, set priorities, and trust the team survive the rush. You feel the lesson in your body, which is why it sticks in a way a guide cannot.

If you want the bigger picture on building leadership behaviour this way, start with our guide to serious games for leadership development.

Frequently asked questions

Basics

Why do managers struggle to delegate?
Because handing off work feels slower and riskier in the short term than doing it yourself. Add the expert habit, perfectionism, and no time set aside to teach, and delegation keeps losing to the urgent. Treat it as an investment that pays back over weeks, not a favour for when you have spare time.

What should I delegate and what should I keep?
Delegate recurring work, anything teachable, and stretch tasks that grow people. Keep direction, hiring and firing, sensitive people calls, and the rare decisions that are expensive and hard to reverse. If a task is frequent, teachable, or developmental, it should leave your desk.

How to

How do I delegate without losing control?
Delegate the outcome and the decision rights, then control through guardrails and agreed checkpoints instead of constant oversight. You own the result and the boundaries. They own the steps inside them.

How do I delegate to someone who is not ready?
Give a smaller slice, clearer instructions, and earlier check-ins, then widen the scope as they prove they can carry it. Readiness is built by delegating, not waited for. Start small rather than not at all.

Traps

What is the most common delegation mistake?
Dumping a task with no context or guardrails and then taking it back the moment it wobbles. The first teaches nothing, the second teaches your team that bringing you problems makes problems vanish, so they keep bringing them.

Related reading

• Serious games for leadership development: the complete guide
• Chaos in the Kitchen: decisions under pressure
• The Put The Player First framework

See the games Get in touch