Decision Escalation: Fear is a big driver, but not the only one

Estimated reading time: 8 minutes

For CEOs and transformation leaders who want faster decisions without gambling on heroics, this explains why escalation happens and how to redesign routing so people actually use it.

Decision escalation is the gap between the decision route on paper and the human logic in meetings. Fear is a major driver: when the personal downside of being wrong feels higher than the organizational upside of being fast, people escalate to protect themselves. Psychological safety matters because it reduces interpersonal fear and makes taking responsible risk possible. But escalation also happens when power overrides process, when incentives reward risk-avoidance or local optimization, and when decision categories are unclear. The fix is not more forums. It is safer accountability: explicit decision rights, guardrails, and escalation as a service with clear SLAs. That is how routing becomes a habit, not a diagram.

The steering committee moment where escalation becomes the default

You are in a weekly steering committee. Someone presents a “decision needed” slide.

The room gets quiet.

Not because it is complex. Because nobody wants to own the blast radius.

A director says, “We should align with Legal.”
Legal says, “We need InfoSec.”
InfoSec says, “We need Architecture.”
Architecture says, “This is a business call.”

Twenty minutes later, the decision is “escalate to the executive sponsor”. Everyone leaves relieved. Nothing is closed.

That is decision escalation in real life:
a social system for distributing risk, status, and accountability.

What decision escalation and decision routing actually mean

Decision escalation is when a decision moves upward or sideways because the decision owner does not feel able or safe to close it.

Decision routing is the operating rule that defines where a decision goes, who owns it, and how it gets closed.

Most transformations treat routing as a structural problem: committees, RACI charts, meeting cadence.

The human side is the real determinant: whether people believe they will be supported when they decide, especially when outcomes are uncertain.

That is why psychological safety matters. It is widely described as the ability to speak up and take interpersonal risks at work without fear of negative consequences.

The real drivers of escalation

Fear is big. But if you stop there, you will design the wrong fix.

1) Fear and defensive decision-making

Fear shows up as “one more review,” “we need alignment,” or “let’s take it to steering.”

In plain terms: when decision ownership is a career risk, escalation becomes the rational move.

Research on defensive decision-making describes this pattern: people choose personally safer options, not the best organizational option, and psychological safety can reduce that defensive behavior.

2) Power and status override the route

If a senior leader can routinely bypass routing, everyone learns a new rule: the fastest path is political sponsorship.

That destroys the credibility of decision rights, even if the taxonomy is perfect.

This is also why “empowerment” messaging often fails. People do not follow routes. They follow consequences.

3) Incentives and local optimization

Escalation is often a KPI move.

If Finance is measured on cost containment, it will escalate anything that looks like spend.
If Legal is measured on risk avoidance, it will escalate ambiguity.
If a function owns budget but not outcomes, it will escalate to protect budget authority.

The route becomes a battleground for control, not a mechanism for speed.

4) Ambiguity and category confusion

When the decision category is unclear, escalation becomes the default.

Teams are not saying “I refuse.” They are saying “I do not know which rules apply, so I want someone senior to absorb the ambiguity.”

This is why decision routing must be category-based, not project-based. HBR’s classic “Who Has the D?” argument is essentially this:

Clarify who recommends, who agrees, who decides, and who performs, decision by decision.

5) Past scars and institutional memory

After a failure, organizations add gates.

They call it governance. It is often trauma encoded into process.

Escalation becomes a habit long after the original incident is gone.

A simple diagnostic model: Fear vs Power vs Ambiguity

Use this in meetings to diagnose the real cause of escalation in under two minutes.

If you remove blame and escalation drops, it is fear.
Signal: lots of “I just want to be safe” language, vague accountability, heavy reliance on consensus.

If escalation persists even with psychological safety, it is power or incentives.
Signal: “We need VP approval” even when the category is clear; routes change based on who is in the room.

If the debate is about what the decision even is, it is ambiguity.
Signal: people argue about definitions, scope boundaries, and who owns what.

This matters because each driver requires a different fix.

Designing routing that survives humans

Here is the design goal: make accountability safe and predictable.

Design rule 1: Protect the decision owner

If ownership only comes with downside, you will get escalation theater.

Protection is not emotional support. It is operating clarity:

• Clear guardrails (what is allowed, what is not).
• A visible escalation path that is not punitive.
• A leader commitment to back decisions made within guardrails.

Psychological safety helps people speak up and act, but leadership behavior and norms are what make it real.

Design rule 2: Make escalation a service, not a punishment

Escalation should feel like help, not exposure.

Practical moves:

• Publish a simple escalation intake: category, decision statement, options, recommendation, risk, deadline.
• Enforce a response SLA by category (example below).
• Close decisions in writing, with the rationale and the guardrail used.

Design rule 3: Route by reversibility, not seniority

Not all decisions deserve the same friction.

Add one field to every decision: reversibility.

• Reversible decisions get fast routing and short SLAs.
• Irreversible decisions get deliberate routing.

This reduces fear because it reduces perceived blast radius.

Design rule 4: Stop chasing “alignment”. Define who must sign off.

When teams say “we need alignment,” they usually mean: nobody is sure who has the right to say yes.

That creates endless meetings and safe behavior, because everyone tries to avoid being the person who moved too fast.

Instead, be explicit about roles for each decision:

• Recommender: does the analysis and proposes an option.
• Decider: makes the final call.
• Sign-off (must approve): only the few people who can block the decision for a clear reason (risk, legal, security, budget threshold).
• Input: people who can advise, but cannot block.
• Doers: the team that executes once the decision is made.

Key rule: keep “must approve” very small.
If many people can block, the decision will always escalate or stall because it becomes political and slow by design.

A good test: if someone is not accountable for the outcome, they should not have veto power.

A weekly operating playbook

Use this to reset decision routing in an active program.

Step 1: Audit the escalations (30 minutes)

Pick the last 10 escalations and label each one:

• Fear
• Power or incentives
• Ambiguity
• Past scar

If you cannot label it, your routing is not explicit enough.

Step 2: Install decision SLAs by category (one page)

Example decision SLAs:

• Scope tradeoff within guardrails: 48 hours
• Vendor selection under threshold: 5 business days
• Risk exception: 10 business days
• Funding change: next steering, maximum 7 business days

The point is not speed. The point is predictability.

Step 3: Run a “decision closure” agenda every week

In your steering committee, stop “status reporting” as the main event.

Run this sequence instead:

1. Decisions closed last week (what guardrail was used)
2. Decisions stuck (what driver: fear, power, ambiguity)
3. Escalations requested (approve or reject the escalation)
4. New decisions entering the route (assign owner and SLA)

Step 4: Make bypass visible

Create a simple rule: if a decision bypasses the route, it must be documented with:

• who bypassed
• why
• what route was ignored
• what will change to prevent repeat

This is how you stop power from silently rewriting your operating system.

When this advice does NOT apply

• True crisis decisions where time is existential and the normal route is too slow.
• Regulated approvals where law or policy requires a specific authority.
• One-time existential bets (merger, major divestiture) where escalation is appropriate.
• Organizations with unstable leadership where no routing will stick until sponsorship stabilizes.

What to do this week

• Pull your last 10 escalations and label them fear vs power vs ambiguity.
• Rewrite one decision category with explicit owner, guardrails, and SLA.
• In the next steering committee, spend 15 minutes closing decisions, not reporting slides.
• Publicly back one decision owner who closes within guardrails.

That is how routing becomes behavior.

---

Related article

Your transformation is not stuck in tech. It is stuck in approvals

Facts that matter

• Psychological safety is commonly defined as being able to express opinions and take interpersonal risks at work without fear of negative consequences.
• Research on defensive decision-making argues that people may choose personally safer alternatives, and that psychological safety can mitigate defensive decisions under uncertainty.
• HBR’s “Who Has the D?” framework emphasizes clarifying decision roles to improve decision speed and execution consistency.
• Edmondson’s work links psychological safety to learning behavior in teams, which supports earlier surfacing of issues that otherwise trigger late escalations.

---

FAQ

Why do decisions escalate even when we have a RACI?

RACI often spreads accountability instead of concentrating it. When “Responsible” and “Accountable” are interpreted differently across functions, people protect themselves by escalating. You need a single decision owner per decision and explicit agreement points, not a shared responsibility cloud.

How do I tell if escalation is fear or politics?

If you promise no blame and the team becomes willing to decide, it is fear. If the team still wants a senior sponsor even when the category and guardrails are clear, it is power or incentives. If the room argues about what the decision is, it is ambiguity.

What should a steering committee do differently?

Stop being a reporting forum. Become a decision closure mechanism. Spend the first part of the meeting closing decisions and documenting outcomes. Treat escalation as an intake with SLAs, not as a vague “bring it next week” ritual.

Won’t decision SLAs create reckless decisions?

Not if you route by reversibility and guardrails. SLAs create predictability, not recklessness. The discipline is: reversible decisions move fast; irreversible decisions get deliberate review, with clear agreement points and a final owner.

---

Glossary

• Decision routing: The defined path that assigns decision owner, forum, and closure steps by decision category.
• Decision escalation: Moving a decision upward or sideways because it cannot be closed within the current authority or feels unsafe to own.
• Psychological safety: A climate where people can speak up and take interpersonal risks without fear of negative consequences.
• Defensive decision-making: Choosing options that reduce personal risk rather than maximizing organizational outcomes.
• Guardrails: Pre-agreed thresholds and principles that allow faster decisions without reopening fundamentals.

---

Executive Takeaways

• Escalation is usually a human logic problem, not a process problem.
• Fear drives many escalations, but power, incentives, and ambiguity drive the rest.
• Make accountability safe with guardrails, clear owners, and escalation SLAs.
• Route decisions by category and reversibility, not by org chart seniority.
• Turn steering committees into decision closure systems, not status theaters.