Manage Conflicts

Two team leads keep clashing in every standup over who owns the integration work. You could pick a conflict technique and referee the argument on the spot, but skip a step and you treat the symptom while the same clash returns tomorrow. Managing conflict is two moves, and the first is diagnosis: find what is actually generating the friction, then read how intense it is, before you choose any response. The figure below sets these out in order: identify the underlying source, read the context and severity, then select the resolution technique.

Find the underlying source

Locate the real driver of the conflict rather than the surface argument. Common sources are competing priorities, scarce or shared resources, schedules and deadlines, technical opinions, and unclear roles or ownership. The PMP Examination Content Outline^[1] makes "identify conflict sources" the first task under Manage Conflicts for exactly this reason: treat the visible symptom and the driver stays in place to recur.

A conflict that recurs at every meeting is the clearest tell of an unresolved root cause, and the most common root cause is unclear roles, ownership, or expectations. Sitting down to clarify who owns what resets expectations and unblocks the work far more reliably than avoiding the person or changing your own leadership style.

Read the context and severity

The right resolution approach depends on the intensity of the conflict, the relationships between the people, and the stakes involved, so assess those before acting. Analyzing the context is the second task the outline^[1] lists under Manage Conflicts. There is no single technique that fits every situation: a mild difference of technical opinion and a personal, escalating dispute call for very different responses, and applying your one go-to move to both is the mistake this step exists to prevent. Only after these two reads, source then context, do you select a response.

Every response to conflict is one of five techniques, and they differ in one thing that decides which to reach for: how durable the outcome is. The comparison table at the top of this page lists all five in order; this section explains why the order runs the way it does and names the classic aliases you will meet on the exam.

Collaborate / problem-solve (also called confronting) works with the parties to address the underlying interests and reach a win-win that removes the root cause. It is the preferred default because it produces genuine commitment, not just compliance, and it is the only technique that actually resolves the driver rather than papering over it.

Compromise (also reconciling) trades concessions so each side is partly satisfied. It is faster than collaborating and useful when both parties must give a little and time is short, but neither side fully gets what it needs, so the root issue can resurface.

Smooth / accommodate (also smoothing or accommodating) plays up the points of agreement to preserve harmony and de-emphasizes the differences. It keeps the relationship intact and can buy time, but it leaves the actual disagreement unresolved.

Force / direct (also forcing, directing, or competing) means imposing your decision and directing both parties to accept it. It is win-lose: it secures compliance quickly but not commitment, and resentment often follows. Reserve it for genuine emergencies, safety issues, or non-negotiables, never for an ordinary disagreement collaboration could settle.

Withdraw / avoid (also withdrawing or avoiding) steps back from the conflict, including the tempting move of reassigning people to separate work streams to keep them apart. It only postpones the conflict and treats the symptom, which is why PMI ranks it lowest: a temporary, lose-lose response that leaves the cause fully intact.

These five map onto the classic five conflict-handling styles^[2], which position each style by how assertive it is about your own interests and how cooperative it is about the other party's. PMI teaches the same five styles under the names above; whichever labels a question uses, the ranking by durability is what it is testing.

A well-chosen technique still fails if you apply it at the wrong grain, in the wrong forum, or in front of the wrong audience. Three questions set the grain: who should resolve this, where, and how publicly.

Let a self-managing team resolve routine disagreement

On a healthy team, a routine or collective disagreement is theirs to work out. The servant-leader project manager trusts the team, observes, and offers help only if the disagreement stalls or escalates, which preserves the ownership and autonomy that make the team self-managing in the first place. A self-managing Scrum Team^[3] is one formalization: it decides internally who does the work and how, and any self-organizing team the organization empowers to manage its own work operates the same way, whether the delivery approach is agile, hybrid, or predictive. Coaching agile teams through conflict^[4] treats mild, constructive disagreement as healthy friction to protect, not suppress. Imposing a formal technique or a manager-led meeting on a mild difference undermines exactly that self-organization, so reserve the formal techniques for escalated, interpersonal, or genuinely unresolved conflict.

Facilitate in the forum, do not take it offline

When conflict surfaces in a meeting, the project manager stays and uses facilitation skills to move the parties toward a shared understanding right then. Asking the disputants to take it offline, or postponing the meeting, is avoidance dressed up as tact: it stalls alignment and signals that disagreement is unwelcome.

Meet privately first, then bring the parties together

An escalated or interpersonal conflict is the exception to resolving things in the open. Before bringing the parties together, meet one-on-one with each to hear their perspective, defuse the emotion, and surface their real interests. That private understanding sets up a facilitated session where the parties collaborate to a win-win. The figure below traces that sequence: meet each party privately, surface their real interests and defuse the emotion, bring them together in a facilitated session, and reach a collaborate/problem-solve win-win. Airing a two-person dispute to the full team as the first step can embarrass the parties, harden their positions, and spread the friction, so the private conversations come first and the joint session second.

The cheapest conflict to manage is the one your ground rules prevented. Ground rules and conflict-management norms, usually captured in a team charter, are the team's agreed expectations for how people work together and how disagreements get handled. Three moves make them work: agree them collaboratively, communicate them widely, and enforce them consistently. The figure below lays out that lifecycle end to end: agree the rules collaboratively so the team co-owns them, communicate them to the team and external stakeholders, then enforce violations consistently.

Agree the rules collaboratively

Set the ground rules with the team, not for the team. Rules the team builds together are rules the team owns, and that ownership is what creates the psychological safety people need to surface concerns instead of burying them. A project manager who dictates a list of rules gets compliance on paper and little else. Establishing an environment that fosters adherence to common ground rules is a named task in the Examination Content Outline^[1], and adherence follows from ownership.

Communicate the principles to the team and external stakeholders

Ground rules kept inside the team fail at the boundary. Share the agreed conflict-management principles with both the team and the external stakeholders who interact with it, so everyone knows how disagreements will be handled and no one operates under different, unstated expectations. Communicating conflict-management principles with the team and external stakeholders is a distinct outline task precisely because internal-only norms break down the moment an outside stakeholder joins the disagreement.

Rectify violations promptly and consistently

When someone breaks an agreed ground rule, address it promptly and consistently, focusing on the behavior rather than the person. Letting minor breaches slide to keep the peace normalizes the violation and erodes the norm for everyone, so consistent, low-drama enforcement is what keeps the rules real. Managing and rectifying ground rule violations is the final task the outline lists under Manage Conflicts.

PMP conflict questions are almost always situational: a short scenario, then four plausible actions. The right answer usually collaborates and confronts the real issue directly; the distractors are the four weaker techniques dressed up to look reasonable. Learn the tells.

The distractor catalog

• "Take the discussion offline" or "table it until after the sprint" is avoidance. It sounds considerate but defers the conflict; the facilitate-in-the-forum answer beats it.
• "Escalate to the sponsor or to HR" as a first move is premature. The project manager owns day-to-day conflict; escalation is right only after a direct attempt has genuinely failed.
• "Reassign the two people to separate work streams" is withdrawing. It removes the friction from view without resolving the cause, which is why it ranks lowest.
• "Direct both parties to accept your decision" is forcing. It is correct only when the scenario is a true emergency or safety issue; on an ordinary disagreement it is the trap.
• "Propose a quick compromise" is tempting because it sounds fair, but it is wrong whenever the scenario leaves room to collaborate to a full win-win. Compromise is second-best, not best.

How to pick the right answer

First check what the scenario is really asking. A mild, healthy disagreement on a self-managing team usually wants "let the team resolve it." An escalated or interpersonal conflict usually wants "meet with each person privately first." Everything else, absent an emergency, wants "bring the parties together and collaborate on the underlying issue." When two answers both look collaborative, prefer the one that first diagnoses the source or clarifies roles over the one that jumps straight to a solution. And when a question describes conflict that recurs, the answer is almost always to clarify roles and responsibilities, not to change your leadership style or avoid the person.