Why Does Everything Escalate to Me?

Review your calendar from the past five working days. Focus on decisions, not meetings: every approval, question, and problem that reached you because no one else resolved it.

Count them.

If the number exceeds ten, this signals a problem. If it is over twenty, you are likely compensating by working late, responding on weekends, and rationalising this as necessary leadership.

Now filter that number. How many of those decisions genuinely required your judgement? Not your preference. Your judgement. Where your specific knowledge, authority, or experience was the irreplaceable ingredient.

The number that survives that filter is smaller than expected. Often by a factor of three or four. The rest arrived because the organisation has learned, through repetition and reinforcement, that routing decisions upward is safer than owning them.

What you are looking at is the Escalation Trap.

The Escalation Trap is a structural leadership problem in which decisions consistently flow upward to the most senior person in the room, regardless of whether that person has the right information, authority, or bandwidth to make them. It is not a delegation failure. It is a system design failure. The trap closes when the pattern becomes self-reinforcing: leaders who step in to resolve escalations inadvertently signal that escalation works, which increases future escalation.

Three conditions sustain the Escalation Trap: ambiguous decision rights, a cultural or hierarchical expectation that seniority equals responsibility, and an absence of explicit escalation criteria. Removing any one of the three breaks the pattern.

What the Escalation Trap Actually Is

The escalation trap is a self-reinforcing pattern where a leader’s competence becomes the organisation’s dependency. The better you are at solving problems, the more problems get routed to you. The more problems you solve, the less your team practises solving them. The less they practise, the more they escalate. The cycle accelerates quietly until the leader is the single point of failure for decisions that should never have left the floor they originated on.

This differs from poor delegation. Delegation is a skill that can be addressed through training. The escalation trap is a structural problem rooted in team behaviour. It persists even with capable hires, because the system incentivises escalation. You are faster, safer, and more predictable than making a decision and risking being wrong.

The pattern is expensive. McKinsey finds decision-making consumes up to 70% of some executives' time, and 61% say most of that time is spent ineffectively. Across roughly 1,200 global organisations, the same research put the cost of inefficient decision processes at about 530,000 manager-days a year for a typical Fortune 500 company. Deloitte's research reached a similar conclusion from the other direction: companies with clear decision rights consistently achieve higher revenue growth. The pattern compounds.

The leader experiences this as being overwhelmed. The team experiences it as being disempowered. Neither party chose it. Both are maintaining it.

The Identity Problem Underneath

Here is where the standard delegation advice falls apart.

If escalation were simply a structural problem, you could fix it with a RACI matrix and a few conversations about authority thresholds. Sometimes that works. Often it does not. The leader redesigns the decision framework, communicates it clearly, and within three weeks the same decisions are arriving on the same desk through slightly different channels.

Your success was built on your ability to solve problems. Early in your career, this approach was rewarded. Promotions followed your thoroughness, your ability to identify issues others did not see, and your competence in addressing challenges.

The escalation trap reinforces this identity. Each decision you receive affirms your central role. Letting go of escalation goes beyond process change. It requires redefining your professional identity. You must accept that your team will make decisions differently. Some worse, some better, and the majority adequate. That is challenging if your self-image relies on having the best judgement in the room.

When being the decision-maker is central to how a leader sees the role, delegating triggers a protective response. It is not laziness or ego. It is the same mechanism that makes any identity shift uncomfortable. The leader registers delegation as loss before the rational mind can reframe it as progress.

This is where most delegation advice fails. It treats the issue as procedural. Move decisions down the chain. Implement a framework. However, if a leader’s sense of professional worth is tied to decision-making, no framework alone will be effective.

For founders, the dynamic is even more acute. The founder built the company by being the central intelligence of the operation. That identity does not dissolve because you hired a leadership team. If your situation is specifically the founder version of this pattern, the founder coaching piece is worth reading alongside this one.

Why This Runs Deeper in Singapore and Southeast Asia

In Western management literature, escalation is typically framed as a failure of delegation. The leader needs to let go. This framing misses the cultural architecture of leadership in Asia.

In Singapore, hierarchy goes beyond organisational charts. Even experienced team members may escalate decisions, fearing that acting independently could be seen as overstepping. In cultures in which maintaining face and respecting seniority are structural norms, the risk of making a wrong decision is heightened by the social consequences of acting without approval.

HBR’s cross-cultural research documented this precisely. Japanese organisations tend to be hierarchical in authority but consensual in decisions. Chinese organisations tend to be hierarchical in both. In Singapore, where a team can span six nationalities and three first languages, the escalation trap operates across all of these dynamics simultaneously.

As a result, standard Western advice such as “just enable your team” is often ineffective in APAC contexts. A leader in Singapore may encourage independent decision-making, yet the team may continue to escalate as before. The message is received, but the underlying cultural norms remain unchanged.

The APAC leader also faces a dual version of the identity threat. The Western version is “if I am not the decision-maker, who am I?” The APAC addition is “if my team decides without my involvement, does that diminish my authority? If I step back, will it be read as disengagement rather than delegation?”

These are not irrational fears. In hierarchical cultures, they are legitimate navigation questions. The leader who answers them badly loses authority. The leader who never addresses them stays trapped.

Solving escalation in Southeast Asia requires understanding the root causes, not simply instructing teams to stop. Often, the boundary between individual and managerial decisions is unclear, inherited from predecessors or formed by previous adverse experiences. The fix is structural. Clarify the decision rights, define authority explicitly, and the escalation reduces. Not less hierarchy. Better-defined hierarchy. Clear decision rights that work within the existing cultural architecture rather than attempting to override it.

What Your Team Is Actually Doing

From the team’s perspective, escalation is a rational strategy. Consider what they have learned from watching you.

When someone escalates, you respond quickly. When someone decides independently and gets it wrong, the consequences are visible. When someone decides independently and gets it right, nobody notices.

This creates a clear incentive: escalation is low-risk and high-reward. Independent decisions carry higher risk and lower reward.

Your team has watched you close a decision in principle, only to reopen it in a meeting three days later. They have watched you delegate a project and then seek updates at a frequency that signals you do not actually trust the delegation.

Each of these behaviours is reasonable on its own. Together they create a system that trains your team to escalate decisions rather than own them.

There is a related pattern that operates in the other direction. When the escalation trap is active at the top, the people in the middle start managing upward as a survival strategy. They learn to read the leader, anticipate preferences, and present decisions pre-aligned with what they believe the leader wants to hear. This is not sycophancy. It is rational adaptation to a system that punishes independent decisions and rewards upward deference. The managing up dynamic and why it corrodes leadership culture is explored here.

The two patterns reinforce each other. The leader escalates because the team does not decide. The team does not decide because the leader escalates. Breaking one without addressing the other produces temporary relief and eventual reversion.

The Three Tests

There is a diagnostic I use early in coaching engagements to determine whether the escalation trap is active.

The first: can your direct reports describe, without checking, which decisions they own, which they need to consult you on, and which require your approval? Ask three of them separately. If you get three different answers, the decision architecture does not exist in any functional sense. What exists is a set of assumptions, shaped by experience, about what you will and will not tolerate.

The second: when you return from a week away, how much of what accumulated required your actual involvement? Not your preference. Your involvement. If the answer is everything, or close to it, the system has been designed around your presence. That is architectural dependency.

The third: what happened the last time someone on your team made a decision you disagreed with? Not a catastrophic error. An ordinary decision you would have made differently. If the organisational response was to treat it as a problem, the team received a clear signal: decide only when certain the boss would agree. Which means: do not decide.

Two out of three is enough. The trap is already operating.

The C-A-S Decision Mapping Approach

The C-A-S Decision Mapping Tool is a structured way to break the escalation cycle. C-A-S stands for Clarity, Accountability, and Support. It works in three steps.

Step 1: Clarity. List every decision that reached you in the past seven days, including approvals, strategic calls, operational choices, and escalations. Be honest about the total. Most leaders find the number is higher than expected.

Step 2: Accountability. Sort each decision into one of three categories. Keep: this requires your specific judgement because you have a lived context nobody else has, or because the stakes demand your personal accountability. Delegate: clear criteria exist, a deputy has sufficient context, and the risk is acceptable if they get it wrong. Eliminate: this should not be a decision at all. It can be automated, systematised, or simply stopped.

Most leaders find that fewer than a third of their decisions belong in the Keep category. The rest accumulated there through habit, through cultural expectation, or because nobody drew the boundary.

Step 3: Support. Design the boundary and hold it. This means defining explicit escalation criteria: when should a decision come to you? At what financial threshold? What risk level? What strategic significance? It also means installing a weekly decision audit. Fifteen minutes. Three questions. What landed on my desk that should not have? What did I delegate that came back? What is still unclear about who owns which decisions?

The audit is where the real change happens. Not in the framework. In the discipline of reviewing whether this week looked different from last week.

What Changes Look Like (And Why They Feel Wrong)

When leaders start redirecting decisions back to their teams, two things happen immediately. Speed drops. Quality varies.

Both are temporary, and both feel terrible.

The team will make a decision you disagree with. You will want to intervene. If you do, you reset the pattern to zero. Every intervention teaches the team that delegation was conditional, that you were watching, and that they should have escalated after all.

The transition period typically lasts six to twelve weeks. During that time, the leader’s role shifts from decision-maker to decision architect. You are no longer solving problems. You are building the system that solves problems without you.

Leaders who guide this transition successfully report something unexpected. The calendar opens up. The inbox quiets. And the first instinct is anxiety, not relief, because the silence itself feels like losing control.

That disorientation is the signal that something is actually changing.

For organisations evaluating the return on this kind of work, the ROI case for executive coaching is documented here.

Where This Connects

If you recognised your own pattern in this article, you are not alone. The escalation trap is one of the most common patterns among senior leaders in APAC, and one of the least discussed because it disguises itself as diligence.

The C-A-S Decision Mapping Tool is a starting point. For a deeper look at why directive leadership breaks down in hybrid APAC teams, read Why Command and Control Leadership Fails in Hybrid APAC Teams. For what happens when organisations try to solve this by removing management layers entirely, see The Squeezed Middle. If the pattern has already started affecting retention and board relationships, the CEO coaching piece addresses what changes when you work on it directly. And if you are curious about what structured coaching actually looks like when applied to this kind of pattern, that is worth reading too. The cross-cultural dimension of decision architecture in APAC teams is covered in The APAC Leadership Playbook.

Frequently Asked Questions

Why does everything get escalated to me at work?

Escalation tends to concentrate at the top when your team is missing one of three things: clarity on where decisions belong, accountability for outcomes, or support to act without approval. When any of those are absent, the path of least resistance is to bring decisions upward. The pattern compounds. Each escalation you resolve teaches your team that escalation works. Without a deliberate change to how authority is distributed and supported, the volume does not fall on its own.

How do you stop unnecessary escalations?

Start by mapping which decisions your team brings to you against which decisions they should own. The majority of escalation is not a capability problem. It is a boundary problem. Define the categories of decision that belong at each level, make those explicit rather than assumed, and build the support structures that allow your team to act: access to information, low-stakes practice on smaller calls, and confidence that they will not be second-guessed if they get a reasonable decision slightly wrong. Reducing escalation is a structural change.

What is escalation in leadership?

In leadership, escalation refers to the pattern in which decisions, problems, or actions that should be resolved at one level of an organisation are passed upward to a more senior person. Healthy escalation exists for decisions that genuinely require executive input. Unhealthy escalation happens when routine, bounded decisions consistently rise because the authority, clarity, or confidence to resolve them at the right level is absent. For senior leaders carrying a full escalation load, the overwhelming share falls into the second category.

Why do managers escalate decisions?

Managers escalate for three primary reasons. First, because the boundaries of their authority are unclear and they are risk-averse about overstepping. Second, they lack the information or resources needed to make a confident decision at their level. Third, because previous attempts to act independently were corrected or overridden, which taught them that approval-seeking is safer than ownership. All three are structural problems. Addressing escalation requires examining how authority is defined, how information flows, and what happens when someone makes a reasonable call that does not land perfectly.

Is the Escalation Trap the same as poor delegation?

No. Delegation advice assumes the problem is skills or willingness. The escalation trap operates at the identity level. The leader may understand delegation intellectually and still reach for decisions because being the decision-maker is central to how they see their role. The fix addresses the identity question first, then the operational architecture.

What is the C-A-S Decision Mapping Tool?

C-A-S stands for Clarity, Accountability, and Support. It is a three-step approach: map every decision that reaches you, categorise each as Keep, Delegate, or Eliminate, then design explicit escalation criteria and hold a weekly decision audit to track whether the pattern is shifting.

How do I delegate without losing control?

The concern about losing control usually signals a missing structure rather than a delegation problem. Effective delegation does not mean removing oversight. It means being explicit about what is being handed over, what good looks like, and when you want to be informed versus when you do not. Define the expected outcome, the constraints that apply, and the agreed check-in points. Without those elements, delegation produces anxiety on both sides. With them, you retain visibility without becoming the decision point for everything that moves.