Conflict Management: 5 Techniques & PMBOK 8 Steps

1. Conflict is inevitable — but not always harmful

Many PMs treat conflict like a "house fire" — something to extinguish immediately. But PMBOK 8 takes a very different perspective:

PMBOK® 8, Section 5 — Conflict Management: "Successful conflict management results in greater productivity and positive working relationships. When managed properly, differences of opinion can lead to increased creativity and better decision-making."

Conflict has two sides:

A skilled PM does not eliminate all conflict — instead, they create an environment where constructive conflict is encouraged, while destructive conflict is detected early and resolved decisively.

2. The seven most common sources of conflict in projects

PMBOK 8 confirms: "Sources of conflict include scarce resources, scheduling priorities, and personal work styles." Expanding on this, the 7 most common conflict sources are ranked from most frequent → least frequent:

💡 PMP exam tip: "Schedules" is the #1 most common source of conflict. "Personality" is the least common. Exam questions frequently ask "what is the MOST common source of conflict?" — do not mistake it for "personality clashes," even though that sounds more dramatic.

3. The 6-step conflict management framework per ECO

The PMP ECO identifies 6 enablers for Manage Conflicts, forming a complete process from prevention to resolution:

⚠️ Note: Although steps 5–6 (prevention) are listed last, in practice you should establish ground rules FIRST — right from the moment the team is formed. The ECO ordering reflects analysis logic (what to do when conflict occurs), but an effective PM invests in prevention from the very beginning.

4. Steps 1–2: Identify conflict sources and analyze context

Step 1: Identify Conflict Sources

Conflict has symptoms and root causes. The PM must distinguish between them: two developers arguing about code style is a symptom — the root cause may be a dispute over architectural control, deadline-driven stress, or a lack of clear coding standards.

Identification techniques include: observing team behavior (who avoids whom, who frequently disagrees), listening during daily standups and retrospectives, analyzing patterns (where and when conflict recurs), and one-on-one conversations (many hidden conflicts only surface in private).

Step 2: Analyze the Context

Not all conflicts are handled the same way. PMBOK 8 lists 5 context factors that determine which technique you should use:

Real-world example: a conflict between the PM and the sponsor over the timeline — the sponsor holds more power (relative power), the relationship is critically important (relationship), and a long-term solution is needed (long-term). → Collaborate or Compromise is appropriate; Force will backfire.

5. Five conflict resolution techniques — choosing the right one for each situation

PMBOK 8 states precisely: "There are five general techniques for resolving conflict. Each technique has its place and use." No single technique is always correct — each fits a different context.

The golden rule for PMP: PMI consistently prioritizes Collaborate/Problem-Solve (Win-Win) as the best method for long-term conflict resolution. On the exam, if this option is available and the scenario allows time — choose Collaborate. Only select another technique when the scenario explicitly states that collaboration is not possible (e.g., emergency, extreme deadline, safety issue).

Quick-selection matrix

Compromise sits in the middle: when both the issue and the relationship are of moderate importance, or when a quick temporary solution is needed.

6. Steps 3–4: Implement the resolution strategy and communicate principles

Step 3: Implement an Agreed-on Resolution Strategy

The most important keyword here is "agreed-on" — the resolution strategy must be agreed upon by all parties, not unilaterally decided by the PM.

Standard process: Analyze context (steps 1–2) → Select the appropriate technique → Present options to all parties → Reach agreement → Execute → Monitor results → Document lessons learned.

PMBOK 8 also clearly defines the team's role:

PMBOK® 8: "If the differences become a negative factor, project team members are initially responsible for their resolution. If conflict escalates, the project manager should help facilitate a satisfactory resolution."

This means: the PM should not jump in to resolve every conflict. The first step is always to let the team handle it themselves. The PM intervenes only when the conflict escalates or the team cannot resolve it on their own.

Step 4: Communicate Conflict Management Principles

The PM needs to clearly communicate the project's conflict management principles to both the internal team and external stakeholders. PMBOK 8 suggests 4 communication principles when dealing with conflict:

1. - Keep communication open and respectful — "It is important to keep a safe environment to explore the source of the conflict. Without a safe environment, people will stop communicating."

2. - Focus on the issues, not the people — "Conflicts should not be personal. The focus is on resolving the situation, not casting blame."

3. - Focus on the present and future, not the past — "If something similar happened previously, bringing up the past will not resolve the current situation."

4. - Search for alternatives together — "This collaboration can create more constructive relationships... moves the conflict into a problem-solving space."

7. Steps 5–6: Establish ground rules and manage violations

Step 5: Establish Ground Rules

Prevention is better than cure. PMBOK 8 states clearly: "Team ground rules, group norms, and solid project management practices, such as communication planning and role definition, can reduce the amount of conflict."

The Team Charter is the primary tool — PMBOK 8 defines it as including: team values, communication guidelines, decision-making criteria and processes, conflict resolution processes, meeting guidelines, and team agreements.

The most important point: the team must participate in creating the ground rules, rather than having them imposed by the PM. PMBOK 8 notes that discussing areas like "codes of conduct, communication, decision-making, and meeting etiquette allows team members to discover values that are important to one another." The process of discussing ground rules is itself a team-building activity.

Step 6: Manage and Rectify Violations

Ground rules only have value when enforced consistently. A 5-step process for handling violations:

1. - Identify — Detect the violation through observation, team feedback, or retrospectives

2. - Speak privately — Have a private conversation with the person who violated the rule to understand the cause

3. - Remind and gain commitment — Reiterate the ground rules and ask for a commitment to comply

4. - Monitor — Observe behavior after the reminder

5. - Escalate if needed — If violations continue, apply formal procedures

PMBOK® 8: "Conflict should be addressed early and usually in private, using a direct, collaborative approach. If disruptive conflict continues, formal procedures may be used, including disciplinary actions."

🌟 The PM should also remember: "All project team members share responsibility for ensuring the rules documented in the team charter are followed." — Responsibility for compliance belongs not just to the PM, but to the entire team.

8. Emotional Intelligence — the PM's secret weapon

PMBOK 8 lists Emotional Intelligence (EI) as a separate tool within Lead the Team — and it is critically important for conflict management.

PMBOK® 8, Section 5: "Emotional intelligence is the ability to identify, assess, and manage the personal emotions of oneself and other people, as well as the collective emotions of groups of people."

Four pillars of EI applied to conflict:

🌟 PMBOK 8 emphasizes: "A project manager should invest in their personal emotional intelligence by improving inbound (self-management and self-awareness) and outbound (relationship management) competencies." EI is not an innate talent — it is a skill that can be developed.

9. PMP exam tips on Conflict Management

📍 Tip 1 — Default answer = Collaborate: When the question does not specify time pressure or an emergency — the default answer is always Collaborate/Problem-Solve (Win-Win). Only select another technique when the scenario explicitly states a constraint (e.g., "the deadline is tomorrow," "this is a safety issue").

📍 Tip 2 — "Address early, in private": PMBOK 8 is clear: conflict should be addressed early and usually in private. When an exam question asks "what should the PM do FIRST?" — the answer is usually NOT "address it publicly in the meeting" or "send an email to the whole team."

📍 Tip 3 — Team solves first, PM facilitates: When conflict arises between team members — the PM should let the team try to resolve it first and only intervene when it escalates. The answer "PM directly resolves the conflict" is usually wrong unless the scenario states "the team has already tried and failed."

📍 Tip 4 — Escalation is not failure: When the PM has made a genuine effort to resolve the conflict without success — escalating to management or HR is the appropriate next step. PMBOK 8: "If disruptive conflict continues, formal procedures may be used." Escalation is NOT failure — it is proper process management.

10. Ten situational practice questions

Question 1

Two senior developers disagree about the database architecture. Developer A wants NoSQL for flexibility; Developer B insists on relational for data integrity. Both have valid technical arguments, and the decision will significantly impact long-term maintainability. There is no time pressure.

What conflict resolution technique should you apply?

A. Force/Direct — Choose the solution you believe is best since you're the PM.

B. Compromise — Use NoSQL for some modules and relational for others.

C. Collaborate/Problem-Solve — Facilitate a workshop where both developers analyze requirements together and reach consensus.

D. Smooth/Accommodate — Ask Developer A to accept Developer B's approach to maintain harmony.

Question 2

During a daily standup, a team member publicly criticizes another's code quality, calling it "sloppy and unprofessional." The criticized member looks visibly upset. Other team members appear uncomfortable.

What should you do FIRST?

A. Address the criticism publicly during the standup to set an example about respectful behavior.

B. Redirect the standup to focus on progress updates, then speak privately with the criticizing team member about the ground rules.

C. Ask both team members to resolve the issue between themselves.

D. Document the incident in the issue log and discuss at the next retrospective.

Question 3

A client representative and your site engineer have been arguing for two weeks about structural support placement. The disagreement is delaying the critical path. Both have rejected each other's proposals twice.

What approach is MOST appropriate?

A. Compromise — place supports in an intermediate location.

B. Bring in an independent structural expert to provide data, then facilitate a collaborative discussion based on the expert's findings.

C. Apply Force — go with the engineer's recommendation since they're responsible for site execution.

D. Escalate to the sponsor for a binding decision.

Question 4

You are assembling a new team from three departments. During the kickoff, you notice tension between marketing and engineering — they have a history of blaming each other for failures in previous projects.

What is the BEST proactive approach?

A. Separate them into different work streams to avoid interaction.

B. Facilitate the creation of a team charter with conflict resolution processes, communication guidelines, and team agreements — with input from all members.

C. Meet individually with each department to mediate past grievances.

D. Set clear expectations that past conflicts won't be tolerated.

Question 5

A team member from India consistently misses code review deadlines, causing US team delays. Investigation reveals the deadlines fall during their evening family time due to the 12-hour time zone difference. The US team is frustrated.

How should you approach this conflict?

A. Remind the Indian member they agreed to the ground rules and must comply.

B. Remove them from the code review rotation.

C. Analyze the root cause (time zone context), then facilitate a collaborative schedule adjustment that works for both parties while meeting project needs.

D. Alternate the review deadline between time zones each sprint.

Question 6

During a retrospective, a junior team member says: "I feel like my ideas are always dismissed by the senior members. I've stopped suggesting improvements." Two seniors immediately become defensive.

What should you do?

A. Thank the junior member for honesty, defuse the defensiveness, and facilitate a discussion about creating a safer environment for all ideas.

B. Ask the junior member to provide specific examples so seniors can respond.

C. Move on and address privately after the meeting.

D. Remind the team that retrospectives are about process, not personal issues.

Question 7

Your vendor consistently delivers components below quality standards. When you raise concerns, their PM says "everything is on track." This has happened three times. Your QA team rejects the deliverables each time.

What is the BEST approach?

A. Issue a formal notice of non-compliance referencing contract terms.

B. Organize a joint review session with both teams to examine specifications together, identify where misunderstandings occur, and establish a shared quality checklist.

C. Accept deliverables with minor defects to maintain the timeline.

D. Replace the vendor.

Question 8

Two experienced team members have a strong personal dislike for each other. Despite two private conversations, their behavior is creating a toxic atmosphere — whispering in meetings, refusing to collaborate, and making passive-aggressive comments.

What should you do NEXT?

A. Separate them into different work streams.

B. Escalate to their functional managers and/or HR, as the conflict has moved beyond what informal methods can resolve.

C. Try one more collaborative discussion with both in the room.

D. Wait for their performance review to address formally.

Question 9

The project sponsor says: "I need this feature delivered by Friday — no excuses." The lead developer says: "It's technically impossible in 3 days without cutting quality significantly." Both look at you.

How should you handle this?

A. Support the sponsor — they have authority over the project.

B. Support the developer — technical reality should drive decisions.

C. Present the trade-offs transparently: what's achievable by Friday, what the quality risks are, and what alternatives exist — let the sponsor make an informed decision.

D. Propose a compromise of partial delivery by Friday.

Question 10

You notice that a team member has been privately complaining about your management style to other members, calling you a "micromanager." Team morale has declined and some members seem hesitant to share updates with you.

What is the BEST approach?

A. Confront the team member and explain that undermining the PM is unprofessional.

B. Ignore the complaints and focus on delivering results.

C. Reflect on the feedback with self-awareness, then have an open, non-defensive conversation with the team member to understand their perspective and collaboratively adjust your approach.

D. Raise the issue at the next team meeting for transparent discussion.

Answer Key

Question 1: Answer: C

— This is a significant technical decision with long-term impact and no time pressure. PMBOK 8: Collaborate "incorporates multiple viewpoints and insights from differing perspectives." Both developers have valid arguments — collaboration may reveal a solution that combines the best of both approaches.

Question 2: Answer: B

— PMBOK 8: "Conflict should be addressed early and usually in private." Addressing it publicly could embarrass both parties and escalate. Leaving them alone (C) ignores a ground rule violation. Waiting for retrospective (D) delays too long. Redirect the standup first, then address privately.

Question 3: Answer: B

— After two weeks of failed negotiation, new input is needed. An expert provides objective data that breaks the deadlock and enables collaboration. Compromise (A) may create a technically unsound solution. Force (C) damages client relationship. Escalating (D) is premature when there's still a collaborative option.

Question 4: Answer: B

— PMBOK 8: "The team charter establishes clear expectations... Early commitment to clear guidelines decreases misunderstandings and increases productivity" and "works best when the team develops it." Separating (A) avoids the issue. Past mediation (C) doesn't establish forward-looking rules. Top-down expectations (D) lack buy-in.

Question 5: Answer: C

— The root cause is a time zone conflict, not poor work ethic. PMBOK 8 emphasizes cultural awareness and adapting communication strategies. Enforcing rules without context (A) ignores legitimate constraints. Removing them (B) wastes talent. Imposed compromise (D) lacks collaboration.

Question 6: Answer: A

— This is a ground rules and psychological safety issue. PMBOK 8's Build an Empowered Culture emphasizes creating environments where team members "contribute ideas freely." Asking for examples (B) puts a vulnerable person on the spot. Moving on (C) signals the concern isn't valued. Dismissing as "personal" (D) shuts down feedback.

Question 7: Answer: B

— This is a recurring conflict with a pattern. PMBOK 8's Be an Accountable Leader: "explore the root cause of the issue and identify acceptable adjustments." Joint review = Collaborate/Problem-Solve. Formal notice (A) may be needed later but isn't the first step. Compromising quality (C) undermines value. Replacement (D) is premature.

Question 8: Answer: B

— PMBOK 8: "If disruptive conflict continues, formal procedures may be used, including disciplinary actions." Two private attempts have failed — the informal route is exhausted. Separation (A) is a workaround. Another conversation (C) is unlikely to succeed. Waiting (D) lets the toxic environment persist.

Question 9: Answer: C

— The PM's role is to facilitate informed decisions, not take sides. PMBOK 8: leaders demonstrate "transparency" and "integrity — willingness to share bad news early." Present facts, show options, let the authority decide. Siding with either (A, B) creates Win-Lose. Proposing compromise (D) without stakeholder input is premature.

Question 10: Answer: C

— PMBOK 8 emphasizes EI: "Self-awareness is the ability to conduct a realistic self-assessment — understanding our own emotions, goals, motivations, strengths, and weaknesses." The complaint may contain valid feedback. Confronting (A) confirms the "doesn't trust" perception. Ignoring (B) lets morale deteriorate. Public discussion (D) could embarrass the team member. Private, self-aware dialogue models the trust and openness being questioned.

11. Conclusion

Conflict management is not about "fighting fires" — it is about building an environment where disagreement becomes a driver of creativity. Three key takeaways:

1. - Analyze before acting — Identify the source (7 sources) + analyze context (5 factors) BEFORE choosing a technique. Picking the wrong technique due to a misread context will escalate the conflict instead of resolving it.

2. - Collaborate is the default, but not the only option — Win-Win is the ideal approach for long-term resolution. But when the situation is urgent (Force), when preserving the relationship matters (Smooth), or when a temporary fix is needed (Compromise) — the PM must be flexible. Knowing WHEN to use each technique is the most important skill.

3. - Prevention > Cure — Ground rules, a team charter, and clear role definitions from the outset will significantly reduce the number of conflicts that arise. And when violations occur — address them early, privately, and consistently. Do not wait until the "house is on fire" to act.

PMBOK® 8: "The success of project managers in managing their project teams often depends on their ability to resolve conflicts." — Conflict management is not a "nice to have" skill. It is a survival skill for every PM.

Frequently Asked Questions (FAQ)

What are the 5 conflict resolution techniques in PMP and when should each be used?

Collaborating/Confronting: find a win-win solution — use when the relationship is important and the issue is complex. Compromising: both parties give up something — use when a quick decision is needed. Smoothing/Accommodating: temporarily reduce tension — use when more time is needed. Forcing: exercise authority — use in a crisis. Withdrawing/Avoiding: retreat from the conflict — use least often, when the issue is not significant.

According to PMBOK 8, which technique should a PM prioritize when resolving conflict?

PMBOK 8 and most PMP exam questions prioritize Collaborating/Problem Solving — because it produces the best outcome and protects long-term relationships. However, there is no one-size-fits-all approach: the PM must assess urgency, importance of the relationship, and power dynamics to select the most appropriate technique.

How does productive conflict differ from destructive conflict?

Productive conflict: disagreement over ideas, approaches, or priorities — leads to better decisions when managed well. Destructive conflict: personal attacks, hidden agendas, or passive aggression — damages team trust and performance. The PM's role is to turn destructive conflict into productive conflict by focusing on interests, not positions.

You now have a solid grasp of project conflict management — it's time to practice with real exam questions.

• Next article: Leading the Project Team: 7 Leadership Competencies for PMs per PMBOK 8

• Project team management: from hiring to conflict resolution per PMP

• Building a shared project vision per PMBOK 8

Try Free PMP Practice Questions →

Official References:

• PMBOK® Guide Standards — PMI (pmi.org)