How to delegate at work – and why most people get it wrong
There's a moment most leaders recognise. You're looking at your to-do list and something's been sitting there for three weeks. Not because it's difficult. Not because you've forgotten. But because you're the one doing it, when honestly – genuinely, obviously – someone else could.
And yet you haven't handed it over.
You've told yourself it'll be quicker to just do it yourself. Or that the briefing would take too long. Or that you're not sure anyone else would do it quite right. Or – and this is the honest one – that you feel a bit guilty about passing it on.
Sound familiar? I thought so.
Delegation is one of those things that almost everyone agrees is important and almost no one does well. And the reason isn't usually a lack of knowledge. It's a tangle of habits, instincts and guilt that keeps us busier than we need to be.
Why delegation is harder than it looks
The most common reason people don't delegate is that they've confused it with dumping. Handing a task to someone with no context, no clarity about what good looks like, and no support – that's not delegation. That's abdication. And it usually ends badly, which then becomes the evidence people use to justify doing everything themselves.
Real delegation is a skill. And like most skills, the first few attempts are slower and messier than you'd like. That's not a reason to stop. It's just the learning curve.
The second most common reason is guilt. Particularly for people who care about their teams – and if you're reading this, you probably do – there's a reluctance to add to someone's workload. But here's the thing: done well, delegation isn't adding to someone's plate. It's often one of the most useful things you can do for their development.
What delegation actually involves
In How to Be a Productivity Ninja, I talk about delegation as one of the key characteristics of working like a Ninja. Specifically, it connects to the ideas of ruthlessness and stealth – being clear about what deserves your attention and protecting that space.
The Ninja approach to delegation has a few simple rules:
Not everything is yours to do. The starting point is getting honest about which tasks genuinely require your specific expertise, judgement or relationships – and which ones are on your list simply because they landed in your inbox. The first category deserves your best attention. The second category deserves a good handover.
Clarity is everything. The quality of a delegation is determined almost entirely by the quality of the brief. What does the finished thing look like? What's the deadline? What decisions can they make without checking back with you? What's off-limits? The clearer you are upfront, the less you need to hover afterwards.
Trust takes practice. You can't build trust with a team if you never give them the chance to deliver. That means accepting that the first version of something might not be exactly how you'd have done it – and that's usually fine. The objective is the outcome, not the method.
The bottleneck problem
One of the things I see most often in organisations – and honestly, in myself when I'm not paying attention – is the leader as bottleneck. Everything has to come through them. Decisions queue up. Progress slows. People feel infantilised.
This doesn't happen because leaders are control freaks. It happens because being needed feels useful. Because when you're busy, busy feels productive. Because checking things gives a sense of oversight, even when that oversight is costing more than it's adding.
The question worth asking is: if you were away for two weeks, what would happen? If the honest answer is 'not much' – your team has real capability and you've built good systems. If the answer is 'everything would grind to a halt' – that's not a sign of your indispensability. It's a sign that delegation has some work to do.
A few things that help
A checklist or standard process for recurring tasks makes delegation enormously easier. If you can point someone to a clear set of steps, you're not explaining the same thing from scratch every time – you're building the kind of institutional knowledge that makes teams genuinely more capable over time.
Check-ins are fine. Hovering isn't. There's a meaningful difference between agreeing in advance when you'll review progress, and dropping into someone's work unprompted every few hours. The first is good management. The second is anxiety dressed up as diligence.
Feedback closes the loop. Once a delegated task is done, say what worked and what you'd want differently next time. Not a performance review – just a quick, honest debrief. That's how people get better, and how the next delegation becomes easier for both of you.
The bigger picture
Here's what I've found, after years of building a team and coaching people who lead them: the leaders who struggle most with delegation are often the ones who care most about doing things well. The instinct to hold on is, at its root, a quality instinct. It just needs redirecting.
Delegation, done well, isn't lowering your standards. It's creating the conditions for other people to meet them. And when that happens – when someone delivers something you weren't sure they could, and they're visibly proud of it – that's one of the best things about leading people.
Your job isn't to do the work. It's to make the work happen. There's a difference.
If you want to go deeper on attention management and how the Productivity Ninja framework can help you work out what's genuinely yours to do, How to Be a Productivity Ninja is the place to start. And the free Productivity Ninja course covers the practical system in bite-sized sessions.
Frequently asked questions
Why is delegation important at work?
Because your time and attention are finite, and not everything on your list deserves the same quality of both. Delegation frees you to focus on the work that genuinely requires your specific skills and judgement – while also developing the people around you.
How do you delegate effectively?
Start with a clear brief: what the outcome looks like, what the deadline is, and what decisions the person can make without checking back. Then trust the process. Check in at agreed points rather than hovering. Give honest feedback when the task is done.
What stops people from delegating?
Usually one of three things: the belief it's quicker to do it yourself (true in the short term, costly in the long term), guilt about adding to someone's workload, or a previous bad experience with unclear delegation. All three are addressable.
What's the difference between delegation and abdication?
Delegation involves a clear brief, appropriate support and agreed check-ins. Abdication is handing something over with no context and hoping for the best. The first builds capability. The second erodes trust.