A senior leader works sixty-hour weeks. Their inbox is never clear, their evenings go on reports, and strategic work keeps slipping to “next month”. Meanwhile their team is capable, under-stretched and slightly frustrated. Ask the leader why they don’t delegate more and the answer is usually some version of: “By the time I’ve explained it, I could have done it myself.”
That sentence is true in the short term and costly over any longer period. Delegation is one of the most common development themes for senior leaders, and it is rarely a question of not knowing how. Capable people find it hard for reasons that have more to do with confidence, identity and habit than with technique. This guide looks at why delegation is hard at senior level, what to keep and what to hand over, and how to delegate well enough that it sticks.
Why capable leaders struggle to delegate
- Speed. You are faster at the work than anyone else, because you have done it for years. Delegating means accepting it will take longer, at least at first.
- Standards. Other people won’t do it exactly your way. Some of the time their way will be worse, and some of the time it will be better.
- Identity. Many senior leaders built their reputation on being the person who gets things done. Letting go of the doing can feel like letting go of what made them valuable.
- Risk. If it goes wrong, you are still accountable. Holding on feels safer.
- Guilt. Your team is already busy. Adding to their load feels unfair.
- Habit. The work arrives on your desk, and dealing with it is easier than deciding who else should.
Each of these is understandable. Together, they create a leader who is overstretched, a team that is underused, and a function that can only move as fast as one person.
What to keep, and what to hand over
Senior leaders sometimes treat delegation as a question of offloading tasks they don’t enjoy. A better test is to ask where your judgement is genuinely needed.
| Keep | Delegate | Delegate to develop someone |
|---|---|---|
| Setting direction and priorities | Recurring operational decisions | Work slightly beyond someone’s current level |
| Decisions about senior people | Reports and analysis | Representing the function in a cross-team project |
| Relationships only you can hold | Meetings where you add little | Presenting to senior stakeholders |
| Issues with high risk to people or reputation | Work others can do to 80% of your standard | Leading a piece of change |
The middle column is where most of your time can be recovered. The right-hand column is where most of your team’s growth will come from.
Five levels of delegation
Much delegation fails because nobody agreed how much authority was being handed over. Being explicit removes most of the confusion.
| Level | What you say | When to use it |
|---|---|---|
| 1. Investigate | “Look into this and tell me what you find.” | New area, or the person is new to the work |
| 2. Recommend | “Look into it and recommend what we should do.” | Building someone’s judgement |
| 3. Decide, then tell me | “Make the call and let me know before you act.” | Trust is growing, stakes are moderate |
| 4. Act, then inform | “Go ahead and let me know how it went.” | Proven capability, routine risk |
| 5. Own it | “This is yours. Come to me if you need me.” | Full handover of an area |
Aim to move each piece of work up the levels over time. If something has been sitting at level one or two for a year, that tells you more about the delegation than about the person.
Matching the work to the person
Good delegation is as much about who as what. The same task can stretch one person well and overwhelm another. Before handing something over, think about what each person on your team needs next in their development.
| Where the person is | What they need | Good work to delegate to them |
|---|---|---|
| New to the role or the organisation | Confidence and context | Well-defined tasks at levels 1–2, with clear check-ins |
| Capable and reliable, but not stretched | Bigger scope and visibility | A recurring decision area at level 3–4, or a cross-team project |
| Ready for the next role | Experience of the role above | Representing you in senior forums; owning a piece of strategy at level 5 |
| Struggling with their current load | Focus, not more work | Delegate around them for now, and help them prioritise |
It also helps to say why you’re choosing someone. “I’d like you to take this because it’s good experience for the kind of role you’ve said you want” lands very differently from a task arriving without explanation.
Over time, aim to spread delegated work across the whole team. Relying on the same two capable people is efficient in the short term, but it burns them out and leaves everyone else under-developed.
How to hand over well
- Explain the purpose, not only the task. Why does this matter, and what does a good result look like?
- Agree the level of authority using the five levels above.
- Set the check-in points in advance, so you aren’t tempted to hover, and they aren’t left wondering when you’ll step in.
- Say what you’d like to hear about, and what you don’t need to.
- Make yourself available, then stay out of the way.
- Review the outcome together, including what you’d both do differently next time.
When delegated work goes wrong
It will, sometimes. How you respond decides whether people will take on responsibility again. Separate the outcome from the person, look at whether the brief, the authority and the support were clear, and fix the problem together. Taking the work back the first time something slips teaches everyone that delegation is temporary.
It is also worth remembering that your own early work wasn’t perfect either. Someone gave you the room to learn.
Checking in without micromanaging
Most delegation breaks down in the weeks after the handover. Leaders either disappear completely, or they keep checking in so often that the other person never really owns the work. Small changes in how you follow up make a big difference.
| Instead of… | Try… |
|---|---|
| “Where are you up to with that?” several times a week | Agreed check-in points set at the handover |
| Asking to see drafts of everything | Agreeing which outputs you need to see before they go out, and which you don’t |
| Correcting the work yourself | Giving feedback and letting them make the changes |
| Solving the problem they bring you | “What do you think we should do?” |
| Quietly redoing the work afterwards | Saying what you’d like done differently next time |
If you notice yourself wanting to check in more often than agreed, ask what you are actually worried about. It is usually a specific risk, and that can be discussed openly rather than managed through constant follow-up.
When your team is already at capacity
Sometimes the reason a leader doesn’t delegate is genuine: the team really is fully stretched. In that case, delegation on its own won’t solve the problem, because there is nowhere for the work to go.
The answer is usually to decide what the function stops doing. Look at the work across the team, not only yours, and ask:
- Which reports, meetings or processes would nobody miss if they stopped?
- What are we doing to a higher standard than anyone needs?
- What could be done less often?
- What belongs to another team, or could be shared with them?
Freeing even a few hours a week in your team creates room for the work you need to hand over, and often removes frustrations they have had for a long time.
What good delegation looks like six months on
Delegation is working when you can see these things happening:
- Decisions in delegated areas get made without you, and you hear about them afterwards.
- Your team brings you recommendations rather than problems.
- Two or three people have grown noticeably in confidence and capability.
- You have regular time in your diary for direction, relationships and thinking.
- When you take leave, very little waits for your return.
If only some of these are true, look back at your delegation audit and ask which pieces of work are still sitting at the lower levels, and why.
Common mistakes
- Delegating tasks but not decisions. If every choice still comes back to you, you’ve only delegated the typing.
- Delegating only the work you dislike. People notice, and it rarely develops them.
- Taking work back at the first problem.
- Redoing finished work to your own standard. Unless it genuinely matters, accept good enough and give feedback instead.
- Delegating to the same one or two people. It overloads your strongest people and leaves others undeveloped.
Your delegation audit
List the recurring work that takes up your time and decide what to do with each item. The first row shows an example.
| Task or decision | Hours per month | Who could own it | Starting level | Handover date |
|---|---|---|---|---|
| Monthly performance report | 10 | Operations manager | 2 – Recommend | End of this month |
If you lead other managers, How to Lead Through Other Leaders looks at the wider shift from doing the work to building the people who do it.
Not sure where your strengths and gaps sit as a leader? The free Leadership Readiness Assessment takes about ten minutes.
Working on how you lead?
I work one-to-one, online, with senior leaders stepping into bigger roles. Wherever you’re based, sessions are scheduled around your time zone.
The Lead With Clarity Programme is a 12-week coaching programme for leaders who want to lead with more clarity, confidence and impact. It combines one-to-one sessions with guided implementation weeks, so the changes happen in your actual role between sessions.
If your time is going to work that belongs to someone else, book a discovery call and we’ll look at what to change first.