Why Does Everything Escalate to Me?

If you were to review your calendar from the past five working days. Focus not on meetings, but on decisions: 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.

What you are looking at is the escalation trap that we can easily fall into.

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 increase. 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 is different from poor delegation. Delegation is a skill. This differs from poor delegation, which 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.

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.

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.

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. structural version of this problem. Fix the decision rights, clarify authority, and the escalation will be reduced.

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 is beyond a process change; it requires redefining your career identity. You must accept that your team will make decisions differently—some worse, some better, and most adequate—which might be challenging if your self-image relies on having the best judgment.

This is where most delegation advice fails. It treats the issue as procedural—simply move decisions down the chain or implement a framework. However, if a leader's sense of professional worth is tied to decision-making, no framework will be effective.

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. When a team member escalates an issue, you reply promptly.

If someone decides independently and errs, the consequences are apparent. If they succeed, the result is often overlooked. This creates a clear incentive: escalation is low-risk and high-reward, while independent decisions carry higher risk and lower reward. 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.

While each of these behaviours is reasonable on its own, together they create a system that encourages your team to escalate decisions.

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 judgment because you have a lived context nobody else has, or because the stakes demand your personal accountability. Delegate: clear criteria exist, a deputy has ample 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 6 to 12 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 not thankfulness but anxiety, because the silence itself feels like losing control.

That disorientation is the signal that something is actually changing.

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. 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 conversation starts here.

Sixty minutes is enough to map your escalation pattern and see what the calendar looks like when you stop carrying decisions that were never yours.

The conversation starts here.