Escalation is Default?

It’s Tuesday. Ten minutes to go before the stakeholder call. A capable team member leans into your doorway with a document open on their screen. “Quick one. Can you just confirm this is okay before I send it?”

It’s not a big decision. It’s the kind of call they’ve made a hundred times and yet you can feel the air in the question: I’d rather you hold the risk. So you look. You suggest a tweak. You give the nod.

They leave relieved.

You stay behind with a familiar, slightly heavier feeling you can’t quite name. Escalation often looks responsible from the outside. It sounds like alignment. It signals care. It can even read as maturity: “I don’t want to get it wrong", and sometimes it is exactly that.

But there’s a version of escalation that isn’t about judgement at all.

It’s about safety.

It’s what happens after enough small moments where decisions came back up the chain, where ownership felt fuzzy, where the phrase “just this once” quietly became a pattern. No one announces it. It simply becomes the smartest move in the room.

Not because people can’t decide but because they’re not sure what will happen if they do.

In some workplaces, deciding is what earns you trust. You’re expected to make the call, take the outcome, and learn fast if you missed something.

In others, deciding is what creates exposure. Decisions are visible, reviewable, and often revisited. People have experienced a decision being “supported” in the meeting and quietly overridden afterwards. Or they’ve watched someone take a reasonable initiative and then get corrected in public for a detail they couldn’t have known.

When you’ve lived in that system, escalation isn’t hesitation. It’s competence. It’s reading the room. It’s a way of ensuring you don’t end up alone with a consequence you weren’t authorized to carry. This is where escalation becomes less a choice and more a reflex.

The reflex doesn’t always look dramatic. It looks like an extra “Just checking…” in Slack. It looks like a calendar invite with one more approver than necessary. It looks like a leader’s inbox slowly filling with decisions that used to be distributed through the team.

Over time, the leader starts to feel it too. They’ll say, “Why is everything coming to me?” and they’ll be right. The team member will be thinking, “Because last time I decided, it came back and bit me.”

Neither person is trying to undermine the other. They’re adapting.

Leaders adapt by stepping in earlier. They tighten controls, not out of ego, but out of pressure. The pace is fast, the stakes feel high, and it’s simpler to make the call than to clean up a misalignment later.

Team members adapt by escalating sooner. They sense that decisions “stick” better when they’re made higher up. They can feel which calls will be second-guessed. They learn where the invisible lines are, and they stop trusting themselves near the boundary.

The system recalibrates.

Slowly.

Quietly.

And then one day you notice the real cost: confidence doesn’t collapse. It thins. Decision-making becomes heavier than the decision itself. People start collecting evidence instead of making calls. They look for cover. They ask for “quick confirmation” not because they lack capability, but because they’re trying to locate authority. Leaders, without meaning to, become the bottleneck and the shield.

That’s when escalation starts to undermine the very thing it’s meant to protect. It doesn’t just slow the work. It changes the relationship people have with responsibility. If the safest path is always “take it one level higher,” then people stop practicing the muscle of judgement, and if they stop practicing it, they stop trusting it. When they stop trusting it, escalation becomes even more sensible.

A loop.

This isn’t about telling people to “stop escalating.” Escalation is sometimes exactly what good governance looks like. It’s also not about forcing decisions down to people who don’t have the authority, the information, or the support.

This is about noticing when escalation is happening because it’s easier than clarity.

When nobody is quite sure who owns the call. When “just this once” has happened enough times that “this once” is now the system.

If you’re seeing a lot of escalation in your team, it may not be a confidence problem at all. It may be a trust-and-clarity problem wearing a confidence costume. A question I’d invite you to sit with after the next “quick check” lands in your inbox:

When we escalate here, what risk are we trying to reduce and whose confidence are we quietly training to shrink?