How Do I Stop Good Managers Becoming Bottlenecks?

Competence attracts dependency

People naturally go to the person who gives good answers. That is understandable. But if the manager continually gives the answer, they train the organisation to keep coming back. The better they are, the more work can accumulate around them.

Ask how many decisions still need this person

This is a useful starting point. Which decisions genuinely require their authority? Which require their judgement? Which come to them simply because:

“They always know what to do.”

Those are not the same thing.

A bottleneck often looks like a hero

The manager is: busy; responsive; valuable; constantly needed. People may say:

“We couldn't function without them.”

That sounds complimentary. It should also make you nervous.

Indispensability is not always evidence of leadership success

Sometimes it is evidence that the manager has not built enough capability around them. A strong manager should increasingly create more people who can: think; decide; solve; carry. Not more people waiting for the manager.

Look at what happens when they are away

This is one of the clearest tests. Do decisions stop? Does work queue? Does their phone light up? Do customers wait? Does the team say:

“We'll have to wait until they get back.”

That is bottleneck evidence.

Ask what has become dependent on them

Customer relationships? Technical knowledge? Approvals? Problem-solving? People decisions? Planning? You need to know where the dependency sits.

Not every dependency is bad

Some work reasonably belongs with the manager. The issue is concentration. If too much of the function requires one brain, one person or one sign-off, the business becomes fragile.

Start with decision rights

Good managers often accumulate decisions that others could make. Why? Habit. History. Lack of confidence below. Unclear authority. Ask:

“Who should really be deciding this?”

Push decisions to the lowest sensible level

Not recklessly. Sensibly. If an employee has enough: information; capability; authority, let them decide. That reduces queueing.

Stop making the manager the approval desk

Can I send this? Can I refund this? Can I order this? Can I roster that? Can I change this? If the answer is predictable, perhaps the rule should be clearer.

Use thresholds

For example: approve spend up to X; resolve customer issues within Y; make roster changes within Z. Now fewer routine decisions need the manager.

Capture recurring decisions

If the manager answers the same question repeatedly, ask:

“Can we turn this into a decision rule?”

That is how judgement starts becoming scalable.

Teach the reasoning, not just the answer

If the manager simply says: “Do X,” the employee learns one answer. If they explain: “Here is what I considered and why,” the employee begins learning judgement. That is much more valuable.

Stop letting the manager be the only person who knows

This is a major risk. Pricing logic. Customer history. Supplier issues. Technical fixes. If all of it sits in one person's head, the business is exposed.

Capture important knowledge

Not every thought. Important, recurring knowledge. What does somebody else need to know to act sensibly without them? That is the useful question.

Cross-train deliberately

Who else can: cover; decide; handle; understand? One person does not need to duplicate the manager completely. But enough capability should exist around critical work.

Build deputies where appropriate

Not ceremonial titles. Real backup. Who can carry the role for a week? Who can chair the meeting? Who can make routine decisions? That creates resilience.

Ask who the manager is developing

This is a critical leadership question. Who can do more because of them? If the answer is nobody, the bottleneck will continue.

Build shoulders

The manager should have people beneath them capable of carrying increasing weight. That is what I mean by building shoulders. Without shoulders, everything rests on one neck.

Look at how the manager responds to questions

Employee asks:

“What should I do?”

Manager answers instantly. Helpful. And reinforcing dependency. Try:

“What do you think?”

That one shift can reduce a surprising amount of future traffic.

Teach the manager to ask for recommendations

“What do you recommend?”

Not simply:

“What's the problem?”

This changes the quality of escalation.

Stop accepting empty escalation

If someone brings: “We've got an issue,” ask: What have you tried? What are the options? What do you recommend? The manager should not become the thinking engine for everybody else.

Watch whether the manager enjoys being needed

This is uncomfortable but important. Some very good managers get identity from indispensability. Everyone needs them. They feel valuable. Then they unconsciously resist building independence.

Ask whether they are creating capability or collecting dependence

That is a strong coaching question.

Look at their calendar

What fills the day? Approvals? Problem-solving? Customer issues? Team questions? If almost everything is reactive, they may already be the bottleneck.

Look at interruption volume

How often are they pulled away from important work? By whom? For what? Patterns matter.

Track repeat questions

If the same category keeps returning, fix the cause. Knowledge? Authority? Training? System? Do not simply get faster at answering.

Stop becoming proud of fast rescue

The manager says:

“They know they can always call me.”

Fine. But ask:

“Should they always need to?”

Accessibility is good. Dependence is different.

Define what should not come to the manager

This is often overlooked. People need clarity about what they can own themselves.

Define escalation rules

Come to the manager when: risk is outside authority; safety; legal; ethical; significant commercial impact; serious people issue. Everything else? Use judgement.

Give people enough information to decide

You cannot push decisions down while keeping information up. Access matters. Data. Context. Policies. If the manager knows everything and everyone else knows fragments, dependency is inevitable.

Visibility should move down too

Employees need enough evidence to manage their own work. Do not make the manager the only person who can see the score.

Use dashboards intelligently

Team members should know: what good looks like; how they are tracking; what matters. That reduces constant interpretation.

Make standards explicit

People ask managers constantly when standards are vague.

“Is this okay?”

“Is this good enough?”

Define What Success Looks Like. Then people can self-assess more.

Clarify roles

Sometimes bottlenecks are really role-clarity problems. Everyone asks the manager because nobody knows who owns what. Fix the ownership.

One owner per outcome

That reduces unnecessary upward traffic.

Improve handovers

Cross-functional confusion often finds its way to the strongest manager. Why? Because someone needs to join the pieces. Fix the handover rather than permanently using the manager as glue.

Stop making the manager the human connector

Sales tells manager. Manager tells Operations. Operations replies to manager. Manager tells Sales. Why? Can the functions talk directly? Build direct relationships.

Encourage peer-to-peer problem solving

Employee A has issue with Employee B. Do they need manager mediation? Perhaps not. Managers should not become the communications department for adults. Ask: have you spoken to them? This question works at every level.

Do not let every conflict escalate

Coach people to resolve appropriate issues directly. That frees the manager for higher-value work.

Meetings can create bottlenecks too

If only the manager can chair, interpret and decide, the meeting depends on them. Build wider capability.

Rotate some responsibilities

Let others: lead sections; present data; own actions; facilitate. That grows capability.

Make the Action Register visible to the team

Then follow-up does not all depend on the manager's memory. People can see their own commitments.

The manager should not be everybody's reminder system

“Did you do this?”

“Did you remember that?”

Adults need to own their commitments. Use the system.

Look at who closes loops

If the manager personally has to ensure every action finishes, the team may not be self-managing enough.

Build accountability into rhythm

Regular review. Visible owners. Due dates. Then the manager does not need to chase randomly.

Stop fixing every mistake personally

If the manager cleans up every error, people never feel the full responsibility. Support. Coach. But let people repair appropriate mistakes themselves.

Ask employees how they would fix it

That develops ownership.

Watch for reverse delegation

Employee has problem. Conversation ends. Manager now has the problem. Classic bottleneck. Who left carrying the ball?

Return the ball

“I’ll help you think it through. What are you going to do next?”

Simple.

Look at the manager's own boss too

Sometimes senior leaders reinforce the bottleneck. They praise the manager for knowing everything. Go directly to them for all information. Bypass the team. That makes the problem worse.

Senior leaders should ask for the system, not the hero

Instead of:

“Can Sarah fix this?”

ask:

“Who should own this?”

That changes the culture.

Do not bypass people beneath the manager

If the CEO always goes directly to the manager for every detail, the wider team stays invisible. Use the proper structure where practical.

Give credit to the team

The manager should not become the sole face of every success. Recognise others. That supports identity and ownership below.

Ask whether the manager is hoarding key relationships

Maybe all important customers only deal with them. That is risky. Introduce others. Share history. Build confidence.

Customer dependence matters too

Customers may say:

“I only want to speak to Sarah.”

Understandable. But build trust with more than one person. That protects the business.

Transfer relationships gradually

Joint meetings. Then employee leads. Manager supports. Then employee owns. Same development principle.

Do not wait for a crisis to create backup

Illness. Resignation. Holiday. Then suddenly you discover how much knowledge was concentrated. Build backup before you need it.

Use absence deliberately

Let the manager take a real holiday. Notice what happens. What breaks? What waits? That is diagnostic information.

Do not let them remain available all holiday

If they answer every question from the beach, you learn nothing. And neither does the team.

Create planned non-availability

Perhaps the manager deliberately steps out of a meeting. What happens? That can reveal dependence safely.

Look at what the team can do without them

Over time, that list should grow. This is evidence of good management.

The manager should work increasingly on higher-level issues

As team capability grows, their time should move towards: planning; development; systems; cross-functional work; future risk. Not more of the same small decisions.

The level of questions reaching them should rise

This is a powerful test. If ordinary questions disappear and more complex ones remain, good. If everything still comes to them, development has stalled.

Bottlenecks can be technical or behavioural

Sometimes employees lack skill. Sometimes they have learned that asking is easier than thinking. Know which.

Do not reward helplessness

If asking the manager always produces a fast answer, helplessness becomes efficient. Change the reward. Require thinking. But do not punish legitimate questions You still want people to ask when appropriate. The goal is not silence. It is better judgement.

A good escalation should contain thinking

Issue. Evidence. Options. Recommendation. That should become normal.

Recognise people who solve without unnecessary escalation

“You handled that well without needing me.”

That reinforces independence.

Recognise the manager who creates independence too

Do not only praise them for personal output. Praise: development; delegation; succession; systems. That tells them what leadership success looks like.

Change their performance expectations

If their KPIs only reward personal output, they will keep doing. Include management outcomes. Team capability. Succession. Improvement.

Ask who could cover them tomorrow

This is a practical succession question. If nobody, why?

Give people stretch before the manager is overwhelmed

Do not wait until the manager cannot cope. Build capability early.

Stop adding direct reports forever

Sometimes the bottleneck is structural. The manager has too many people. No amount of coaching fixes an impossible span. Review the design.

Look at layers and roles

Maybe another level of responsibility is needed. Team lead. Supervisor. But do not add hierarchy merely for decoration. Solve a real coordination problem.

Fix processes that route everything upward

Some systems themselves require unnecessary approval. Review them. Which controls still add value? Which are historical?

Remove old approvals

A business grows. Policies change. But approvals remain. Soon everyone waits for one person. Clear the clutter.

Automate where sensible

Some routine information or approvals may be systemised. Use technology where it genuinely reduces low-value manager work. But do not automate bad processes simply to make them faster.

First ask whether the step is needed

Then automate.

Build decision knowledge

When an unusual decision occurs, capture useful reasoning. Next time someone may be able to decide without escalation.

Do not document everything

Capture what is: important; repeatable; likely to recur. That is enough.

Review dependency explicitly in one-on-ones

Ask the manager:

“What still comes to you that should no longer need you?”

That is an excellent development question.

Then pick one thing

Move it. Do not try to redesign everything in a week.

A practical bottleneck audit

Ask: What decisions wait for this manager? What knowledge lives only with them? What problems repeatedly escalate to them? What customers depend only on them? What approvals could move down? Who could carry more? What recurring question could become a rule or system?

What work stops when they are away? Which relationships can be shared? What are they still doing because they have always done it? Those answers give you the work.

A practical anti-bottleneck plan