Delegation is one of those management skills that sounds incredibly simple until you actually have to do it.
Give someone a task, explain what needs to be done and let them get on with it.
Except, in reality, it rarely works quite like that.
At The BCF Group, we see the same problem time and again when working with managers and leaders.
Tasks are delegated because they need to be done, because the manager doesn't have time to do them, or sometimes simply because they are jobs the manager doesn't want to do.
Assumptions are then made about the person receiving the task, and when the work doesn't come back in the way the manager expected, frustration follows.
Sometimes the manager ends up taking the task back.
Sometimes they become increasingly involved in every decision.
Sometimes the employee is left struggling because they were never properly equipped to do the job in the first place.
And then we call it a delegation problem.
We aren't always convinced it is.
Very often, it is a leadership problem.
The biggest mistake managers make is believing that delegation starts when you hand someone the task.
It doesn't.
Delegation starts much earlier, with the decision about whether that person is actually in a position to succeed.
Before delegating something, there are four things we believe managers should consider: capability, capacity, intent and desire.
Capability is relatively obvious.
Can this person actually do the task? Do they have the knowledge, skills and experience required?
Capacity is different.
Even if they can do it, have they got the time and resources to do it properly? A manager can easily create an impossible situation by delegating something to an already overloaded member of the team and then wondering why the quality isn't there. And if they don’t have capacity, what could you move to someone else from their workload?
Then there is intent.
Does the person understand what they are being asked to achieve and, importantly, why it matters? People are much more likely to take ownership of something when they understand the outcome rather than simply receiving a list of instructions.
Finally, there is desire.
Do they actually want the responsibility? Are they interested in developing this particular skill or taking ownership of this piece of work?
None of this means that a manager should only delegate to people who are already capable of doing everything perfectly.
In fact, delegation can be one of the best development tools available to a manager.
But there is a big difference between deliberately stretching someone and simply handing them something they aren't prepared to do.
One of the most dangerous words in management is "assume".
We assume someone knows how to do something because they've been in the organisation for a while.
We assume they've done something similar before.
We assume that because they're a good performer, they will automatically know how to handle a new responsibility.
Sometimes those assumptions are right.
Sometimes they are spectacularly wrong.
The problem is that the manager often doesn't discover the difference until the task is already underway.
This is particularly common when someone is being given a new responsibility as part of their development.
The manager sees potential and thinks, "They'll figure it out."
The employee sees a task they have never done before and thinks, "I'm expected to know how to do this."
Neither person necessarily says anything.
And that's when delegation starts to go wrong.
Good managers are willing to invest time upfront. They explain the outcome, demonstrate where necessary, talk through the boundaries, give the person an opportunity to ask questions and, where appropriate, allow them to practise before they are completely on their own.
That may feel like more work initially. It is.
But the purpose of delegation isn't to save time in the first five minutes. It is to create greater capability and capacity over time.
This is also consistent with how we approach learning at BCF.
Our Train the Trainer programme, for example, is deliberately practical.
Delegates don't simply hear what good training looks like and then get sent away to try it.
They practise, receive feedback, reflect on what happened and have further opportunities to apply what they've learned.
The approach is designed to develop capability rather than assume that knowledge automatically becomes competence.
Delegation should work in much the same way.
There is another side to poor delegation, and arguably it is even more common.
The manager delegates something, tells the employee they trust them to do it and then spends the next few days watching everything they do.
They ask for constant updates. They check every decision. They review every email. They change things that don't look exactly as they would have done them.
Eventually, the employee stops making decisions and starts asking the manager what they should do.
Then the manager becomes frustrated because, "They don't take enough ownership."
But what did we expect?
You cannot genuinely give someone responsibility while simultaneously taking away their autonomy.
There is nothing particularly empowering about being told, "You own this," while your manager is standing over your shoulder checking every move.
That's not delegation.
It's micromanagement.
And often it comes from a manager who genuinely wants to do the right thing.
They care about the outcome. They don't want the person to fail. They believe their involvement is helpful.
But there is a point where support becomes interference.
The challenge for the manager is learning to recognise where that point is.
One of the books we often draw on when discussing delegation is Ken Blanchard's The One Minute Manager Meets the Monkey.
The idea of the "monkey" is a simple but powerful metaphor for understanding responsibility.
Imagine an employee comes to their manager with a problem. The manager listens and says, "Leave it with me. I'll look into it."
The monkey has just moved from the employee's back to the manager's.
The manager may feel helpful. The employee may feel relieved. But the unintended consequence is that the manager has now taken responsibility for the next step.
Do this often enough and something interesting happens.
The manager becomes overloaded while the team becomes increasingly dependent on them.
Every problem comes back to the manager. Every decision requires the manager. Every difficult situation becomes something the manager needs to resolve.
Eventually the manager asks, "Why does everyone keep coming to me?"
The answer is often because we have trained them to.
Good delegation isn't about throwing responsibility at people and walking away.
It is about helping people develop the confidence and capability to carry their own responsibilities.
When someone comes to a manager with a problem, the answer doesn't always need to be theirs.
Sometimes the better question is, "What do you think you should do?"
Or, "What options have you considered?"
Or simply, "What do you need from me?"
The manager remains available, but the responsibility stays with the person who owns the task.
That is a very different relationship.
This is why we prefer the idea of regular catch-ups rather than regular check-ups.
A check-up can feel like surveillance. "Have you done it yet? Where are you up to? Can I see what you've done?"
A catch-up is different. It creates a space for support and guidance without taking ownership away.
"How is it going?"
"What have you discovered?"
"What's working well?"
"Where are you finding it difficult?"
"What options are you considering?"
"Is there anything you need from me?"
Those conversations give the manager an opportunity to reinforce positive behaviour, provide advice, challenge thinking and help remove obstacles.
They also create an early warning system.
If something is starting to go wrong, you don't need to wait until the deadline arrives to discover it.
You can help the person think through the problem while still allowing them to own the solution.
That distinction matters.
The purpose of the conversation isn't to make sure the employee is doing everything exactly as the manager would do it.
The purpose is to support them in achieving the agreed outcome.
Because they may not do it the way you would.
And that is okay.
Perhaps the hardest part of delegation isn't the conversation with the employee.
It's the conversation the manager has with themselves afterwards.
Once you have delegated something properly, you have to accept that it is no longer your task.
You may still be accountable for the wider project. You may still be responsible for the overall result. But that particular piece of work now belongs to someone else.
They need to own it.
They need to make decisions.
They need to experience the consequences of those decisions.
They need to learn from the experience.
And sometimes they need to do things differently from you.
This is where managers can struggle, particularly if they were previously very successful individual contributors.
They know how to do the work. They know the quickest route. They know what good looks like.
It can be incredibly tempting to step in.
But leadership isn't about proving that you can do something better than everyone else.
It's about creating an environment where other people can succeed.
That requires letting go of the need to control every detail.
Stephen Covey's The 7 Habits of Highly Effective People provides another useful way of thinking about this.
His Urgent/Important matrix is often used as a simple productivity tool, but we think it has a much wider application for managers.
It encourages us to think carefully about where our time is best spent rather than simply responding to whatever arrives in front of us.
That matters because managers can easily become trapped doing work that somebody else could be doing.
They tell themselves it is quicker to do it themselves. They don't have time to teach somebody else. They know they'll do it better. Or they simply don't trust anyone else to get it right.
All of those thoughts can be understandable.
But if you keep acting on them, you create a team that depends on you.
The question isn't whether you can do the task. The question is whether you should.
Sometimes the answer will be yes.
There will always be things that require your experience, judgement or authority.
But sometimes the better leadership decision is to delegate the task and use the opportunity to develop somebody else.
If you haven't read Covey's The 7 Habits of Highly Effective People, it remains one of the books we would recommend to anyone serious about becoming a better leader.
This is perhaps the biggest distinction managers need to understand.
Delegation is not giving people the jobs you don't want to do.
That's dumping.
Delegation is deliberately transferring responsibility for a piece of work to someone else and giving them the capability, capacity, clarity and support they need to succeed.
There is a huge difference.
When done well, delegation is one of the most powerful development tools a manager has.
It gives people opportunities to stretch themselves. It builds capability and confidence. It allows people to demonstrate what they can do. It creates greater ownership and accountability.
And, over time, it gives the manager the capacity to focus on the things that genuinely require their attention.
The best managers aren't necessarily the people who can do the most.
They are often the people who can create the conditions for other people to do more.
It will. That's part of the deal.
If you give people genuine responsibility, there will be occasions when something doesn't work.
A decision will be wrong. A deadline will be missed. The quality won't be what you expected.
The easy response is to take the task back.
"I knew I should have done it myself."
That may feel justified in the moment, but it can create a damaging cycle.
The employee learns that taking responsibility is risky. The manager learns that delegation doesn't work. The next time a similar task comes around, the manager does it themselves.
The cycle repeats.
Instead, we need to become curious about what happened.
Did the person have the capability?
Did they have enough time?
Was the outcome clear?
Did they understand what good looked like?
Did they have enough authority to make the necessary decisions?
Did they know when to ask for help?
Did the manager provide the right level of support?
Sometimes the answer will be that the employee made a mistake. That's okay. People make mistakes.
The question is what we do with the mistake.
A blame culture teaches people to hide problems.
A coaching culture encourages people to surface them, understand them and learn from them.
If we want people to take ownership, we have to make it safe for them to learn while they are doing it.
When you look at delegation this way, it becomes much more than a productivity technique.
It becomes a fundamental part of leadership.
The purpose isn't simply to get more work completed.
It is to build a team that is capable of achieving more without depending on the manager for every decision.
That requires an investment from the leader.
You have to choose the right person. You have to assess capability and capacity. You have to explain the outcome clearly. You may need to train and coach. You need to agree how you will support them. Then you have to step back sufficiently for them to genuinely own the work.
That last part is often the hardest.
But if you have chosen well, prepared well and supported well, you have earned the right to let go.
And that is probably the simplest test of whether you are really delegating.
Ask yourself: If I say I trust this person to own this task, do my actions demonstrate that I actually do?
Because delegation isn't about saying, "I trust you."
It is about creating the conditions in which someone else can take responsibility, make decisions, learn from the experience and ultimately succeed without you standing over them.
That is not just good delegation.
That is good leadership.
At BCF, we help organisations develop managers who can do exactly that: build capability, create ownership and give people the confidence and responsibility to perform without unnecessary management interference. Delegation is not simply a productivity skill. Done well, it is one of the ways leaders build stronger, more capable teams.
The BCF Group has been developing leaders, coaches, and trainers for over 25 years.
Our programmes focus on the practical skills that drive real behavioural change, from coaching capability to communication and leadership impact.
If you’re looking to build leaders who create ownership, not dependency, it starts here - get in touch