“We Should Have Known Before”: The Fear Behind Late Decision Escalations

Estimated reading time: 10 minutes

For leaders who want faster, cleaner decisions by making escalation safer, earlier, and more explicit.

Late escalation is rarely a competence problem. It is usually a human one. People keep issues too low in the organization because escalation often feels like exposure: “I failed,” “I lost control,” or “I’m bringing bad news.” So they wait, try to solve it quietly, and hope for more certainty. Then the issue lands in front of leadership late, heavier, and more political. That is when someone says, “We should have known before.” The fix is not more meetings or another approval gate. It is to redesign escalation as a normal part of governance. Define what must be escalated, by whom, by when, and with what evidence. Then leaders must reward early escalation publicly. Escalation is not weakness. It is disciplined risk routing.

Organizations don’t discover problems late. They authorize escalation late.

Michel Paquin

The sentence leaders say when the room gets quiet

I have heard this sentence in boardrooms, steering committees, and next to coffee machines.

“How come we have to decide about that now? We should have known before.”

Sometimes it comes out with frustration. Sometimes with disbelief. Sometimes almost as a complaint against the organization itself.

But the sentence is usually pointing at the wrong problem.

Most of the time, the organization did know before.

Someone saw the signal. A dependency was slipping. A vendor answer did not match the original assumption. A pricing exception started spreading. Legal uncertainty appeared. A decision that looked local was becoming cross-functional.

The issue was not invisible.

It just stayed too low for too long.

And that is where I think many leaders misread what is happening. They assume the delay came from weak process discipline, poor project management, or lack of ownership. Sometimes that is true. But very often, the real cause is more human and more uncomfortable:

fear of escalation.

Not dramatic fear. Not panic.

Just the quiet, ordinary fear that shows up in organizations every day:

• fear of looking incompetent
• fear of being blamed for noise
• fear of escalating too early
• fear of triggering politics
• fear of losing control of the issue once it moves up

That fear is enough to keep a decision at the wrong level long after it should have moved.

What late escalation really means

Late escalation is when a team keeps a problem, risk, or decision below the right decision level beyond the point where local handling still makes sense.

An escalation is the formal movement of a decision or risk to a higher authority, wider forum, or different owner because the issue no longer fits the current decision boundary.

That matters because many teams do not delay escalation out of laziness. They delay it because escalation carries a social cost.

In theory, leaders say they want transparency.

In practice, many organizations still teach people that bringing a problem upward means one of three things:

1. you could not solve it
2. you created the problem
3. you are about to make someone uncomfortable

Once people learn that, they do what humans do. They protect themselves.

They gather more data. They wait for one more conversation. They try one more workaround. They soften the message. They present half of the risk instead of the whole thing. They keep the issue alive at a lower level even when it no longer belongs there.

Then leadership receives a “sudden” issue that was not sudden at all.

The hidden mechanism: escalation feels like identity risk

This is where governance people sometimes miss the human layer.

A decision framework does not operate on logic alone. It operates inside status, emotion, memory, and hierarchy.

When someone escalates, they are not only moving information. They are taking an interpersonal risk.

Psychological safety is commonly defined as a shared belief that people can speak up with ideas, questions, concerns, or mistakes without being punished or humiliated. Amy Edmondson’s work helped establish that concept, and recent summaries from Harvard Business School and the National Safety Council still describe it in those terms.

That idea is usually discussed in the context of innovation or team learning. But it applies just as strongly to governance.

Because escalation is a form of speaking up.

It says: this is bigger than my lane.
It says: I need help, authority, or a broader trade-off.
It says: this may now affect someone more senior than me.
It says: we may have to revisit an assumption.

That is not operationally neutral. It touches identity.

And when identity risk is high, people delay.

Why your governance may be creating the problem

Many organizations do not have an escalation problem because people are weak.

They have an escalation problem because the governance design is weak.

A lot of governance models are very clear about forums, gates, and approvals. They tell people where decisions go once they are already formalized.

But they are vague on the moment that matters most:

When should a team stop holding the issue and escalate it?
If that trigger is unclear, escalation becomes emotional and political.

People start asking:

• Is this big enough yet?
• Will I be judged for bringing this now?
• Should I wait until I have the full answer?
• Does this need executive attention, or am I overreacting?
• Who will be annoyed if I raise it?

That is not governance. That is guesswork under pressure.

And guesswork under pressure always favors delay.

A simple model: the Escalation Trigger Map

One practical fix is to define escalation triggers before the next issue appears.

I call this an Escalation Trigger Map.

It is a simple rule set that tells teams when a decision must move up, sideways, or into a different forum.

1. Define the decision boundary at each level

Start with three levels if you want to keep it simple:

Level 1: Team decision
The team can decide locally if the issue is reversible, low impact, and contained within its scope.

Level 2: Program or cross-functional escalation
The issue must move if it creates dependency conflicts, timing risk, process exceptions, or cross-team trade-offs.

Level 3: Executive escalation
The issue must move if it changes commercial risk, customer impact, compliance exposure, investment, or strategic direction.

This alone reduces a lot of hesitation because people no longer have to interpret escalation from scratch.

2. Make the triggers explicit

Do not say “escalate material issues.”

That sounds serious, but it is useless.

Instead define triggers such as:

1. budget impact above a threshold
2. timeline slip beyond an agreed number of days
3. policy or compliance ambiguity
4. customer or revenue impact above a threshold
5. cross-functional conflict with no local resolution after a set period
6. repeated exception pattern, not just a one-off issue

Now escalation becomes observable.

3. Require a short escalation card

Not a deck. Not a ceremony.

Just a short card:

• What changed?
• Why can’t this stay at the current level?
• What options exist?
• What decision is needed?
• By when?
• What happens if no decision is made?

This changes the quality of escalation. It turns emotional urgency into decision-ready clarity.

4. Set an escalation SLA

An SLA, or service-level agreement, is the agreed time within which a forum or leader must respond.

This is crucial.

If teams know escalation disappears into a black hole, they will avoid it. If they know it will trigger a clear answer in 48 hours, 5 days, or the next defined forum, they will use it.

That is why governance speed is not only about who decides. It is also about how quickly the system acknowledges and closes escalated items.

Leader behavior matters more than leaders think

You can install all the rules you want. If leader behavior punishes escalation, the system will still stay silent.

This is the part I think leaders underestimate most.

The blocking signal is often not formal. It is behavioral.

A sigh in the meeting.
A visible irritation.
A sarcastic “and why am I hearing this only now?”
A public teardown of the person who brought the issue.
A habit of treating escalations as disruption rather than responsible risk routing.

People learn fast.

They remember the emotional consequence of the last escalation more than they remember the governance slide shown at kickoff.

Research reviews from CIPD conclude that psychological safety supports asking critical questions, seeking help, reporting mistakes, raising concerns, and offering suggestions. CIPD also notes that in psychologically safe environments, people focus less on self-protection and more on team goals and problem prevention.

That is exactly the mechanism here.

When leaders make escalation socially expensive, teams optimize for self-protection.

When leaders make escalation normal and respected, teams optimize for signal quality.

When this advice does not apply

There are cases where fear is not the main cause.

This article does not fully explain late escalation when:

• the organization truly lacks basic ownership and nobody knows who holds the decision
• incentives reward hiding bad news until after a milestone is protected
• the problem is not fear but overloaded governance with too many forums and too little authority
• teams are escalating correctly, but leadership is slow, inconsistent, or absent

Fear is a major driver. It is not the only one.

That is why the diagnostic matters. You need to know whether the blockage is emotional, structural, political, or simply operational.

What to do this week

If I were advising a leadership team on this this week, I would start here:

Step 1: review the last three “why are we hearing this now?” moments

Not to blame anyone.
To identify the real delay mechanism.

Ask:

• when was the first visible signal?
• who saw it?
• why did it stay where it was?
• what made escalation feel risky or unnecessary?
• what trigger was missing?

Step 2: define five escalation triggers

Keep them plain language.
Make them usable by managers and teams, not just PMO people.

Step 3: publish a one-page escalation card

Simple enough to use in ten minutes.

Step 4: set response expectations

Tell teams exactly what happens after escalation and how quickly they will get a decision or route.

Step 5: change the leadership script

Facts that matter

• Psychological safety is widely defined as a belief that people can speak up with ideas, questions, concerns, or mistakes without punishment or humiliation. Harvard Business School Online summarized Amy Edmondson’s definition on May 20, 2025.
• The National Safety Council uses the same core definition and explicitly ties psychological safety to speaking up about concerns and mistakes.
• CIPD’s evidence review says psychological safety enables people to ask critical questions, seek help, report mistakes, raise concerns, and offer suggestions. Published in 2024.
• CIPD also notes that in psychologically safe environments, people are less defensive and focus more on team goals and preventing problems instead of protecting themselves. Published in 2024.
• Harvard Business Review argued in 2023 that when employees feel free to speak up, organizations circulate local knowledge, widen useful ideas, and prevent collective tunnel vision.
• McKinsey says executives spend nearly 40% of their time making decisions and believe most of that time is poorly used, which shows how central decision quality and flow are to performance.

FAQ

Why do managers delay escalation even when they know the issue is growing?

Because escalation is rarely interpreted as a neutral act. It can feel like exposure, loss of control, or an invitation to scrutiny. If the culture treats escalation as failure, smart people will wait too long.

What is the difference between good escalation and over-escalation?

Good escalation happens when an issue crosses a clear boundary: risk, cost, customer impact, compliance, dependency, or strategy. Over-escalation happens when teams move routine decisions upward because roles, criteria, or confidence are unclear.

Can better process alone fix late escalation?

Usually not. Process can help, but leader behavior and emotional consequences matter just as much. If the system says “escalate early” but leaders punish bad news, the real rule is still silence.

What should leaders say when someone escalates early?

Acknowledge the behavior you want repeated. Thank them for raising it, confirm that the timing is appropriate, and move quickly to the decision needed. Early escalation should feel responsible, not embarrassing.

Is escalation always a sign that local decision rights are weak?

No. Sometimes escalation is exactly what good governance should produce. The issue is not whether escalation happens. The issue is whether it happens at the right moment, with the right evidence, into the right forum.

Glossary

Escalation
The movement of a decision, risk, or exception to a higher authority or broader forum because it no longer fits the current decision boundary.

Decision boundary
The limit of what a team or person is authorized to decide without moving the issue elsewhere.

Psychological safety
A shared belief that people can speak up, ask questions, raise concerns, or admit mistakes without humiliation or punishment.

Escalation trigger
A predefined signal that tells a team an issue must be moved upward or outward.

Decision SLA
The agreed time within which an escalated issue will receive a response, route, or decision.

Executive Takeaways

• Late escalation is often driven more by fear than by incompetence.
• If escalation triggers are vague, teams will delay and hope the issue stays local.
• Governance should define when escalation is required, not just where decisions go.
• Leader reactions teach the real escalation rules faster than any framework document.
• Escalation is not weakness. It is disciplined risk routing.

Suggested internal links