Conflict Resolution & Roadblock Escalation

1. The Psychology of Escalation: Feature, Not Bug

In many organizations, "escalation" has a negative connotation. It can be perceived as an admission of failure, an act of aggression, or "tattling" on a colleague. This cultural barrier often causes teams to delay raising critical issues, letting them fester until they become genuine crises. For your transformation to succeed, it's vital to reframe escalation as a healthy, necessary tool for collaborative problem-solving.

To understand this better, let's explore the cultural and practical aspects of escalation management.

The key shift in mindset is to view an escalation path as a pre-agreed process for seeking help, not assigning blame. It provides a safety valve that empowers individuals at all levels. When someone knows there is a clear, blameless path to get a decision un-stuck, they are more likely to raise issues early, which is crucial for the adaptive strategy you want to build.

2. Diagnosing Conflict: When to Escalate

Not all disagreements require formal escalation. Part of designing an effective path is understanding the nature of conflict itself, so you can recognize when informal resolution is failing and a structured intervention is needed.

A useful tool for this is Glasl's Model of Conflict Escalation. It shows how conflicts, if left unchecked, tend to intensify through predictable stages, moving from a collaborative "win-win" mindset to a destructive "lose-lose" reality.

Let's break down the phases:

• Phase 1: Win-Win. Here, the conflict is about the issue itself. Parties are still focused on finding a mutually beneficial solution. Interventions like facilitated discussion are usually enough.
• Phase 2: Win-Lose. The focus shifts from the issue to the relationship. It becomes about winning and losing, personal attacks, and forming coalitions. At this point, mediation by a neutral third party (like a TMO lead or manager) is often required.
• Phase 3: Lose-Lose. The goal is no longer to win, but to ensure the other side loses, even at one's own expense. This is where threats, sabotage, and total confrontation occur. Intervention here must be authoritative and decisive, which is precisely what a formal escalation to senior leadership provides.

Your escalation process is a formal mechanism to trigger intervention, ideally while the conflict is still in late Phase 1 or early Phase 2, before significant damage is done to relationships and project goals.

3. Designing a Formal Escalation Path

A robust escalation path is not just a line on an org chart; it's a well-defined process. Let's build one using a structured, four-step approach.

Based on these readings, here is a consolidated framework for designing your path:

Step 1: Define Escalation Categories

First, define the types of issues that can be escalated. This provides clarity and helps route the issue to the right people. These categories should align with the decision types you defined in the last lesson.

• Resource Contention: e.g., two workstreams needing the same key engineer.
• Budget Overruns: e.g., a workstream needing more funds than allocated.
• Scope Disagreements: e.g., conflict over whether a feature is in or out of scope for a release.
• Technical Roadblocks: e.g., a critical architectural decision that impacts multiple teams.
• Timeline/Dependency Conflicts: e.g., one team's delay blocking another team's start.

Step 2: Define Escalation Levels and Service Level Agreements (SLAs)

This is the core of the path. You must define the hierarchy and the expected response time at each level. For your transformation, this might look like:

• Level 1: Between individuals within a workstream -> Workstream Lead
• Level 2: Between workstreams -> Transformation Management Office (TMO)
• Level 3: Major strategic, budget, or cross-program issues -> Steering Committee (SteerCo)

For each level, you must define an SLA. For example:

• Acknowledgement SLA: The recipient of the escalation must acknowledge receipt within 4 business hours.
• Resolution SLA: The issue must be resolved or a clear action plan communicated within 3 business days.

This matrix makes the path tangible and sets expectations for urgency.

Step 3: Define the Escalation Procedure ("How to Escalate")

An escalation should not be a frantic email or a hallway complaint. It should be a structured request for a decision. As recommended in the CIO article, the person escalating must first do their due diligence. The procedure should require the submission of a concise brief (e.g., a 1-pager) containing:

1. Problem Statement: A clear, neutral summary of the issue or conflict.
2. Business/Customer Impact: Why does this matter? Quantify if possible (e.g., "This will delay the Q3 launch and affect our top 5 customers.").
3. Options Explored: What solutions were considered by the parties involved? What were the pros and cons of each?
4. Point of Disagreement: A specific summary of where the parties are deadlocked.
5. Specific Request: What decision is needed from this level of leadership?

This discipline ensures that by the time an issue reaches a leader, it has been properly framed, saving time and focusing the discussion on resolution, not discovery.

Step 4: Secure Leadership Buy-in and Communicate

An escalation path is useless if leadership doesn't respect it. The final step is to review the documented path with the Steering Committee and other leaders. They must publicly commit to:

• Being responsive and honoring the SLAs.
• Following the process and not encouraging "back-channel" escalations that undermine the structure.
• Focusing on solving the problem, not on blaming the individuals or teams who escalated it.

Once approved, this document should be shared widely and become part of the transformation program's operating charter.

4. Application Exercise: Navigating a Conflict

Let's apply this to a realistic scenario from your transformation.

Scenario:
The Product Workstream wants to delay the next major release by one month. They have discovered that a core part of the legacy monolith is more complex than anticipated, and they want to refactor it properly to align with the new microservices architecture. They argue this is crucial for long-term stability.

The GTM Workstream is strongly opposed. They have a major marketing campaign planned, and the sales team has already committed to the original release date with several key customers. They argue that a delay will damage credibility and potentially lose deals.

The two workstream leads have met twice but are deadlocked. The TMO Lead has now been brought in.

Your Task (15 minutes):

1. Diagnose the Conflict: Based on Glasl's model, what stage would you say this conflict is in? Justify your answer.
2. Draft an Escalation Brief: Imagine you are the TMO Lead. The decision is too significant for you to make alone, so you must escalate to the Steering Committee. Draft a 1-page escalation brief following the structure from Step 3 above. Be concise and use bullet points.
3. Outline the Path: In this scenario, what was the correct escalation path the issue followed?

Conclusion

Today, we've designed the critical mechanism for handling friction in your transformation. A clear and trusted escalation path is what allows a complex program to absorb shocks and keep moving forward.

Key Takeaways:

• Escalation is a healthy governance process, not a sign of failure. It requires a culture of trust, which leaders must actively build.
• Understanding conflict dynamics (Glasl's Model) helps you know when to intervene. An escalation path is your formal tool for intervening before a conflict becomes destructive.
• A well-designed escalation path is a documented process with clear categories, hierarchical levels, response time SLAs, and a defined procedure for making the request.
• Leadership commitment is non-negotiable. The entire process relies on leaders agreeing to the system and being responsive when issues are raised.

Preview of the Next Lesson

We've repeatedly mentioned the Transformation Management Office (TMO) as a central hub for integration, decision-driving, and escalation management. In our next lesson, we will do a deep dive into this critical function. We will "Define the mandate and operating model of a Transformation Management Office (TMO)," exploring its structure, responsibilities, and how it acts as the engine room of the entire transformation program.