Insights

Why Teams Stop Deciding and Start Escalating

By Moe Nawaz ·

Teams start escalating when asking a senior colleague feels like the safest way to get a decision that will stick. The manager may know what to do, but they’re less sure whether they have the authority, whether another department will go along with it or whether the founder will reverse it later.

Some decisions belong upstairs. A serious safety issue or a commitment outside an agreed limit should go straight to the right person. I’m interested in the ordinary decisions that rise through the business because nobody is quite sure what will happen if they make the call themselves. Those are the decisions that fill a founder’s diary without ever appearing on the founder’s job description.

Follow a decision from the moment it needed making

Suppose a customer asks to move a delivery forward. Sales wants to say yes. Operations knows it can do the work, but only by moving another order. The account manager has dealt with similar requests before and could explain the options. What they don’t know is who can accept the trade off between the two customers. They copy in their director, who asks the founder. The founder settles it over the phone before lunch.

The customer gets a quick answer, and the founder may reasonably think they’ve helped. At the next request, copying in the director looks like the obvious move. In time, the account manager learns to prepare a good case for the founder instead of making the call. The founder sees how often decisions come back and starts to wonder whether the team has the judgement to decide. Each side can point to what happened last time.

That’s an illustrative example. To find out what is happening in your own business, pick a decision from last week and ask the person closest to it to walk you through it. When did they first know an answer was needed? What did they already know? At what point did they decide someone else had to make the call? You’ll often learn more from that sequence than from asking the whole management team why they fail to take ownership.

How routine decisions become repeat escalations

  1. A manager faces a decision that affects another team.
  2. Unclear authority makes asking the founder feel safer.
  3. The founder settles it, and the immediate pressure passes.
  4. The next similar decision follows the same route.
The way you resolve today’s exception teaches people where to take tomorrow’s.

Ask what made escalation reasonable

There are several reasons a competent manager might ask for a decision. They may lack the facts. They may have the facts but lack authority to commit the business. Or they may have both and remember what happened when a colleague made a similar call. Those are three different conversations. Telling all three people to show more initiative leaves each of them dealing with the same conditions that prompted the escalation.

Start with information. If you expect an account manager to agree to an expedited order, can they see the delivery schedule and the cost of moving things around? Can they tell which promises have already been made to other customers? If discovering that takes four calls, asking the founder may genuinely be quicker. Let the manager use the same information you use and see whether they still need you to settle it.

Then look at authority. A manager can carry responsibility for a result and still have to ask permission to take the action that would deliver it. I’ve found it helps to distinguish the person who provides facts, the person who makes the call and the person who carries it out. Bain’s guide to better decisions makes a similar distinction in its RAPID framework. In a small team those roles may sit with one person. The useful thing is for everyone involved to know where the final say sits.

Finally, ask what people expect will happen after they decide. Amy Edmondson’s study of psychological safety and learning in work teams links the ability to take interpersonal risks with learning behaviour. It’s a useful lens here. If raising a doubt earns a public rebuke, or making an authorised decision earns an unexplained reversal, people have something concrete to remember. Ask them what happened the last time they acted without checking first.

Agree which decisions should travel upwards

Choose one recurring decision. Write down who decides, what information they need, who they should consult and which exceptions must come to you. A reasonable starting point might be that an operations manager can move a delivery if they can see the capacity, keep other customer commitments intact and stay within the agreed cost. If any of those conditions fails, give them a named person to contact. Test the wording against two recent cases. If you and the manager read it differently, you’ve found a problem before the next customer has to wait for an answer.

Take particular care when a decision affects two teams. “Agree it between yourselves” sounds reasonable until each team has a different target and neither can accept the cost of helping the other. Decide who has the final say across that boundary. Make sure the person can see the consequences on both sides. You can learn more about how those conflicts multiply as the business expands in Why Growth Adds Pressure Faster Than Clarity.

Make the escalations you keep easier to answer

A decision that genuinely belongs with you can still waste time on the journey. I’d ask whether the person escalating it can explain the choice in a few sentences. What needs deciding? By when? What would they do and what is the main risk? If their recommendation rests on a fact nobody has checked, you now know what’s missing. If you disagree with their judgement, you have something specific to discuss. The next escalation can be better because the manager understands how you reached your answer.

Watch the difference between consulting someone and getting their permission. The person with the final say on a delivery change may need the warehouse supervisor to confirm that the stock is ready. That check can be valuable even if the supervisor has no authority to change the order. Problems begin when everyone who supplies information ends up with an informal veto and nobody can tell when the consultation is finished. Agree which input is essential and give the decision owner a time by which to act. If someone has a formal right to stop the decision for safety or compliance reasons, make that explicit. A manager should be able to tell the difference between a colleague who must sign off and one whose advice they should hear.

Watch what happens when the team chooses differently

The most revealing moment comes when somebody makes a decision within the agreed limits and you would have chosen differently. Ask them what they knew, what options they considered and what they’ll watch now that the decision is made. If there’s a material risk they missed, address it. If you simply prefer another option, let the decision stand and review the outcome together. Your reaction is part of what the team will use to interpret the authority you’ve given them.

Try this with one category of decision for four weeks. Count the decisions made at the agreed level, the ones escalated and the ones you reopened. Track the time it took to get an answer, and look at what mattered to the customer or the business. If approvals are faster but complaints rise, review a sample together. The limits may be wrong, the information may be incomplete or the team may need more practice in one particular circumstance.

Ask the manager what they could now handle that would have come to you a month ago. Ask what still needs your involvement and why. If routine decisions move while important exceptions still reach you, you have evidence that authority is working as intended. That’s also useful evidence when preparing for succession or sale. A prospective successor can see who makes the decisions and what happens when they do. I explore that further in Exit Readiness: Can the Business Run Without You?.

The next time a routine decision comes back to your desk, pause before giving the answer. Ask what the person would do with the authority and information they have today. Then ask what they would need to make the next comparable decision themselves. The answer will often tell you exactly where to start.

Questions and answers

When should a team escalate a decision?

Escalate when the decision exceeds agreed authority, involves a material risk, or requires a trade off nobody at that level can make. Give the person receiving it the facts, the options, your recommendation and when an answer is needed.

Does a high number of escalations mean managers lack confidence?

It can, but first check what managers know, what they’re authorised to decide and whether their previous decisions were upheld. Confidence is easier to build when they have a real opportunity to decide and review the outcome.

How do I get fewer approvals without missing important risks?

Set clear escalation thresholds and review outcomes. Keep an eye on the escalations you would expect to see as well as the ones you want to reduce. A quieter inbox only helps if people still bring serious exceptions to you.

Where should a founder start?

Pick one decision you’ve made repeatedly this month. Give a named person the information and authority they need to handle the next few cases. Agree the exceptions and a review date before you begin.

Further reading

I explore why capable leaders end up carrying too much in The Strategic Architect. Find The Strategic Architect on Amazon.

Back to Insights ↗