Your Team Is Not Slow. It Is Waiting for You.

You say you have delegated.

You have given people work. You have given them projects. You may even have given them targets.

But every exception, trade-off, risk, pricing decision, hiring choice, customer escalation and priority conflict still comes back to you.

That is not delegation.

That is task distribution with centralised control.

And it is one of the fastest ways to make a growing business slower, more dependent and more expensive to run.

You gave them the work. You kept the decision.

A leader can look at a team and see people who are busy, capable and committed. The team can look back and see a leader who still needs to approve every meaningful move.

Both things can be true.

Your team is not failing because it lacks effort. It is failing to move because the real authority still sits with you.

Someone can own a project without owning the decisions that make the project move. They can prepare the options, gather the facts, run the meetings and update the tracker. But if they are not allowed to decide what happens next, they are not leading the work. They are servicing your decision queue.

That queue becomes the operating system of the business.

It looks like this:

• A manager sees a problem but waits until the next leadership meeting.
• A commercial opportunity needs a trade-off, so it sits in a Slack thread until you are free.
• A client issue is obvious, but nobody will respond until they know your preferred wording.
• Two leaders disagree, so they escalate rather than resolve it.
• A small risk becomes a larger one because the person closest to it is waiting for permission.

Then you look at the backlog, the missed deadline or the slow customer response and ask why execution has stalled.

It stalled because it reached you.

Being informed is not the same as being in control.

Many leaders keep every approval because they tell themselves they need visibility. They do not want surprises. They want to protect the quality of the decision. They believe they are managing risk.

But there is a difference between being informed and making yourself the route through which every decision must travel.

If every piece of information has to become your decision before the work can continue, you have turned visibility into a bottleneck.

Your team notices this long before you do.

They stop using judgement because using judgement creates risk for them. If their decision is likely to be reversed, challenged in public or pulled back to you anyway, waiting becomes the safer option.

So they wait.

They wait for your view. They wait for your meeting. They wait for your answer to a question they could have answered themselves.

Eventually, you start calling them passive.

But passivity is often learned behaviour. You taught them that the safest way to operate is to bring the decision back to you.

More meetings will not fix a decision-rights problem.

The usual response is to add another management meeting, a longer approval process or a better reporting pack.

That does not solve the problem.

A meeting cannot compensate for unclear authority. A dashboard cannot make someone accountable for a decision they are not allowed to make. A more detailed update simply gives the bottleneck better information.

The work still stops with you.

The fix is not to tell your team to be more proactive. It is to make the operating rules explicit.

Start with the decisions that regularly come back to you. Not the theoretical decisions in an org chart. The real ones that delay work every week.

For each one, answer five questions:

1. Who owns the decision? One person. Not a group. Not “the leadership team.”
2. What can they decide without you? Be specific about the authority they hold.
3. What must be escalated? Define the thresholds: money, risk, customer impact, legal exposure or strategic consequence.
4. What information must they use? Good judgement is not guesswork. Give people the criteria.
5. What happens if they make a decision you would not have made? If the answer is punishment or public correction, you have not delegated. You have set a trap.

This does not remove leadership accountability. It puts it where it belongs.

Your role is not to be absent. Your role is to make the boundaries clear enough that your people can move without borrowing your authority every time pressure rises.

Your behaviour decides whether the new rules survive.

You can publish a decision-rights document tomorrow. It will not matter if you keep taking the decisions back.

The test comes in the moment someone makes a call you would have made differently.

Do you ask what they saw, what they weighed and what they will do next? Or do you step in, reverse it and show the rest of the team that authority was never really theirs?

Every time you reclaim a decision without examining the system around it, you reinforce the old pattern.

That is why delegation is not just a process problem. It is a behaviour problem.

Sometimes decision rights are unclear. Sometimes your team does not trust the process. Sometimes you have not built the capability you expect people to use. And sometimes you have never really released control.

You need to know which one is true before you try to fix it.

Measure whether the work moves without you.

Do not measure delegation by how many projects you assign.

Measure it by whether the work moves when you are not in the room.

Ask:

• Which decisions were made this month without escalation?
• Which decisions still returned to the top, and why?
• Where did people wait for permission that they should not have needed?
• What decision was reversed, and what did that teach the team?
• Is your leadership team solving problems together, or packaging them for you?

If every meaningful issue still arrives at your desk, you are not leading scale.

You are managing a queue.

The way out is not to work harder at the centre. It is to build a team that can decide, act and recover without needing you to be the answer to every question.