1. What Is Conflict?
Definition & Nature
Conflict in project management is a disagreement, incompatibility, or opposition between two or more parties regarding goals, values, needs, resources, or approaches. Conflict is natural and inevitable in any project environment — it is NOT inherently bad.
PMI's View: Conflict is normal and can be productive when managed well.
It can surface hidden problems, drive creativity, and produce better decisions through constructive debate.
Types of Conflict
- Task Conflict – disagreements over project goals, scope, or deliverables (often healthy)
- Process Conflict – disagreements over how work should be done
- Relationship Conflict – personal friction between individuals (usually destructive)
- Status Conflict – disputes over authority, decision-making rights, or hierarchy
Why It Matters on the PMP Exam
Conflict Management appears across all three PMP domains:
- Domain 1 – People: Task 8 is directly "Negotiate Project Agreements," and Task 9 covers collaboration & conflict
- Domain 2 – Process: Issue logs, risk registers, change requests all involve conflict
- Domain 3 – Business Environment: Stakeholder conflicts on priorities and value
🎯 EXAM TIP
The PMP exam consistently tests which technique to apply when.
Remember: PMI almost always prefers Collaborate/Problem-Solve as the BEST approach,
and Withdraw/Avoid as the LAST resort (unless used temporarily to cool down).
2. Sources of Conflict
7 Major Sources (PMI / Thamhain & Wilemon Study)
| # | Source | Description | Common Phase |
|---|---|---|---|
| 1 | Schedules | Disagreements over timelines, milestones, deadlines | All phases – most common overall |
| 2 | Project Priorities | Competing demands on limited time and resources | Planning & Executing |
| 3 | Resources | Conflicts over who gets scarce people, equipment, or budget | Executing |
| 4 | Technical Opinions | Disagreements on methods, tools, design solutions | Design & Development |
| 5 | Administrative Procedures | Disagreements on reporting, policies, or procedures | Initiating & Planning |
| 6 | Cost | Budget disputes, cost estimates variances | Planning & Monitoring |
| 7 | Personality | Personal clashes, communication styles, ego conflicts | Any phase – least common |
Most Common Source Per Phase
Initiating: Priorities & Administrative Procedures
Planning: Priorities & Schedules
Executing: Schedules & Technical Opinions
Closing: Schedules (rush to finish)
🎯 EXAM TIP
Schedules = #1 source of conflict in projects overall.
Personality = least common source. If the exam asks "what is the MOST common source" → answer Schedule/Time.
3. Five Conflict Resolution Techniques
PMI recognizes five techniques drawn from the Thomas-Kilmann Conflict Mode Instrument. Each varies along two axes: Assertiveness (concern for self) and Cooperativeness (concern for others).
✅ BEST — PMI PREFERRED
1. Collaborate / Problem-Solve (Win-Win)
- All parties openly address the conflict and work together to find the best solution
- Requires trust, time, and willingness to share information
- Both parties' concerns are fully addressed → lasting resolution
- Produces highest quality decisions and maintains relationships
Example: A developer and a QA engineer disagree on release criteria. The PM facilitates a workshop where both define clear, measurable acceptance criteria acceptable to both teams.
PMI says: Use this FIRST when possible. It is the ONLY technique that produces a true win-win outcome.
⚖️ ACCEPTABLE — Use when collaboration isn't possible
2. Compromise / Reconcile (Lose-Lose)
- Each party gives up something to reach a middle-ground agreement
- Provides a temporary or partial resolution
- Neither side is fully satisfied — hence "lose-lose" (both lose a little)
- Useful when both parties have equal power and time is limited
Example: Two teams want the same senior engineer. PM negotiates: one team gets the engineer Mon–Wed, the other Thu–Fri, and both adjust their plans accordingly.
Note: PMI recognizes compromise as a valid technique but NOT the preferred one. It may reopen later.
🤝 SITUATIONAL — Short-term only
3. Smooth / Accommodate (Yield)
- Emphasize areas of agreement; downplay or minimize areas of difference
- Preserves the relationship at the expense of the problem resolution
- One party yields to the other's position to maintain harmony
- Good for trivial issues or when you need goodwill for a bigger issue later
Example: PM lets the client choose the meeting day even though Thursday is inconvenient, to preserve goodwill on a larger scope negotiation.
Warning: Does NOT resolve the underlying conflict. The issue will likely resurface.
⚠️ USE WITH CAUTION — Short-term, authority-based
4. Force / Direct (Win-Lose)
- PM pushes one party's viewpoint using authority, power, or rank
- Creates a winner and a loser — damages relationships if overused
- Appropriate in emergencies or when a quick, decisive action is required
- Also used when the issue is non-negotiable (safety, legal, ethical)
Example: During a safety incident, PM orders immediate work stoppage despite team pushback. Safety is non-negotiable.
Note: Least effective for long-term morale. Use for emergencies or mandatory compliance situations.
❌ AVOID (usually) — Last resort
5. Withdraw / Avoid (Retreat)
- Postpone or retreat from the conflict — neither assertive nor cooperative
- Issue is left unresolved and can escalate over time
- Sometimes appropriate to allow cooling-off period or gather more information
- Acceptable if the conflict is trivial and will resolve itself
Example: Two team members have a heated argument during a stressful sprint. PM asks them to step away and reconvene after lunch. (Temporary withdrawal is OK.)
PMI says: This is generally the WORST technique. It doesn't solve anything long-term.
🎯 EXAM TIP — The Ranking
PMI-preferred order: Collaborate → Compromise → Smooth → Force → Withdraw
Memory trick: "Cheerful Comrades Smoothly Fight Wars" (Collaborate, Compromise, Smooth, Force, Withdraw)
4. When to Use Each Technique
| Technique | Use When… | Outcome | Time Needed |
|---|---|---|---|
| Collaborate | Issue is important; time is available; trust exists; long-term relationship matters | Win-Win ✅ | High |
| Compromise | Both parties have equal power; temporary solution acceptable; relationship important | Lose-Lose ⚖️ | Medium |
| Smooth | Issue is minor; goodwill needed; relationship > outcome; buy time | Yield 🤝 | Low |
| Force | Emergency; safety/legal issue; quick decision required; authority is clear | Win-Lose ⚡ | Very Low |
| Withdraw | Issue is trivial; more info needed; emotions are too high; will resolve itself | No resolution ❌ | None (delay) |
Real Scenario: Which Technique?
Scenario A: Two engineers argue over which testing tool to use. Both have valid technical points. The PM has 2 weeks before the testing phase begins.
→ COLLABORATE. Time exists; issue is important; true agreement will last.
→ COLLABORATE. Time exists; issue is important; true agreement will last.
Scenario B: Two PMs from different departments both need the same testing lab for the same week.
→ COMPROMISE. Both have equal standing; split the lab time 50-50.
→ COMPROMISE. Both have equal standing; split the lab time 50-50.
Scenario C: A team member complains about the coffee machine location. The PM disagrees but it's trivial.
→ SMOOTH. Issue is minor; no real project impact; maintain goodwill.
→ SMOOTH. Issue is minor; no real project impact; maintain goodwill.
Scenario D: A worker refuses to wear a hard hat on site. Safety violation. Immediate danger.
→ FORCE. Safety is non-negotiable; PM must use authority immediately.
→ FORCE. Safety is non-negotiable; PM must use authority immediately.
Scenario E: Two team members have a very heated personal argument. Everyone is emotional and nothing productive can happen right now.
→ WITHDRAW (temporarily). Allow cooling-off. Revisit with Collaborate later.
→ WITHDRAW (temporarily). Allow cooling-off. Revisit with Collaborate later.
5. Conflict in the Project Lifecycle
The frequency and type of conflict changes as the project progresses:
| Phase | Common Conflict | Typical Technique |
|---|---|---|
| Initiating | Priorities, roles & responsibilities, scope boundaries | Collaborate, Smooth |
| Planning | Schedule, resources, budget estimates, technical approach | Collaborate, Compromise |
| Executing | Schedule pressure, resource sharing, technical opinions, personality | Compromise, Force (if safety) |
| Monitoring & Controlling | Change requests, cost variances, scope creep disputes | Collaborate, Compromise |
| Closing | Lesson learned debates, unresolved scope items, team transition | Smooth, Collaborate |
💡 KEY INSIGHT
Conflict tends to peak during Executing because that's when teams are under the most schedule and resource pressure simultaneously.
Good PMs anticipate this and build conflict-resolution time into their plans.
Agile Context
In Agile / Scrum environments, conflict is managed more frequently and transparently:
- Daily Standups surface conflicts early (impediments)
- Retrospectives are the primary venue for resolving team conflicts
- The Scrum Master acts as a servant leader and conflict facilitator
- Agile teams are expected to be self-organizing — they resolve conflicts without PM intervention when possible
- Kanban uses WIP limits to reduce resource conflict
6. The Project Manager's Role in Conflict
PM as Conflict Facilitator
The PM is NOT a judge or a police officer. The PM's role is to facilitate resolution, not impose it.
- Identify the conflict early — watch for warning signs (missed meetings, hostile emails, decreased productivity)
- Understand the root cause — is it schedule, resource, personality, or something else?
- Bring parties together — private discussions first, then joint if needed
- Apply the right technique — default to Collaborate; escalate if needed
- Document the resolution — update the Issue Log
- Follow up — verify the resolution held; watch for recurrence
Key PM Behaviors (PMI Mindset)
✅ DO: Address conflict directly and promptly
❌ DON'T: Ignore or hope it resolves itself (Withdraw as default)
✅ DO: Remain neutral and impartial
❌ DON'T: Take sides or show favoritism
✅ DO: Focus on issues, not personalities
❌ DON'T: Allow personal attacks or blame
✅ DO: Keep discussions private when possible
❌ DON'T: Air conflicts in public forums or large meetings
🎯 EXAM TIP — Active Listening
PMP exam questions often test whether the PM uses active listening during conflict resolution.
Active listening = paraphrase what you heard, ask clarifying questions, don't interrupt, acknowledge emotions.
This is ALWAYS the right first step before choosing a resolution technique.
7. Escalation Path
Not all conflicts can be resolved at the PM level. Here is the proper escalation path:
Team Members attempt self-resolution
↓ Project Manager facilitates
↓ Functional Manager / Department Head gets involved
↓ Sponsor / Senior Management makes final call
↓ PMO / Steering Committee (for organization-level conflicts)
↓ Project Manager facilitates
↓ Functional Manager / Department Head gets involved
↓ Sponsor / Senior Management makes final call
↓ PMO / Steering Committee (for organization-level conflicts)
When to Escalate
- Conflict involves decisions above the PM's authority (budget changes, scope changes, resource allocation from another department)
- Conflict is unresolvable at the current level after reasonable attempts
- Conflict involves ethical violations, harassment, or discrimination
- Conflict threatens the project's critical path or key deliverables
- A team member is in safety danger
⚠️ IMPORTANT
Escalation is NOT failure. It is a professional responsibility.
PMI expects the PM to escalate appropriately rather than struggle alone with unresolvable conflicts.
Failure to escalate when needed is a PM failure.
🎯 EXAM TIP — Escalation Order
If the exam asks what to do when you can't resolve a conflict → first try Collaborate, then if still stuck → escalate to the Sponsor or functional manager.
Never go directly to senior management without trying resolution first.
8. Key Models & Frameworks
Thomas-Kilmann Conflict Mode Instrument (TKI)
The TKI model maps the five techniques on two axes:
HIGH │ Force Collaborate
│ (Win-Lose) (Win-Win)
A │
S │
S │ Compromise
E │ (Lose-Lose)
R │
T │ Withdraw Smooth
│ (No outcome) (Yield)
LOW └──────────────────────────
LOW COOPERATIVENESS HIGH
- Collaborate = High assertiveness + High cooperation → the ideal zone
- Compromise = Medium/medium → middle ground
- Force = High assertiveness + Low cooperation → authoritative
- Smooth = Low assertiveness + High cooperation → yielding
- Withdraw = Low assertiveness + Low cooperation → passive
PMI / PMBOK Approach
The PMBOK Guide (7th edition) discusses conflict under Team Performance Domain and emphasizes:
- Conflict resolution is part of team development
- The PM applies emotional intelligence — self-awareness, empathy, social skills
- PMI Code of Ethics requires honesty, respect, fairness in all conflict handling
- Use of RACI Matrix and RAM to prevent role-conflict proactively
Tuckman's Team Development & Conflict
| Stage | Conflict Level | PM Action |
|---|---|---|
| Forming | Low (polite uncertainty) | Set expectations, build trust |
| Storming | HIGH (peak conflict) | Apply conflict techniques; be visible |
| Norming | Declining | Reinforce norms and agreements |
| Performing | Low (healthy debate) | Step back; team is self-managing |
| Adjourning | Medium (anxiety about closure) | Recognize contributions; lessons learned |
🎯 EXAM TIP — Storming
Conflict peaks during the Storming stage of team development.
The PM should be most actively involved in conflict management during Storming.
This maps to the Executing phase of the project lifecycle.
9. Real-World Scenarios
Scenario 1 — Resource Conflict (Engineering Project)
Situation: You are a PM on a bridge rehabilitation project. Two superintendents both need the only concrete pump on site on the same day — one for deck pours, one for pier caps.
Analysis: This is a resource conflict (schedule-driven). Both have valid needs. No safety issue.
Best Approach: Collaborate → Sit with both superintendents, review the schedule, and find a sequencing solution that satisfies both while keeping the critical path intact. If no clean solution exists → Compromise (one pours AM, one pours PM).
Analysis: This is a resource conflict (schedule-driven). Both have valid needs. No safety issue.
Best Approach: Collaborate → Sit with both superintendents, review the schedule, and find a sequencing solution that satisfies both while keeping the critical path intact. If no clean solution exists → Compromise (one pours AM, one pours PM).
Scenario 2 — Stakeholder vs. Team (IT Project)
Situation: A key stakeholder demands a feature be added mid-sprint that the dev team says will require 2 weeks. The stakeholder says it's "critical."
Analysis: Scope conflict + priority conflict. Classic Agile tension.
Best Approach: Collaborate with stakeholder and Product Owner to evaluate business value, add the feature to the backlog, and reprioritize. Do not allow scope to be forced into the sprint without team consent.
Analysis: Scope conflict + priority conflict. Classic Agile tension.
Best Approach: Collaborate with stakeholder and Product Owner to evaluate business value, add the feature to the backlog, and reprioritize. Do not allow scope to be forced into the sprint without team consent.
Scenario 3 — Personality Clash
Situation: Two senior developers consistently have hostile email exchanges. Other team members are affected. Productivity is dropping.
Analysis: Relationship/personality conflict. Cannot be ignored.
Best Approach:
Analysis: Relationship/personality conflict. Cannot be ignored.
Best Approach:
- Meet with each person privately (active listening)
- Set clear behavioral expectations (ground rules)
- Bring both together to Collaborate on a working agreement
- If it continues → escalate to HR / functional manager
Scenario 4 — Emergency Safety Conflict
Situation: During a highway construction project, a crew member refuses to follow a lane closure plan because "it takes too long to set up." Traffic control is compromised.
Analysis: Safety violation. Non-negotiable. No time for discussion.
Best Approach: Force/Direct immediately. Stop work. Enforce MUTCD compliance. Document the incident. Brief the crew afterward.
Analysis: Safety violation. Non-negotiable. No time for discussion.
Best Approach: Force/Direct immediately. Stop work. Enforce MUTCD compliance. Document the incident. Brief the crew afterward.
10. Exam Tips — Master List
🎯 TIP 1 — Default Answer
When in doubt, PMI's preferred answer is always Collaborate/Problem-Solve.
If you see "the PM should..." and none of the wrong options explicitly say collaborate, look for the option that involves bringing parties together, open discussion, or finding a mutually acceptable solution.
🎯 TIP 2 — Avoid Avoid
Withdraw/Avoid is almost never the right PMP answer. If you see "ignore the conflict" or "let it resolve on its own" → that's wrong in 90% of PMP scenarios.
Exception: "temporarily withdraw to allow emotions to cool" is acceptable as a first step.
🎯 TIP 3 — Force vs. Collaborate
Force is only right when: (a) safety/legal/ethics are involved, (b) it's an emergency, or (c) the PM has clear authority and time is critical.
If none of those apply → Collaborate.
🎯 TIP 4 — Source Ranking
Most common = Schedules. Least common = Personality.
These are tested frequently in straightforward knowledge questions.
🎯 TIP 5 — Agile Questions
In Agile scenarios: the Scrum Master facilitates conflict. The team self-organizes.
Retrospectives = the formal mechanism for resolving team-level conflict in Agile.
Daily standups = surface conflicts (impediments) early.
🎯 TIP 6 — Document Everything
After any conflict resolution, the right answer is to update the Issue Log.
If it involves scope or change, a Change Request may be required too.
🎯 TIP 7 — Proactive > Reactive
PMI wants PMs who prevent conflicts before they start:
clear roles (RACI), team charters, ground rules, stakeholder engagement plans.
If the exam offers "create ground rules" as an option → it's often correct for prevention-type questions.
🎯 TIP 8 — Win-Win Terminology
"Win-Win" = Collaborate. "Lose-Lose" = Compromise. "Win-Lose" = Force.
These outcome labels appear directly in PMP questions. Know them cold.
🎯 TIP 9 — Emotional Intelligence
PMP 2021+ exam emphasizes EI heavily. The PM should demonstrate empathy, self-regulation, and social awareness in conflict situations.
If an answer shows the PM listening, acknowledging feelings, and then problem-solving → likely correct.
🎯 TIP 10 — Ethics & Fairness
The PMI Code of Ethics requires the PM to be honest, fair, and respectful.
Any conflict resolution that involves deception, favoritism, or coercion (outside of genuine safety) violates the code → wrong answer.
11. ⚡ Cheat Sheet
BEST Technique
Collaborate / Problem-Solve
→ Win-Win · Long-term fix
Collaborate / Problem-Solve
→ Win-Win · Long-term fix
WORST Technique
Withdraw / Avoid
→ No resolution · Problem grows
Withdraw / Avoid
→ No resolution · Problem grows
Top Conflict Source
Schedules / Time
→ Most common in ALL phases
Schedules / Time
→ Most common in ALL phases
Least Common Source
Personality
→ But most destructive when it occurs
Personality
→ But most destructive when it occurs
Agile Conflict Venue
Retrospective (resolve) + Standup (surface)
→ Scrum Master facilitates
Retrospective (resolve) + Standup (surface)
→ Scrum Master facilitates
Tuckman Peak Conflict
Storming Stage
→ PM most active here
Storming Stage
→ PM most active here
Document After Resolution
Issue Log (always)
→ Change Request if scope impacted
Issue Log (always)
→ Change Request if scope impacted
Outcome Labels
Win-Win · Lose-Lose · Win-Lose · Yield
Collab · Comp · Force · Smooth
Win-Win · Lose-Lose · Win-Lose · Yield
Collab · Comp · Force · Smooth
| Technique | Also Called | Outcome | PMI Ranking |
|---|---|---|---|
| Collaborate | Problem-Solve, Confront | Win-Win | #1 BEST ✅ |
| Compromise | Reconcile | Lose-Lose (partial) | #2 |
| Smooth | Accommodate, Yield | Give in | #3 |
| Force | Direct, Compete | Win-Lose | #4 |
| Withdraw | Avoid, Retreat | No outcome | #5 WORST ❌ |
12. Key Terms — Click for Definition
Click any term below for a quick explanation:
Conflict
Thomas-Kilmann Model
Collaborate/Problem-Solve
Compromise
Smooth/Accommodate
Force/Direct
Withdraw/Avoid
Schedule Conflict
Personality Conflict
Issue Log
RACI Matrix
RAM
Scrum Master
Kanban
Storming Stage
Emotional Intelligence (EI)
Escalation
Ground Rules
Team Charter
Active Listening
Project Priorities
Resource Conflict
Technical Opinion Conflict
WIP Limits
13. Practice Quiz