Human Capital
The same conflict keeps erupting. You're solving the wrong problem.
Organizations resolve conflicts repeatedly because they address visible disputes without diagnosing what caused them. Learn how to move past symptom-treatment to root-cause analysis, and why that shift cuts recurring conflicts by 40-60%.
Recurring conflicts signal that you're treating symptoms rather than causes. A diagnostic approach identifies whether the real problem is resource competition, role ambiguity, misaligned incentives, or broken process—and what kind of intervention actually addresses it. Interest-based negotiation then shifts from positional bargaining to collaborative problem-solving, creating solutions that stick because both parties have genuine buy-in. Without this foundation, you cycle through the same disputes indefinitely.
What good looks like
| Metric | Minimum | Strong | World-class |
|---|---|---|---|
| Problem Recurrence RatePercentage of problems that are reopened or regenerate the same or similar incident within a defined period after initial closure. | 15-22% | 8-14% | 2-6% |
| Problem Documentation CompletenessPercentage of closed problems with documented root cause, resolution steps, and remediation details sufficient for future reference and prevention. | 55-68% | 75-87% | 90-97% |
Organizations with weak root-cause discipline see problem recurrence rates of 15-22%, while those with mature diagnosis and permanent-fix validation drop to 2-6%. The gap reflects a fundamental difference: reactive organizations treat each conflict as an isolated incident; mature organizations extract systemic lessons and redesign to prevent repetition. Documentation completeness shows the same pattern—weak discipline leaves 32-45 percentage points of institutional knowledge uncaptured, meaning the next conflict starts from scratch rather than building on what the last one revealed.
Industry-Specific Benchmarks
These ranges are cross-industry. The figures differ materially by sector and company size.
Find benchmarks for your industry →Why the gap exists
The difference between organizations that resolve conflicts once and those that resolve them repeatedly lies not in the quality of the first conversation but in what happens after. Mature organizations conduct structured root-cause analysis before closure—mapping whether the conflict stemmed from unclear authority, competing priorities embedded in incentive structures, process gaps, or interpersonal breakdown. This diagnosis determines the remedy. A conflict rooted in role ambiguity requires clarified decision rights and authority mapping, not mediation. One driven by competing budget incentives requires realigned metrics. One caused by a broken handoff between departments requires process redesign. Organizations that skip diagnosis invest in conflict resolution conversations that feel productive in the moment but leave the underlying driver untouched.
The second differentiator is whether resolution becomes learning. World-class organizations treat each resolved conflict as an input to organizational design. They document not just what was decided but why the conflict occurred, what it exposed about systems or structure, and what changed to prevent recurrence. This creates a feedback loop: each conflict improves the organization's underlying design, making future conflicts less likely. Weak organizations treat conflict as an anomaly—something to suppress or survive rather than something diagnostic. They resolve the same disputes in different teams, in different quarters, because the structural root remains invisible.
Interest-based negotiation accelerates this pattern. Rather than position-based bargaining where one party wins and the other resents the outcome, this approach uncovers underlying interests and priorities, then generates solutions that address root motivations. The mechanism is straightforward: most organizational disputes are not actually zero-sum. A conflict between product and operations over timeline may surface a product team's interest in market responsiveness and operations' interest in system stability—interests that can both be served through redesigned process or phased rollout rather than one party surrendering to the other. When both parties feel their legitimate concerns are addressed, buy-in is genuine and recurrence is far less likely.
What leading organizations do
Diagnose Before You Resolve
The most common mistake in conflict resolution is beginning with the conversation. Instead, begin with diagnosis: structured assessment of what actually caused the conflict to surface. Is this rooted in unclear decision rights between two functions? In performance metrics that penalize one party for helping another? In a missing handoff in a cross-departmental process? In interpersonal friction that would exist in any working relationship? In ambiguous role boundaries? Each root cause requires a different intervention. Diagnosing correctly means your resolution effort addresses the actual driver rather than the visible symptoms.
The diagnostic process involves stakeholders from all sides—not to determine fault but to map the system factors and relationship factors that made conflict inevitable. A director or VP should ask: What conditions would have to be true for this conflict to not happen next time? The answer is almost never "the involved parties need to get along better." It is usually structural: clearer escalation authority, realigned incentives, process redesign, role clarification, or resource reallocation. Diagnosis creates the foundation for intervention that actually works. Organizations that diagnose before intervening typically reduce recurring conflict in the same area by 40-60% compared to those that skip this step and move directly to mediation.
Leading Practice Report
Full detail: Conflict Diagnostic & Root Cause Analysis
The full report covers:
- Expected benefits
- Core principles
- Key success factors
- Key metrics
- Risks and mitigations
- Implementation roadmap
Move From Positions to Interests
Interest-based negotiation reframes a conflict from "what does each party demand?" to "what does each party actually need?" The distinction is foundational. In positional bargaining, two teams negotiate as adversaries: product wants a three-month timeline, operations insists on six months, they compromise at four-and-a-half, and both leave resenting the outcome. In interest-based negotiation, you uncover what the timeline demand actually serves. Product may need market responsiveness and competitive positioning. Operations may need system stability and risk management. Neither interest is illegitimate, and most organizational disputes are not actually zero-sum.
The practice requires structured conversation: separate people from the problem (focus on the timeline question, not on who is being difficult), surface underlying interests rather than demanding positions, generate multiple options that might address both sets of interests (phased rollout, pre-staging, different components on different timelines), and use objective criteria—data on failure rates, competitive timelines, technical constraints—as anchors rather than having each party's preferences determine the answer. Organizations that use this approach report 30-40% faster resolution and dramatically higher sustainability because solutions emerge from mutual understanding rather than one party capitulating to pressure. The working relationship often strengthens rather than deteriorates because both parties invested in a problem together rather than competing.
Leading Practice Report
Full detail: Interest-Based Negotiation (Interest-Based Relational Approach)
Benefits, core principles, success factors, metrics, risks and the implementation roadmap.
Get the full report →Repair Relationships, Don't Just Resolve Disputes
When conflict damages a working relationship, organizations often choose between two paths: suppress the conflict and move on, or remove one or both parties. Restorative dialogue offers a third option: structured conversation where people acknowledge impact, understand harm, and work toward repair without requiring someone to lose.
This matters most when the people involved need to continue working together and when losing either person would be costly—in knowledge-intensive roles, in partnerships, in geographically distributed teams where relationship stability matters over years. The approach is built on a different assumption than traditional conflict resolution: that understanding impact and acknowledging harm is as important as determining who was right. A structured conversation allows each person to describe how the conflict affected them, to understand the impact on others, to clarify intent versus impact, and to identify what would restore working trust. Organizations report 25-40% higher retention of people involved in conflict when using restorative approaches versus traditional discipline or separation. The cultural effect is equally important: employees observe the organization valuing relationships and repair over quick removal, which strengthens psychological safety and trust.
Leading Practice Report
Full detail: Restorative Dialogue & Relational Repair
Benefits, core principles, success factors, metrics, risks and the implementation roadmap.
Get the full report →Industry context
This problem is universal but surfaces differently by context. In product and engineering organizations, conflicts often stem from competing timelines and resource constraints; the diagnostic approach reveals whether the root is misaligned incentives (product metrics reward speed, operations metrics reward stability) or genuinely insufficient capacity. In distributed organizations, conflict frequently involves unclear decision rights across geographies; diagnosis clarifies authority and escalation rather than defaulting to lengthy negotiation cycles. In matrix organizations, role ambiguity creates chronic conflict; interest-based negotiation becomes necessary because positional bargaining is impossible when both parties have legitimate authority claims.
The recurrence problem is most acute in organizations that have experienced rapid growth or frequent reorganization. Each structural change leaves ambiguity in its wake—unclear handoffs, competing priorities, overlapping responsibilities—and these ambiguities surface as interpersonal conflict. Smaller organizations sometimes avoid this because roles and relationships are more visible; mid-size organizations often experience it most acutely because growth has outpaced explicit process design. Very large organizations sometimes escape it because they invest in governance and documentation, though they often do so only after experiencing the cycle multiple times.
Where to start
- Identify one recurring conflict—something that has erupted in the same form more than once—and map its root cause. Ask: what would have to be different in our systems, processes, or structure for this conflict to not happen? The answer you identify is what requires change, not just mediation.
- In your next conflict resolution conversation, try interest-based structure: ask each party what they actually need rather than what they demand, and generate multiple options before settling on one. Notice whether solutions generated this way are adopted more readily than compromises.
- Establish a conflict review process: when a significant dispute is resolved, document not just the outcome but the underlying cause, the systemic factor that made it inevitable, and what changed to prevent recurrence. This becomes organizational learning rather than a closed incident.
What specific conflict keeps surfacing in your organization? Ask Kepler how to diagnose its root cause and redesign to prevent repetition.
Start free with Ask Kepler →Advanced and emerging approaches
Advanced & Emerging Practices
Emerging practices are included with Ask Kepler Pro and Max.
Unlock these practices →