Short answer: Hand over the outcome and the decision rights, not just the task. Pick work someone else can do at 80 percent of your quality. Tell them what done looks like and which lines they cannot cross. Agree when you will check in. Then get out of the way. You stay accountable for the result and the guardrails. You stop being the person every small thing has to queue behind.

Key takeaways

Question	The short version
What do I delegate?	Anything recurring, anything teachable, anything that would stretch somebody
What do I keep?	Direction, hiring and firing, the sensitive people stuff, the expensive one-way doors
How do I delegate well?	Give the outcome and the decision rights. Set the lines. Book the check-in
How do I keep control?	Own the result and the boundaries. Not the steps. Check in, do not hover
Biggest trap?	Chucking it over the wall with no context, then grabbing it back the second it wobbles

Why managers fail to delegate

Here's the thing nobody says out loud. Every manager knows they should delegate more. Almost nobody does. And it is not laziness - it is that delegating properly is slower today than just doing the bloody thing yourself. You know how. Twenty minutes and it is done. Teaching someone costs you an hour and might still come back wrong on Thursday. So the urgent wins. Again. And your calendar quietly fills up with other people's work while you tell yourself next month will be calmer.

Five ways this goes wrong. You will recognise at least one of them, and probably not the one you expect:

• The expert trap. You got promoted for being brilliant at the work, so you keep doing the work. But your job changed. You are now paid to multiply other people's output, not to be the best individual contributor with a bigger title.
• Perfectionism. "Only I can do it to standard." Occasionally true. Usually it means nobody has ever been allowed to reach the standard, because reaching it requires being worse at it first, in public, for a few weeks.
• No time to teach. Delegation costs an hour now and pays back every week after. But if every week is a fire, the hour never happens... and the fires never stop. That is not a coincidence.
• Fear of looking redundant. If the team runs without you, what exactly are you for? This one is backwards. A team that runs without you is the whole point. That is the job description.
• Reverse delegation. You hand it off, it gets hard, they bring it back with a worried face, and you take it. Congratulations. You now do their job and yours.

None of these get fixed by a better to-do list. They get fixed by deciding to trade this week's speed for next quarter's capacity, and then doing the handoff often enough that it stops feeling like standing on a ledge.

What to delegate and what to keep

Not everything should leave your desk. The manager who delegates the wrong things does just as much damage as the one who delegates nothing, and gets applauded for it for about six weeks. So use a filter.

Delegate this

• Recurring work. Anything you do every week that follows a shape. Teach it once. Get free of it forever.
• Work someone can do at 80 percent of your quality. That last 20 percent is almost never worth your Tuesday. They will close the gap with reps anyway.
• Stretch assignments. A little above where they are now. This is how people grow, and grown people delegate to their own teams. It compounds.
• Things you are frankly mediocre at. Somebody on your team is better than you at something you have been quietly hoarding. Let them have it. Nobody will think less of you.

Keep this

• Direction and priorities. Where the team is going, and what matters most this quarter. Yours to decide and yours to say out loud.
• Hiring, firing, and pay. Who is on the team is not a task. It is the team.
• Sensitive people situations. Conflict, a performance problem, someone quietly checking out. That is the managerial work. It does not get passed down.
• Expensive, irreversible decisions. The one or two a quarter where being wrong costs real money and cannot be undone. Delegate the analysis. Keep the call.

The test: frequent, teachable, or developmental, it goes. Rare, sensitive, or irreversible, it stays. Most of what fills a manager's day sits firmly in the first bucket. Which is exactly why most managers are so busy and so tired.

How to delegate in five steps

A proper handoff takes about eight minutes. A Slack message saying "can you take this?" takes eight seconds and costs you three weeks. Run these five every time and it stops needing thought.

1. Choose the right person and the right size. Match the task to someone standing near it, and size the slice to what they have actually pulled off before. Unproven? Smaller piece, closer support. Experienced? Give them the whole thing and stop fussing.
2. Brief the outcome, not the steps. Say what done looks like, why it matters, and how you will judge it. Then shut up about the how. The how is theirs. That is where ownership actually comes from - not from a pep talk about ownership.
3. Set the guardrails. The lines that cannot be crossed: the budget, the date, who must be looped in, what needs your signature. Inside the lines, they decide. Outside, they come to you. That is how you keep control without standing behind anybody's chair.
4. Agree checkpoints up front. Pick the review dates together, before a single thing gets done. A booked check-in on Thursday replaces four anxious "just checking in!" pings on Tuesday. It also lets you catch a drift while it is still small.
5. Step back, then debrief. Let them run it. Afterwards, talk about what worked and what was horrible, so next time you can hand over something bigger. And do not silently fix their work at 11pm. Silent fixes teach nothing, and they breed people who wait to be rescued.

Common delegation traps

• Dumping, not delegating. No context, no guardrails, no checkpoint - and then genuine surprise when it comes back wrong. That is abdication wearing delegation's clothes.
• Delegating the task but keeping the authority. If they have to ask you about every small thing, you have not delegated anything. You have added a relay leg to your own job and called it empowerment.
• Taking it back at the first wobble. It gets shaky, you grab it, you tell yourself this is faster. And it is, once. You have also just taught the whole team that bringing you a problem makes the problem vanish. They are quick learners. They will be back.
• Over-checking. Asking for updates so often that the person spends more time writing status than doing the work. You agreed the checkpoints. Wait for them.
• Delegating only the boring work. Push down all the drudgery, keep all the interesting bits, and your best person will be gone by March. The stretch has to flow down too. So does the credit.

Delegation is a behaviour, not a checklist

Now here is the bit the listicles leave out, including, if I am honest, most of the one you have just read. You can agree with every word above and still freeze on Monday, when there is a real task in front of you, a real deadline, and a real person who might make a mess of it. Delegation is not knowledge. It is a behaviour. And behaviour is only ever built under pressure, when the result matters and you genuinely cannot do it all yourself.

Reading about letting go changes nothing. Being made to let go, watching what happens, and feeling exactly how much that one held-on-to decision cost you two rounds later - that changes something. That is the whole idea behind the Put The Player First framework and every game I design: build the situation, let the real behaviour walk in, then name it in the debrief while everybody still remembers it.

One simulation does this almost too well. Chaos in the Kitchen puts you in charge of a kitchen during service. Orders land, things go wrong, information is incomplete, and the clock does not care about your feelings. Managers who keep every decision get buried under their own station. The ones who hand off, set priorities and trust their people get through the rush. Nobody has to explain the lesson afterwards. Their shoulders explained it already.

For the bigger picture on building leadership behaviour this way, start with my guide to serious games for leadership development.

Give away the outcome. Keep the guardrails. Book the check-in. That is the whole thing, and it fits on a napkin.

Frequently asked questions

Basics

Why do managers struggle to delegate?
Because handing work off is slower today than doing it yourself, and today is very loud. Add the expert habit, a bit of perfectionism, and no hour set aside to teach anyone anything, and delegation loses to the urgent every single week. Treat it as an investment that pays back over weeks, not as a favour you do when you happen to have a quiet afternoon. You will never have a quiet afternoon.

What should I delegate and what should I keep?
Delegate recurring work, anything teachable, and anything that would stretch somebody. Keep direction, hiring and firing, the sensitive people calls, and the rare decisions that are expensive and cannot be undone. Frequent, teachable or developmental, it leaves your desk. Rare, sensitive or irreversible, it stays.

How to

How do I delegate without losing control?
Hand over the outcome and the decision rights, then control the thing through guardrails and booked checkpoints instead of constant oversight. You own the result and the boundaries. They own everything inside them. Control the edges of the box, not the movement within it.

How do I delegate to someone who is not ready?
Smaller slice, clearer brief, earlier check-in. Then widen it as they prove they can carry the weight. Nobody is ever ready in advance - readiness is built by being trusted with something slightly too big. So start small rather than not at all.

Traps

What is the most common delegation mistake?
Chucking a task over the wall with no context or guardrails, and then grabbing it back the moment it wobbles. The first teaches nothing. The second teaches your team that bringing you a problem makes the problem disappear. They are quick learners. They will 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

With love from Bengaluru, this is Arvindh saying over and out.