The Escalation Trap: Why “Just Ask Your Manager” Is Quietly Wrecking Your Team
A pointless escalation is a low stakes, low ambiguity decision kicked up to a manager out of habit, fear, or a culture that trains people to distrust their own judgment. It is not a real risk or a genuine cross team conflict. The fix is leaders pushing back and sending people to resolve issues directly first.
Somewhere in your organization right now, a capable adult is sitting on a decision they already know the answer to, because they are waiting for someone with a fancier title to say it back to them.
That is the pointless escalation, and it is not the kind that surfaces a real risk or a genuine cross team conflict, since those escalations are healthy and often necessary. The pointless kind is a low stakes, low ambiguity call that gets kicked upstairs anyway, out of habit, out of fear, or because the culture has quietly trained people to distrust their own judgment, even though nobody involved is actually missing information or expertise. What is really being requested is permission, and when permission seeking becomes the default mode of operation, that is a symptom rather than a process.
1. What a pointless escalation actually looks like
It rarely announces itself as pointless. It usually shows up dressed as diligence:
- “Just want to double check before I…”
- “Can you approve this real quick?”
- “I have a preference but wanted to run it by you first.”
- A Slack thread where three people already agree, but nobody will move until a manager says “approved.”
None of these are urgent, none of them are high risk, and none of them require expertise the requester does not already have.
2. The cross team complaint that skips the conversation
One of the most common versions of this pattern happens between teams rather than within them. Team A feels that a decision made by Team B has negatively affected their work, so instead of raising it with Team B, they take the complaint straight to management. The leader then hears a one sided account of a conflict that has not actually happened yet, because nobody has spoken to the other side.
A good leader should push back on this immediately by asking a simple question: what did the other team say when you raised this with them or asked them to review the impact? If the answer is that they have not spoken yet, the leader should say so plainly and send them back to have that conversation first. It is not a leader’s job to carry debates across the organization on behalf of people who have not attempted to resolve them directly. That kind of escalation does not save time, it just relocates the first conversation to a more expensive room.
This rule is for ordinary operational disagreement, not for everything that crosses a team boundary. It should not be applied to suspected fraud, harassment, discrimination, retaliation, serious misconduct, security incidents, whistleblowing, safety concerns, or situations involving a real power imbalance between the parties. In those cases, sending someone back to sort it out directly with the other side can itself be harmful, and a leader or the appropriate function should get involved straight away. The rule below is about protecting judgment on normal disagreements, not about withholding protection from people who need it.
There is also a real exception on the ordinary side. When the impact of a trade off is not obvious, or when the stakes are genuinely extreme, that is exactly the situation a leader exists to weigh in on, since picking between competing priorities across teams is part of the job. The distinction is not whether a conflict crosses a team boundary. It is whether the two teams have actually tried to work it out first, and whether the choice in front of them is one that reasonably requires someone with broader authority to make the call.
There is a version of this that is even worse. Some leaders do take the escalation forward to other leaders, which sounds like the responsible move, but they do it without telling the other leader where the escalation actually came from. The other leader is now holding a complaint with no source attached. They cannot go verify the details, they cannot ask a clarifying question, and they cannot weigh the complaint against the context the originating team could have supplied. What they end up with is an escalation they can neither act on nor safely ignore, which is not really a decision at all but a deadlock dressed up as one. Their only real options are to guess at what actually happened or to quietly let the escalation die, and neither of those outcomes resolves anything for the team that raised it in the first place. If a leader is going to carry an issue forward, the source has to travel with it, otherwise they are not escalating a problem so much as laundering it into something nobody can actually work.
3. Why it happens
People escalate unnecessarily for a fairly consistent set of reasons: they see escalation as a way to avoid personal blame if something goes wrong, they worry leadership will read a solo decision as a failure to be accountable, and even when they privately think an issue is minor, raising it still feels safer than owning the call.
None of these reasons are really about the decision itself. They are about transferring risk. Escalating is not just asking for input, it is handing someone else the liability for being wrong.
There is a name for this in the research literature. Defensive decision making is when someone knowingly passes up the option that is best for the organization in favor of the option that is personally safer, purely to avoid being blamed if things go wrong, and an experimental study of over three hundred managers found that the combination of low psychological safety and low authentic leadership causally increased this kind of defensive choosing, while a strong sense of psychological safety brought it back down. Escalating a decision you already know the answer to is a mild, everyday version of the same behavior, and it is not indecision so much as a rational response to an environment where being blamed for a decision costs more than the delay costs the organization.
That points to a sharper way of reading the pattern. Pointless escalation is often less a fact about the employee and more a fact about the incentive structure a leader has built. Every habitual escalator was trained by someone. If a person repeatedly asks permission for decisions that are genuinely theirs to make, there is a reasonable chance that somewhere in their history a decision of theirs was reversed, second guessed after the fact, or quietly redone, and they learned from it. The most damaging version of this is not created by weak employees. It is created by leaders who say someone is empowered and then, in practice, punish them for exercising that empowerment. After enough decisions get questioned or reversed, escalating first stops looking like a failure of nerve and starts looking like the sensible move. So when a leader complains that everyone brings them obvious decisions, the more useful question is not why the team will not think for themselves. It is what they have learned about what happens when they do, and whether their own past reactions to decisions are what taught the team that asking first is safer than deciding.
4. The energy cost nobody puts on a dashboard
Pointless escalations do not just cost the person waiting. They tax the whole system in a few specific ways.
First, latency compounds, since every hop up the chain adds queueing delay while the manager works through their own backlog, their own meetings, and their own inbox, and a five minute decision can easily become a two day wait.
Second, context has to be reconstructed. The person being escalated to usually knows less about the specific situation than the person asking. So they either rubber stamp the request without really evaluating it, or they spend real time getting up to speed on something the requester already understood fully.
Third, it scales the wrong thing. In organizations with centralized, single point decision making, every small call funnels through the same few people, and that bottleneck does not grow in proportion to headcount. It grows faster, because more people are now feeding the same narrow channel.
Fourth, it erodes trust in both directions. The employee reads constant check ins as evidence that they are not trusted, while the manager reads constant escalation as evidence that the team cannot handle ambiguity, and each interaction confirms the other person’s worst assumption while the cycle tightens over time.
None of this shows up as a single dramatic failure. It shows up as an organization that simply moves slower than the sum of its people should allow.
5. The deeper cost: outsourcing your judgment teaches you not to have any
This is the part that does not show up in a velocity metric, and it is the part worth taking seriously.
Martin Seligman and Steven Maier first described learned helplessness in 1967, after finding that animals who repeatedly experienced outcomes they could not control eventually stopped trying to escape, even once escape became possible again, and it is worth being precise about this research rather than stretching it, because Maier and Seligman themselves substantially revised the original theory decades later. Their own retrospective concluded that passivity following repeated uncontrollable events is better understood as an unlearned default response, and that what actually has to be learned is control, since learning that your actions matter is what switches off the passive response. So escalation culture does not literally recreate the original 1967 mechanism so much as it creates an organizational analogue of it, a system where people are given so few chances to exercise real control over outcomes that the passive default wins by default, because nothing in their day to day experience teaches them otherwise.
The workplace evidence for this is more direct than the animal research anyway. A meta analysis covering 319 studies and more than 151,000 participants found that job autonomy is associated with better job performance, working mainly through increased motivation and reduced strain, and that decision making autonomy in particular has the strongest motivational effect of any type of autonomy studied. A separate meta analysis of leader autonomy support found strong positive links to employees’ autonomous motivation, psychological need satisfaction, and wellbeing. Put together, the research says plainly that when people are given real control over decisions, they perform better and feel better, and when that control is removed, both motivation and performance suffer. Escalation culture is one of the most ordinary, everyday ways that control gets removed. Every decision quietly reassigned upward is one less rep at building the kind of learned control the evidence says people need.
There is a bitter irony here, because this pattern is usually driven by leaders trying to prevent mistakes. By treating every decision as high risk enough to need their sign off, they do not build a stronger team. Instead they train employees to believe the only way they can perform well is if someone senior is managing them the whole time. Constant correction and second guessing sends one message regardless of intent: stop trying, because your judgment does not matter here.
That is executive outsourcing in a sentence. It is an organization where thinking has been centralized into a small number of heads, and everyone else has been trained to fetch rather than decide.
6. How to actually prevent it
Underneath all of this sits a simpler problem than escalation itself, which is that nobody has actually agreed who owns the decision. Healthy teams tend to fall into one of three clear patterns: either one person decides and simply informs everyone else afterward, or one person owns the decision while others supply the information they need to make it well, or the two sides genuinely disagree and someone with broader decision rights is there to adjudicate. Dysfunctional teams collapse all three of those into a single reflex, which is to ask the manager, and the remedies below are ways of pulling those three patterns back apart.
6.1 Write down what does not need escalation
Most teams have an implicit sense of what is safe to decide alone, but implicit means everyone calibrates differently, and the most cautious people end up over escalating for the whole team. A short, explicit list, such as “under five hundred dollars does not need sign off,” “typo fixes ship without review,” or “customer refunds under a certain amount are the rep’s call,” does more to cut pointless escalations than any culture speech. If an issue does not meet the defined threshold, the decision gets made locally, executed, and simply documented afterward rather than deferred.
6.2 Make teams resolve ordinary disagreements directly first
Before a leader agrees to weigh in on a dispute between teams, they should ask what the other team actually said when the issue was raised with them directly. If the honest answer is that nobody has asked yet, the right response is to send them back to do that first, with the sensitive topic carve out from section 2 always in force. This protects the leader’s time for the disputes that genuinely need a tie breaker, and it forces both teams to actually understand each other’s constraints before anyone above them gets pulled in.
6.3 Answer low stakes escalations with a question, not a decision
When someone brings you a low stakes call, resist the urge to just decide it for them, and ask what they think you should do instead. Do not step in and do not answer the question outright, just ask what they would do and why, and if their answer is reasonable, hand the decision back to them fully theirs and let it stand once handed back, rather than quietly reviewing, correcting, or redoing it afterward. Saying someone is empowered to decide while still second guessing the outcome sends a contradictory signal, since people learn to trust the behavior over the words, and the pay off of doing this consistently is a team that brings you fewer of these calls over time, because they have actually built the judgment to make them alone.
6.4 Separate informing from asking
A large share of unnecessary escalations are really status updates wearing an approval request costume. Give people an explicit pattern such as proceeding unless there is an objection by a certain time. It preserves visibility for the manager without creating a blocking dependency.
6.5 Reward sound judgment and let reasonable decisions stand
If a well reasoned local decision that turns out slightly wrong gets treated the same as recklessness, you have just taught everyone to escalate defensively. Separate your feedback on process, meaning whether they thought it through and used good judgment, from your feedback on outcome, meaning whether it actually worked. People escalate less when they trust that a good decision will not be punished for a bad roll of the dice.
7. The real trade off
None of this means you should never escalate. Genuinely high stakes, high ambiguity, or cross boundary decisions should absolutely go up, since that is what the chain is for, and under escalating a real risk is its own expensive failure mode. This is also true for cross team disputes where the trade off is not obvious or the consequences are extreme, and it is always true for the sensitive categories flagged in section 2. Picking between competing priorities in those cases is exactly what a leader is there for. The goal is not zero escalation. The goal is restoring the judgment call to the level where the context actually lives, so escalation is reserved for the handful of decisions that truly need more eyes, more authority, or more risk tolerance than the person closest to the problem has.
Every time you let a good decision stand without relitigating it, you are not just saving your own time, you are teaching someone that their judgment is real, and if you do that consistently, escalations stop being a bottleneck and become a signal instead, reserved for the moments that actually deserve one.