5.2 Conflict Resolution in Agile

In high-performing Agile teams, conflict is not only inevitable—it is desirable when focused on ideas and innovation. Cross-functional team members with diverse perspectives naturally encounter friction when deciding architectural approaches, prioritization, or process improvements. However, unmanaged conflict can quickly degrade team dynamics, collapse trust, and destroy productivity. Agile servant leaders must recognize the signals of escalating conflict and apply targeted resolution strategies.

Lyssa Adkins' 5 Levels of Conflict

Agile coaching pioneer Lyssa Adkins established a framework defining 5 Levels of Conflict. Understanding these levels allows servant leaders to determine whether to step back and allow self-organization or intervene decisively.

Level 1: Problem to Solve

• Focus: The team is focused on sharing facts, resolving a technical or operational challenge, and finding the best solution.
• Language: Objective, direct, clear, and collaborative (e.g., "The build failed on branch B. Let's check the test logs to see what broke").
• Team Dynamic: Open debate; opinions are expressed freely without fear of personal attack.
• Servant Leader Action: Step back. Allow the team to self-organize and resolve the problem independently.

Level 2: Disagreement

• Focus: Self-protection becomes equal to or more important than solving the problem. Team members begin guarding their positions.
• Language: Cautious, slightly defensive, featuring personalizing statements (e.g., "I thought we agreed you were handling API integration. Why wasn't it finished?").
• Team Dynamic: Communication becomes guarded. People hold back information or seek offline validation from peers.
• Servant Leader Action: Support & Empower. Encourage direct peer-to-peer dialogue, help depersonalize issues, and assist team members in clarifying assumptions.

Level 3: Contest

• Focus: The goal shifts from solving the problem to winning the argument. Competing factions form within the team.
• Language: Distorted arguments, personal attacks, over-generalizations ("always", "never"), and "us vs. them" framing (e.g., "The frontend developers always push untested code and ruin our deployments").
• Team Dynamic: Alliances form; discussion revolves around past grievances rather than current facts.
• Servant Leader Action: Facilitate & Negotiate. Intervene actively to ground discussions back in objective facts, re-establish ground rules, and guide the team toward negotiated trade-offs.

Level 4: Crusade

• Focus: Conflict becomes ideological. Protecting personal principles or "sacred cows" takes precedence over team success. Resolving the original problem is no longer desired; defeating the opposing faction is the objective.
• Language: Ideological, attacks on character, language reflecting intractable positions (e.g., "They don't respect basic software craftsmanship. They will never change, and we can't work with them").
• Team Dynamic: Team members refuse to interact directly; polarization is extreme.
• Servant Leader Action: Protect & Establish Boundaries. Decisively intervene to protect safety. Re-establish strict behavioral boundaries and consult management or Agile coaches for structural intervention.

Level 5: World War

• Focus: Total destruction. Mutual annihilation is accepted as long as the opposing party suffers. Intractable hostility dominates.
• Language: Toxic, explosive outbursts, absolute refusal to communicate, or quiet destructive sabotage.
• Team Dynamic: The team is completely non-functional; psychological safety is destroyed.
• Servant Leader Action: Separate & Escalate. Immediately separate the conflicting individuals to prevent further harm. Escalate to formal HR and organizational management for re-assignment or formal resolution.

---

The Thomas-Kilmann Conflict Resolution Modes (TKI Framework)

The Thomas-Kilmann Conflict Mode Instrument (TKI) measures conflict handling behaviors along two basic dimensions:

• Assertiveness: The degree to which a party attempts to satisfy their own concerns.
• Cooperativeness: The degree to which a party attempts to satisfy the other party's concerns.

                     HIGH |  Competing / Forcing    Collaborating
                          |  (Win-Lose)             (Win-Win)
   ASSERTIVENESS          |
                          |        Compromising (Split Difference)
                          |
                      LOW |  Avoiding / Withdrawing  Accommodating
                          |  (No-Win)               (Lose-Win)
                          +----------------------------------------
                             LOW                  HIGH
                                 COOPERATIVENESS

1. Collaborating (High Assertiveness, High Cooperativeness) — "Win-Win"

• Approach: Parties work together to explore underlying concerns and find an integrative solution that fully satisfies everyone's needs.
• Agile Application: Ideal for complex architectural decisions, definition of working agreements, and product strategy where full buy-in is required.

2. Competing / Forcing (High Assertiveness, Low Cooperativeness) — "Win-Lose"

• Approach: One party uses formal power or insistence to achieve their goal at the expense of others.
• Agile Application: Appropriate in rare emergency scenarios, such as enforcing safety protocols, regulatory compliance mandates, or stopping abusive behavior.

3. Compromising (Moderate Assertiveness, Moderate Cooperativeness) — "Split the Difference"

• Approach: Both parties give up something to reach a fast, mutually acceptable intermediate solution.
• Agile Application: Effective when time is constrained during iteration planning and a temporary operational decision is needed to maintain velocity.

4. Accommodating / Smoothing (Low Assertiveness, High Cooperativeness) — "Lose-Win"

• Approach: One party yields their stance to satisfy the concerns of the other party.
• Agile Application: Useful when maintaining harmony and team cohesion is far more critical than the minor technical point at stake, or when a team member realizes their original assumption was mistaken.

5. Avoiding / Withdrawing (Low Assertiveness, Low Cooperativeness) — "No-Win"

• Approach: Postponing or suppressing the conflict without resolving the underlying issue.
• Agile Application: Useful as a temporary tactical measure when emotional tempers are high, allowing a cooling-off period before addressing the issue at Level 1.

---

Servant Leadership in Conflict Facilitation

Agile servant leaders act as neutral facilitators when resolving team conflict by applying key coaching techniques:

• Depersonalizing the Debate: Reframing statements from personal accusations ("You wrote bad code") to shared objective challenges ("Our automated integration test failed on module X").
• Active Listening & Mirroring: Ensuring each conflicting party restates the other person's perspective to demonstrate understanding before proposing solutions.
• Refocusing on Shared Values: Reminding team members of their agreed-upon Team Charter, shared vision, and customer outcomes.