Demo environment — data may be reset without notice. Not for production use.
VanillaPM
Sign in Get started free Dashboard
P2 People · 33%

Manage conflicts

In the app: Project → Team → Conflict

PMP ECO · People (33%) · Task P2. Surface disagreement early, get to the root cause, and resolve it in a way that keeps the relationship and the work intact.

How to manage conflict — the short version

What it is

Conflict on a project is normal and often useful. It exposes hidden assumptions and better options. The task is to manage it, not suppress it: interpret the source, keep it focused on the issue (not the person), and drive to a resolution the parties own. PMBOK® 8e leans on collaborate / problem-solve as the healthiest default among the classic modes (withdraw, smooth, compromise, force, collaborate).

Most project conflict comes from the work, not the people: competing priorities, scarce resources, schedules, technical opinions, and unclear roles. Personality clashes are real, but they're the least common root cause, and often a symptom of one of the others.

Why it matters

  • Unmanaged conflict festers into schedule slips, silent non-compliance, and attrition.
  • The way a PM handles conflict sets the team's norms. Resolve one fairly and openly, and the team learns it's safe to raise the next one.

Where you do it in VanillaPM

Everything lives in the project's Team workspace:

  • Team → Guideline carries the playbook: the five strategies and the four steps.
  • Team → Conflict is the log. Log a conflict opens a record with the parties, the root cause, the strategy chosen, how far along the four steps it is, and the resolution.
  • Team → Overview shows the open and resolved counts next to the team's Tuckman stage and morale, so a spike in conflict reads in context.
  • Team → Charter is where the team agrees its conflict-resolution process before the first disagreement. People accept a process they helped write.

The log is restricted: only the PM, the sponsor and the people involved can see an entry. A conflict log the whole team can read harms the psychological safety it exists to protect.

Walked example — Coral Ridge Resort

On Coral Ridge, the site engineer and the MEP lead clash over the ceiling void on the sea-view floors. MEP needs depth for ducting, but the brand standard fixes the five-star ceiling height. Logged as a conflict, the root cause turns out to be unclear roles: nobody owned the coordination between the structural and MEP models, so the clash surfaced on site instead of in design. It's not a personality issue. Strategy: collaborate, through a joint BIM clash-resolution session. The fix is to re-route the main duct through the corridor bulkhead. When it lands, the record is closed and the fix feeds a design note.

The record — the theory behind each step

A conflict record isn't paperwork. Each field forces one of the decisions the theory says you should make on purpose. Every screenshot below is the actual sample project, not a mock-up.


1 · Choose the strategy deliberately

The theory: assertiveness × cooperation. The five modes come from the Thomas–Kilmann model. Each one is a different mix of pushing for your outcome (assertiveness) and working for theirs (cooperation):

Strategy Assertive Cooperative Result Use it when…
Collaborate / problem-solve high high win-win there's time, and both needs matter. The default
Compromise / reconcile mid mid lose-lose (partial) a genuine trade-off, or a deadline is forcing a quick middle ground
Smooth / accommodate low high temporary the issue is minor and the relationship matters more
Force / direct high low win-lose safety, ethics or an emergency, where a decision can't wait
Withdraw / avoid low low postponed tempers need cooling first. It comes back
Coral Ridge — the five strategies and four steps, in the Team Guideline
Coral Ridge — the five strategies and four steps, in the Team Guideline

Reading the screenshot: the app keeps the playbook next to the log, so the PM picks a strategy rather than drifting into one. Note how it frames forcing as a "last resort" and withdrawing as "cools things down but the conflict returns". The last line tells you to record a resolution, never blame.

✅ Do name the strategy before you act. A conscious compromise is a decision; an accidental one is just fatigue.
❌ Avoid treating smoothing as kindness. "Let's not make a fuss" hides the issue, and it comes back bigger.


2 · Log the cause and the people, not the blame

The theory: the four steps. Resolution follows a sequence. Skipping a step is the most common way a "resolved" conflict reopens:

  1. Acknowledge. Say out loud that there's a conflict. Unnamed conflict can't be managed.
  2. De-escalate. Lower the temperature, meet face to face, and separate the people from the problem.
  3. Analyze. Find the root cause: priorities, resources, roles, or (least often) personality.
  4. Select & resolve. Choose the strategy, act, and confirm the parties accept the outcome.
Coral Ridge — the record behind the open MEP conflict
Coral Ridge — the record behind the open MEP conflict

Reading the screenshot: the summary names the problem ("MEP vs structure: sea-view ceiling void"), not the people. The context explains why it happened. The root cause is Unclear roles, a process gap the PM can fix, rather than "Tanvir vs Imran". The three involved parties are ticked, which is also what lets each of them see the record. The 4-step progress says Analyze: the BIM session is still finding the answer, so the status stays Open.

✅ Do pick the root cause before the strategy. Collaborating on the wrong cause just produces a well-agreed wrong fix.
❌ Avoid writing the summary as a grievance. If a party would be embarrassed to read it, rewrite it. They can see it.


3 · Track it to closure, and read the patterns

The theory: a resolution is confirmed, not declared. A conflict is resolved when the parties own the outcome and the underlying cause has been addressed, not when the argument stops. Across a project, the log also shows patterns: three "unclear roles" entries in the same area mean the RACI needs work, not three more meetings.

Coral Ridge — the conflict log: one open, one resolved
Coral Ridge — the conflict log: one open, one resolved

Reading the screenshot: the open MEP clash sits at the top with its parties listed. Below it, the beach-access conflict is Resolved, and its resolution says what changed: a public corridor added to the site plan and a local-hiring commitment. That moved the community from resistant toward neutral. A good resolution note records the outcome, so the next PM can learn from it.

✅ Do close the record only when the fix is in place, and write the outcome in a sentence a newcomer would understand.
❌ Avoid a log that only grows. If entries stay open for months, the log has become a complaints box rather than a resolution tool.

Best practices & pitfalls

  • Do address conflict early and directly. The cost of resolution rises the longer it sits.
  • Do separate the person from the problem; log the root cause, not blame.
  • Do prefer collaborate/problem-solve; reserve compromise for genuine trade-offs and force for safety/ethics red lines.
  • Do agree the conflict-resolution process in the team charter before you need it.
  • Pitfall: smoothing ("let's not make a fuss"). It hides the issue and it comes back bigger.
  • Pitfall: escalating to the sponsor first. Escalate only after you've genuinely tried to resolve it at team level.

On the PMP exam

Conflict questions are a staple of the People domain. The exam almost always rewards the face-to-face, collaborate-first response, and expects the PM to get to the root cause before proposing a fix. Watch for answers that escalate to the sponsor immediately or avoid the conversation. Those are usually the distractors. When two good answers remain, pick the one that follows the four steps in order: acknowledge and de-escalate before you analyse and resolve.

Check your understanding a short quiz — pass to mark the task complete