1. How to Manage Conflict
The PMP® Reasoning Architect
This page provides guidance on the main concepts.
The book provides the full reasoning architecture and judgment training.
Click here to view the book on Amazon.
Executive Summary
This chapter synthesizes key principles for managing conflict, drawn from Orlando Casabonne’s book, THE PMP® REASONING ARCHITECT. It prepares for the ECO 2021 Task Manage Conflict. The central thesis is a paradigm shift: conflict is not a sign of failure but a “structural certainty” inherent in any complex endeavor. The absence of conflict, often mistaken for success, can be a dangerous indicator of suppressed issues, as “silence can be a lie.”
The core of this approach is to move from a reactive, peacekeeping mindset to a proactive, architectural one focused on “maintaining system integrity.” This involves a disciplined, two-step diagnostic process before any intervention: first, interpreting the type and stage of a conflict, and second, analyzing its systemic context with “diagnostic neutrality.”
Rather than relying on default personality traits, a “reasoning architect” employs five distinct governance behaviors as a strategic toolkit: Collaborating, Compromising, Smoothing, Forcing, and Avoiding. The ultimate goal is not universal harmony but “restored coherence”—a shared understanding of decisions that allows the team to move forward. This is achieved through the use of artifacts like issue logs and team charters, which function as “behavioral interfaces” to externalize problems and remove personal emotion. This framework reframes conflict as valuable data, enabling leaders to diagnose and strengthen the underlying systems of a project.
1. A Paradigm Shift in Understanding Conflict
Beyond Silence and Harmony
A common misconception in management is that a silent, agreeable team is a successful one. This “peace at all costs” mentality overlooks a critical truth: “silence is often way more dangerous than a shouting match.” The absence of overt fighting does not signify success; it can indicate that team members are disengaged or too fearful to voice concerns, effectively “giving up in private.”
The framework presented in Orlando Cassabone’s PMP Reasoning Architect fundamentally reframes this perspective. It posits that conflict is not a failure of leadership but a “structural certainty” when dealing with limited resources, competing deadlines, and passionate, intelligent people.
- Conflict as a Vital Sign: Conflict is viewed as a sign that “complexity is alive.” It indicates that team members are interdependent and that this interdependence is being tested.
- The Goal is Engineering, Not Elimination: Rather than seeking to eliminate all friction, the objective is to “engineer” conflict, to manage it constructively so it serves the project instead of derailing it.
2. The Reasoning Architect’s Mindset
The approach detailed in the PMP Reasoning Architect aims to cultivate a specific mental model for professional judgment. It diverges from traditional test-prep materials that encourage memorizing rules, instead focusing on teaching managers how to think from first principles.
- From Peacekeeper to Architect: The fundamental shift is from merely “keeping the peace” to the more strategic goal of “maintaining system integrity.”
- From Firefighter to Designer: A manager should not be a firefighter rushing to extinguish every flare-up. Instead, they should act as an architect, diagnosing foundational weaknesses and designing a system where disagreement can be processed safely and productively.
3. The Diagnostic Framework: A Two-Step Process
Before intervening, a reasoning architect must first diagnose the situation. This involves a deliberate, two-part process to understand the nature and root cause of the conflict.
Step 1: Interpret the Conflict
This step requires identifying both the type and the timing of the disagreement.
Four Types of Conflict
| Conflict Type | Description | Implications |
| Task-Based | Disagreements over the work itself, such as technical approaches or methods. (“We should use this software, not that one.”) | Generally healthy and can lead to better outcomes if managed well. |
| Process-Based | Disputes over workflow, roles, and responsibilities. (“Who is in charge of this? I thought you were sending that email.”) | Often a sign of an unclear or incomplete project plan. |
| Relationship-Based | Friction stemming from personality clashes, emotions, and interpersonal dynamics. (“I don’t like your tone.”) | The most destructive type if left unaddressed. |
| Value-Based | Deep-seated disagreements rooted in core beliefs and principles. (“I value moving fast vs. I value getting it perfect.”) | Difficult to resolve as they are tied to personal and professional identities. |
Timing and Intervention
Conflict exists on a spectrum from hidden to open, and the timing of intervention is critical.
- Latent Conflict: The conflict is hidden or dormant. It manifests in subtle cues like crossed arms, dismissive comments (“Fine, whatever”), or eye-rolling.
- Manifest Conflict: The conflict is out in the open, expressed through shouting, angry emails, or passive-aggressive communication.
Intervening too early in the latent stage can appear controlling, while waiting until the conflict is manifest means engaging in damage control rather than proactive management. The ideal moment is just as the conflict begins to “bubble up.”
Step 2: Analyze the Context with Diagnostic Neutrality
This principle requires managers to act with clinical objectivity, separating what is being expressed from what is being implied. Conflict is rarely just about the individuals involved; it is a “symptom of the system.”
- Definition: “Diagnostic neutrality” is the ability to see that the system may be forcing individuals into conflict. The focus shifts from “Bob is being a jerk” to “The system is forcing Bob to act this way.”
- Example: Two managers are fighting over a budget item. The expressed conflict is about money. However, the implied or systemic cause may be that the company has given them conflicting incentives—one is bonused for cutting costs, the other for launching a high-quality product that costs more. The system has made them adversaries.
4. A Toolkit of Governance Behaviors: Five Conflict Management Strategies
The PMP Reasoning Architect presents five strategies not as fixed “personality traits” but as “governance behaviors”: tools to be selected and applied based on a clear diagnosis of the situation.
| Strategy | Description & Goal | When to Use | Key Analogy |
| 1. Collaborating | The “gold standard.” Aims for an “integrative solution” where all parties’ needs are fully met (a win-win). | For high-stakes, complex problems where full buy-in is critical and time is available. Not for trivial issues. | Finding a food hall where one person can get amazing pizza and the other amazing sushi, so both win. |
| 2. Compromising | A short-term fix where each party gives something up. It is a “lose-lose situation that we pretend is fair.” | When time is short and a “good enough” solution is acceptable. The underlying issue remains unresolved. | A band-aid, not surgery. |
| 3. Smoothing | “Provisional containment.” Defuses a tense situation by emphasizing points of agreement and focusing on psychological safety. | In a crisis or right before a high-stakes event (e.g., a client presentation). The issue must be revisited later. | Hitting the “pause button” on a fight. |
| 4. Forcing | Using one’s legitimate authority to make a unilateral decision and provide clarity. | In emergencies involving safety or legal issues, or when facing an imminent, critical deadline. | When a building is on fire, you don’t collaborate; someone needs to yell, “This way, now!” |
| 5. Avoiding | Strategically disengaging from the conflict. This is not permanent evasion. | When emotions are too high (“a cooling off period”), more information is needed, or the issue is trivial. | Ghosting the problem, but with a calendar invite to return to it. |
5. From Resolution to Coherence: The Role of Artifacts
The ultimate goal of this framework is not harmony but “restored coherence”—a state where the entire team has a shared understanding of a decision and the rationale behind it, even if they do not personally agree with the outcome. This is achieved by using artifacts, which the book calls “behavioral interfaces.”
These tools work by externalizing a problem, transforming it from a “me versus you” dynamic into an “us versus the problem” dynamic, thereby removing emotion and introducing logic.
- Issue Log: A formal document that tracks conflicts, who is involved, the proposed resolution, and the status. It forces a logical structure onto a heated situation.
- Team Charter: Described as “a prenup for your project,” this document is created at the beginning to establish agreed-upon rules of engagement, such as decision-making processes and escalation paths.
- Retrospective Notes: In an Agile context, these notes help identify patterns of friction that emerge sprint after sprint, allowing the team to treat recurring tensions as action items to be solved systemically.
6. Applied Architecture: A Case Scenario
The Situation: Two top senior developers are at war over using React (for performance) versus Angular (for scalability) for a front-end framework. Morale is cratering.
- Ineffective Moves:
- Premature Forcing: “We’re using React. Get over it.”
- Ineffective Smoothing: “Can’t we all just get along?”
- The Architect’s Approach:
- Interpret: The conflict is task-based.
- Analyze: The root cause is an organizational gap: the absence of shared architectural standards. The developers are filling a leadership vacuum with personal philosophies.
- Action: The manager facilitates a structured session, reframing the technical choice in the context of business value (“What is the actual goal of this MVP?”). An artifact, a decision log, is created to track the criteria.
- Resolution: The team collaborates to reach an integrative solution. They choose the simpler framework to meet the immediate MVP deadline but schedule a specific checkpoint to re-evaluate for scalability later. Coherence is restored because the decision is tied to shared project goals.
7. Key Takeaways and Pitfalls
Conflict management is an architectural skill. Properly managed conflicts are not problems; they are data indicating where a system, process, or plan is weak.
Major Pitfalls to Avoid:
- Dumping Responsibility: Running to a superior too early instead of diagnosing and managing the issue.
- Chronic Smoothing: Constantly papering over issues without addressing the root cause is like “putting a band-aid on a broken bone.”
- Focusing on Symptoms: Yelling at people to work faster when a schedule is slipping, instead of asking why it is slipping and addressing the underlying conflict that is slowing progress.
8. A Concluding Thought on Healthy Conflict
The ultimate mark of a well-led team is not the absence of noise, but the presence of psychological safety that allows for productive disagreement. A leader must ask a hard question when faced with perfect, immediate agreement: “Are we perfectly aligned, or are we just scared to speak up?” True leadership designs a space where it is safe for conflict to happen in the open, because as the analysis concludes, “if they aren’t fighting in the open, they’re probably giving up in private.”