Stop Hiding the Friction: Why Escalation Is Your Most Misunderstood Change Management KPI

The term “escalation” has its roots in the Latin word scala, meaning “ladder.” Just as a physical ladder elevates us to reach an otherwise inaccessible goal, modern business escalations serve a similar vertical purpose. However, instead of elevating the individual, a business escalation elevates a critical need or unresolved issue to the exact level of authority required to solve it

A split illustration comparing ancient Roman 'scala' (ladder) with modern business escalation. The left shows a Roman soldier climbing a ladder to reach a treasure chest, labeled with 'problem' and 'objective'. The right depicts an office scenario with stressed workers escalating issues through various management levels, culminating in an executive board, labeled 'resolution (hopefully)'.

The Pathology of Bad News

In most corporate environments, ‘escalation’ is treated like a bad word. This often drives project managers toward two distinct, well-recognized failure modes :

The MUM Effect (“Minimizing Unpleasant Messages”)

This well-documented phenomenon occurs when individuals suppress, delay, or avoid reporting bad news to higher authorities due to discomfort, shame, or an overestimation of their own ability to fix the situation. In these environments, escalation feels like a confession. The implicit rule is that a project manager who escalates is one who cannot cope.

Post Office Syndrome

Conversely, this occurs when individuals immediately pass along bad news to higher authorities without analyzing it, attempting to resolve it, or adding necessary context. Driven by a desire to deflect blame, the escalation acts as a mere hand-off. The problem is treated like a toxic letter, dropped on someone else’s desk by a project manager refusing to take ownership.

An illustrated infographic titled 'Understanding Organizational Pathologies: Handling Bad News' depicting two scenarios: 'The Mum Effect' on the left, showing a woman trying to hide project issues while a manager looks on, and 'Post Office Syndrome' on the right, illustrating a woman deflecting responsibility for problems to higher-ups, with a stressed man at a chaotic desk.

Both mindsets are costly. If we want change initiatives to succeed, we must stop hiding the friction—or blindly deflecting it—and start measuring it.

Escalation is Governance, Not Failure

Project management research frames escalation not as a failure, but as a formal, disciplined governance mechanism (Kerzner & Zeitoun, 2026). It is the structured process of passing a decision or blocker to a higher authority when it exceeds the project team’s scope, budget, or decision-making power.  

High-performing organizations do not suppress issues until they turn into failures; they use escalation to keep strategic purpose and day-to-day execution aligned (Gehl & Kock, 2026). Research points to six distinct triggers that rightfully demand escalation:  

  1. Budget and schedule variances: Deviations beyond agreed thresholds that threaten project feasibility.
  2. Scope and technical changes: Complex requirement shifts needed to prevent major quality defects or operational misfits.
  3. Resource and skill constraints: Critical talent shortages or intense competition for resources across functional silos.
  4. Governance and approval bottlenecks: Delays caused by rigid approval gates, policy misalignments, or bureaucracy.
  5. Stakeholder and inter-departmental conflicts: Friction between groups where the project manager holds no direct authority.
  6. High-impact risks: Emerging threats requiring executive intervention, policy changes, or formalized risk absorption (Ahern et al., 2014).
Infographic detailing the 6 strategic triggers of project escalation, including execution, operational triggers, and governance triggers such as budget variances, scope changes, resource constraints, approval bottlenecks, stakeholder disagreements, and high-impact risk mitigation.

Figure 1. Escalation moves a decision to the level that has the authority to take it.

From Rearview Mirrors to Headlights

Transformational projects inherently disrupt legacy habits and rigid policies, creating unavoidable institutional friction (Beste & Klakegg, 2022). Without clear escalation pathways, this friction does not disappear—it simply goes underground, manifesting as quiet resistance, shadow workarounds, or project paralysis.

This is where escalation transforms from a process into a diagnostic KPI. Most change management dashboards are built on rearview mirrors. Metrics like training attendance, survey responses, or system login counts tell you where your transformation has been.  

Escalation metrics, on the other hand, give you headlights.

Discounting the “Post Office PM” who forwards raw noise, a formalized escalation is actually a sign of organizational health, psychological safety, and maturing governance. It reveals the exact point where an issue escapes local authority and requires executive alignment. Tracking escalation data provides leadership with a continuous improvement roadmap, flagging systemic execution bottlenecks in real time so they can be resolved immediately and institutionalized during retrospectives. It highlights exactly where legacy routines are resisting the new vision, allowing leadership to steer before friction turns into failure.

Building a People-First Escalation

Standardizing escalation builds reporting routines directly into the change initiative, granting teams explicit permission to raise institutional misfits early (Gehl & Kock, 2026). To extract the most strategic value from these escalations, three practices make the difference: 

  1.  Bring solutions, not just problems: An escalation should never be a raw complaint. Prepare a concise recommendation outlining possible decision paths and risk trade-offs, enabling executives to decide quickly.  
  2. Speak the language of business value: Executives respond to business impact, not technical jargon. Frame the issue around financial metrics, customer experience, and strategic alignment.  
  3. Document and audit your escalations: A detailed historical log builds organizational memory, ensuring similar friction is handled smoothly in future portfolios.

Escalation is not a sign that your change initiative is failing; it is the exact mechanism that allows change to succeed. By removing the stigma around raising issues and measuring them systematically, operational friction becomes your most valuable diagnostic intelligence.  

Key takeaways

To turn escalation from a dreaded bottleneck into a strategic advantage, keep these four principles in mind:

  • Escalation is governance, not failure. It is a formal mechanism to align execution with strategy, not a penalty for struggling teams.
  • Silence is not safety. Unspoken friction doesn’t disappear; it metastasizes into shadow workarounds, schedule delays, and quiet resistance.
  • Measure what matters. Stop relying solely on lagging indicators. Start tracking four forward-looking metrics: escalation volume/trend, resolution velocity, friction categories, and repeat escalation rate.
  • Culture dictates success. The system only works if project teams have the psychological safety to raise issues, and executives are prepared to receive those escalations framed with solutions and business impacts.

References

  • Ahern, T., Leavy, B., & Byrne, P. (2014). Complex project management as complex problem solving: A distributed knowledge management perspective. International Journal of Project Management, 32(8), 1371–1381.
  • Beste, A., & Klakegg, O. J. (2022). Strategic change towards cost-efficient public construction projects. International Journal of Project Management, 40(5), 485–498.
  • Gehl, K., & Kock, A. (2026). The proof of purpose lies in the project: How organizational purpose is formalized and aligned through project governance. International Journal of Project Management, 44(1), 102580.
  • Kerzner, H., & Zeitoun, A. (2026). The art of escalating to senior management. PM World Journal, 15(2), 1–12.

Leave a Reply