Why Do My Managers Keep Escalating Problems They Should Be Able to Solve?

First distinguish escalation from appropriate consultation

Not every upward conversation is a failure. A manager may quite reasonably seek input where there is: serious safety risk; legal exposure; ethical concern; major financial consequence; something genuinely outside their authority; a significant crisis; or a situation beyond their current experience.

Good judgement includes knowing when to involve someone more senior. The problem is when ordinary managerial decisions routinely travel upwards too. Ask: whose decision is this? This is the simplest starting point. When a manager brings you an issue, ask:

“Whose decision should this actually be?”

Yours? Theirs? Another function's? The leadership team's? If nobody is clear, the escalation may be completely understandable. Many organisations have responsibility charts without real decision clarity. People know what their job title is. They do not know what they are actually authorised to decide.

Unclear authority produces escalation

Suppose a manager is told:

“You own customer service.”

But they do not know whether they can: approve a refund; offer a credit; change a process; say no to a customer; deal with a staff issue; or make an exception. What will happen? They ask. Again. And again. Then leadership complains that they lack ownership. Before criticising escalation, clarify authority.

Responsibility without authority creates dependence

You cannot sensibly say:

“You're responsible for this result.”

while retaining every meaningful decision needed to produce it. That creates pseudo-ownership. The manager carries accountability if it goes wrong. The senior leader still controls what can be done. Of course they escalate. If you want decisions to stay lower in the organisation, decision rights have to move lower too.

Managers escalate when they are frightened of being wrong

This is another major cause. The manager may know what they think. But they are not confident enough to own the consequence. So they ask:

“What would you do?”

Or:

“Can I...?”

Or:

“I just wanted to check.”

Sometimes that is appropriate. Sometimes it is fear disguised as consultation. The development question is:

“What do you think?”

Ask for the recommendation

Do not answer the problem immediately. Ask:

“What do you recommend?”

If they say: “I don't know,” keep going.

“What options do you see?”

“What are the risks?”

“What would you do if I weren't here?”

“What's your best judgement?”

Now you can see whether the escalation is caused by lack of thinking or lack of confidence. Those are different problems.

Do not reward escalation with an instant answer

This is where leaders create the pattern. Manager brings problem. Senior leader immediately gives answer. Manager leaves. What did they learn? Bring problem upwards → receive answer. Very efficient. Very dangerous. Next time, same thing.

If you want different behaviour, change what happens when the escalation arrives. Don't bring me problems. Bring me your thinking. That is a much better standard. If something genuinely needs senior input, ask the manager to bring: What is happening? What evidence do you have? Why does it matter?

What have you already done? What options do you see? What are the risks? What do you recommend? Now escalation still develops judgement. They are not simply acting as a courier for the problem.

The deep-well problem

I sometimes think of a manager arriving at the top of a deep well. There is a problem down there. The leader can climb into the well with them and start wrestling with it. Or stay at the top and ask questions. What can you see? What are your options? What have you tried? What do you think will work?

The leader can throw down a rope. They do not necessarily need to climb into the well. That is the difference between helping someone think and taking the problem over.

Beware the court of appeal

There is another form of escalation. An employee does not like their manager's answer. So they go higher. The senior leader listens and changes the decision. What did everyone learn? The employee learned:

“If I dislike the answer, appeal.”

The manager learned:

“My authority can be bypassed.”

The senior leader became the real manager. Do this repeatedly and you destroy the layer beneath you.

Ask whether the issue has already been discussed with the manager

When somebody skips a level, ask:

“Have you discussed this with your manager?”

If not, why not? There may be a legitimate reason. But often the right response is to send the issue back to where it belongs. That preserves managerial authority.

Do not casually overturn your manager

Sometimes their decision genuinely needs changing. Fine. But involve them. Understand how they reached the decision. Explain what they missed. Help them improve the reasoning.

If you simply overrule them in front of everybody, you have reduced their authority and increased the chance that future decisions will be escalated.

Escalation grows in inconsistent organisations

Imagine one manager makes a decision. It is supported. Another makes a similar decision. It is overturned. A third is criticised for not asking first. What will people do? Escalate everything. Because nobody knows which decisions are safe to make. Consistency in decision boundaries matters.

People notice what leaders punish

If a manager once made a reasonable judgement call and was told:

“Why didn't you ask me first?”

they may remember that for years. Now the leader asks:

“Why won't they decide anything?”

Because they learned the rule. You may need to consciously teach a new one:

“This sits within your authority. I expect you to make the call.”

Explain what “use your judgement” actually means

That phrase can be unhelpfully vague. Give people a framework. Consider: the evidence; the customer impact; financial consequence; people impact; risk; precedent; values; authority; and reversibility. Then make the best sensible decision. Judgement becomes easier to exercise when people understand what should inform it.

Not every decision needs perfect certainty

Some managers escalate because they want somebody else to guarantee the answer. That guarantee rarely exists. Business decisions often involve incomplete information. The job is not to eliminate uncertainty. The job is to make a sensible judgement with the information available. That capability needs practice.

Let people make recoverable decisions

A useful question is:

“If this decision is wrong, can we recover?”

If yes, perhaps the manager should make it. Low-risk, reversible decisions are excellent places to build judgement. You do not need senior approval for everything merely because the outcome is not guaranteed.

Escalate irreversible or high-consequence decisions more readily

By contrast, if a decision creates serious legal, safety, ethical or financial exposure, more senior involvement may be sensible. The point is not:

“Never escalate.”

The point is:

“Escalate intelligently.”

Create escalation boundaries

Managers should know:

Decide yourself

Ordinary decisions within the role and agreed authority. Consult Situations where another perspective would materially improve the decision. Escalate Issues with significant risk, impact or authority implications. That simple distinction can reduce enormous amounts of unnecessary upward traffic.

Ask whether the manager has enough information

Sometimes escalation happens because information is fragmented. The manager cannot see: the commercial position; the customer history; the policy; the financial data; the previous decision. Then the problem may not be confidence. It may be access. Better information can reduce unnecessary escalation.

Ask whether the manager has the skill

Perhaps they genuinely do not yet know how to handle: performance conversations; commercial decisions; conflict; customer negotiation; or prioritisation. Fine. Then this is a development issue. Coach them. Do not simply absorb the work indefinitely.

Use one-on-ones to build judgement

One-on-ones are an ideal place to review escalations. Ask:

“What came to me this month that you think you could handle next time?”

Then unpack it. What did they miss? What authority do they need? What did they learn? What will they do differently? That turns escalation into development.

Track repeated escalation

If the same kind of issue repeatedly reaches you, notice the pattern. Maybe: all customer complaints; all staffing conflicts; all pricing decisions; all operational exceptions. Ask:

“Why does this category keep reaching me?”

Perhaps the system or authority boundary needs changing.

Turn repeated escalation into a system question

If twenty similar decisions come upward, do not solve twenty decisions separately. Ask:

“What rule, authority or process would allow managers to handle most of these themselves?”

That is how the business gets stronger.

Teach managers to own recommendations

A manager who says:

“Here are the three options and I recommend B because...”

is thinking differently from one who says:

“What should we do?”

Even if the final decision still belongs to you, insist on the recommendation. The thinking is part of their job.

Language is a clue

Listen for:

“Can I...?”

versus:

“I'm going to...”

Listen for:

“What should I do?”

versus:

“This is what I recommend.”

Listen for:

“We've got a problem.”

versus:

“This is the issue, this is the evidence, and this is how I think we should handle it.”

Language reveals ownership.

Stop becoming the oracle

Leaders often become victims of their own competence. Everybody asks. You always know. So you keep answering. Eventually the organisation becomes extraordinarily skilled at consulting you. That is not necessarily a compliment. Your objective should not be to become the oracle. It should be to build people who increasingly know how to think without you.

Escalation consumes senior capacity

Every unnecessary escalation has a cost. A decision that should take ten minutes at manager level may consume thirty minutes of senior-leader time. Multiply that across a week. Then senior leaders complain they have no time for strategy, growth, customers or development. Perhaps their calendar is full of decisions that should never have reached them.

Ask why the business still needs you for this

This is a powerful senior-leadership question:

“Why did this need me?”

Authority issue? Capability? Confidence? Information? Poor process? Habit? Politics? Risk? The answer tells you what needs fixing.

Do not confuse availability with good leadership

Being approachable is good. Being available for everything is less useful. A leader can be supportive without becoming the default destination for every uncertainty. Accessibility should not remove responsibility.

Sometimes you need to say: this is yours

If the decision clearly sits within the manager's role, say:

“This is your decision.”

Then perhaps add:

“Talk me through how you're thinking about it.”

That gives both ownership and support.

Follow up afterwards

If they make the call, come back. What happened? What did you learn? Would you make the same decision again? That strengthens judgement. The purpose is not to abandon them after saying:

“You're on your own.”

Recognise good independent judgement

Someone handles something well that they previously would have escalated. Notice it. Say:

“Six months ago that would have come to me. You handled it well.”

That reinforces growth.

Do not punish every imperfect result

If you only praise decisions that produce perfect outcomes, managers will naturally become risk-averse. Review the quality of the reasoning too. Sometimes good judgement produces a poor outcome because uncertainty is real. That does not mean the decision should have been escalated.

A practical escalation test for managers

Before bringing something upward, ask: Does this sit within my authority? If yes, why am I escalating? What evidence do I have? Facts first. What have I already tried? Do not outsource the first move. What are my options? Think. What are the risks? Consider consequence. What do I recommend?

Own a view. What specifically do I need from my manager? Approval? Perspective? Information? Or am I simply asking them to decide? That last question is important.