Managing Conflict
PMP PMP · People
Why conflict is on the exam
Conflict is one of the most heavily tested topics in the People domain, and the July 2026 ECO gives it its own task: manage conflicts. PMI's view is that conflict is normal, expected, and often useful. A team that never disagrees is either not thinking hard enough or not safe enough to speak up. The project manager's job is not to eliminate conflict but to manage it so that it stays productive — focused on ideas, tasks, and solutions rather than on people and personalities. Exam questions test whether you can tell the difference between healthy task conflict and harmful personal conflict, and whether you know which resolution approach fits the situation.
It helps to know where project conflict usually comes from. The most common sources are schedules, priorities, resources, technical opinions, administrative procedures, cost, and personalities — roughly in that order. Schedule conflict is the most frequent because schedules are where everyone's competing demands collide. Personality conflict is the least frequent but the hardest to resolve, because it is about people rather than about the work. When a question describes a conflict, the source often hints at the right response: a disagreement about a technical approach is solved with facts and analysis, while a clash of personalities needs a private conversation and empathy.
The five conflict resolution styles
PMI expects you to know five styles of handling conflict, and this is one of the few places on the exam where a model is tested almost by name. The styles differ in how much they serve your own interests versus the other party's interests:
| Style | Also called | When it fits |
|---|---|---|
| Collaborate / Problem-solve | Win-win | The default. Both parties work together to find a solution that fully satisfies everyone. Best when the issue matters and time allows. |
| Compromise / Reconcile | Lose-lose | Both parties give up something to reach a workable agreement. Useful when time is short or the parties are equally matched, but nobody gets everything they wanted. |
| Accommodate / Smooth | Yield-lose / Lose-win | You give way to the other party. Fits when the issue matters more to them than to you, or when preserving the relationship matters more than the point. |
| Force / Direct | Win-lose | You impose a decision. Only justified in emergencies, when safety is at stake, or when a decision must be made and there is no time to discuss it. |
| Withdraw / Avoid | Lose-lose | You step back from the conflict. Fits only when the issue is trivial, when tempers need time to cool, or when someone else is better placed to resolve it. |
The exam's strong preference is for collaborate/problem-solve. When a question asks for the best approach and collaboration is one of the options, it is usually the answer — unless the situation specifically rules it out, for example when there is no time, when safety requires an immediate decision, or when the conflict is so trivial that engaging with it would waste everyone's time. The trap options are usually force/direct (which sounds decisive but damages relationships) and withdraw/avoid (which sounds diplomatic but lets the problem fester). Compromise is the second-best option in many questions: it is acceptable when collaboration is not possible, but it is not the ideal, because both sides lose something.
How to handle a conflict step by step
Regardless of style, the process for managing a conflict follows the same PMI reasoning chain that runs through the whole People domain: understand first, then act. The steps are: identify the real source of the conflict (not just the surface argument), bring the parties together in a private, safe setting, let each side explain their position and their underlying interests, look for common ground, and work toward a solution that addresses the interests of both sides. Throughout, the project manager stays neutral, focuses the discussion on the issue rather than the people, and makes sure everyone is heard. If the parties cannot resolve it themselves, the project manager facilitates; only if facilitation fails does the project manager escalate, and even then the escalation is to a defined process, not to punishment.
A useful distinction in exam questions is between positions and interests. A position is what someone says they want ("we must use vendor A"). An interest is why they want it ("vendor A is the only one whose support team answers within an hour, and our users need that"). Conflicts that look unsolvable at the level of positions often dissolve at the level of interests, because there may be several ways to satisfy the underlying need. When a question describes two parties deadlocked over a position, the correct action is usually to dig into their interests — which is just the PMI "understand first" principle applied to conflict.
Conflict in agile and hybrid teams
In agile and hybrid environments, conflict is handled largely by the team itself. Retrospectives are the main forum: the team inspects how it worked together, names what caused friction, and agrees on changes for the next iteration. The project manager — or Scrum Master, in a Scrum team — facilitates rather than adjudicates, helping the team surface issues safely and reach its own agreements. The exam rewards this self-organizing approach: an option that has the team resolve its own conflict in a retrospective usually beats an option that has the project manager impose a solution.
One special case worth knowing is conflict between the team and an external party, such as a stakeholder who keeps changing requirements or a functional manager who keeps pulling team members onto other work. Here the project manager acts as a shield: they take the conversation outside the team, negotiate with the external party, and protect the team's focus. The team should not have to fight organizational battles; that is the project manager's job.
When conflict becomes a performance or conduct issue
Not every conflict is a healthy disagreement. Bullying, harassment, discrimination, and repeated disruptive behavior are conduct issues, not conflicts to be facilitated, and the exam treats them differently. The correct response is to address the behavior promptly and privately, document it, and involve human resources or the appropriate organizational process if it continues. The key distinction is that a conflict is a disagreement between parties who both have legitimate interests, while misconduct is behavior that violates organizational policy or basic respect. Exam questions sometimes blur the two deliberately — for example, a team member who "disagrees loudly" in every meeting might be expressing genuine concerns (facilitate) or might be bullying colleagues (address as conduct). Read the scenario carefully: look for words like "insults," "threatens," "excludes," or "repeatedly interrupts" that signal conduct rather than disagreement.
Exam mindset for conflict
For conflict questions, the decision tree is simple. First, ask whether the situation is a conduct issue — if so, address it directly and involve the proper process. If it is a genuine conflict, the default answer is collaborate/problem-solve: bring the parties together, understand interests, and find a win-win. Compromise is the answer when collaboration is impossible — usually because of time pressure or equally matched positions. Accommodate fits when the issue matters more to the other party. Force fits only in emergencies. Withdraw fits only for trivial issues or when tempers need to cool. And in every case, the first step is to understand the source of the conflict before choosing a response.
Exam traps to watch for
- Choosing compromise when collaboration is possible. Compromise is second-best — both sides lose something — while collaboration finds a solution that satisfies everyone.
- Choosing force/direct because it sounds decisive. Forcing a decision is only right in emergencies or when safety is at stake; everywhere else it damages trust.
- Choosing withdraw/avoid because it sounds diplomatic. Avoiding a real conflict lets it grow; withdrawal is only right for trivial issues or cooling-off periods.
- Treating a conduct problem (bullying, harassment) as a conflict to facilitate. Misconduct needs direct action and the proper organizational process, not mediation.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.Two senior engineers disagree strongly about the technical design of a key component. Each believes their approach is better, and the argument is delaying the project. What is the BEST approach for the project manager?
Explanation: This is a task conflict between two people with legitimate technical views, and the PMI-preferred style is collaborate/problem-solve: bring the parties together, evaluate both approaches against the actual requirements, and agree on the best solution. The reasoning chain is: understand both positions and their underlying interests, use facts (the requirements) as the judge, and reach a solution both can support. Option C is force/direct — it may be fast, but it damages trust and may pick the worse design. Option B is a false compromise that creates an incoherent design and doubles the work. Option A is withdraw/avoid — the decision is blocking the project, so delaying it makes the problem worse.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q2.A project manager learns that two team members had a heated argument yesterday and are now refusing to speak to each other. The argument was about a minor scheduling detail. What should the project manager do FIRST?
Explanation: The PMI reasoning chain is: understand first, then facilitate. A private conversation with each person reveals what really happened — the scheduling detail may be the surface issue, with a deeper frustration underneath — and then a facilitated joint conversation can resolve it. Option C is wrong because escalation is premature: the project manager should try to resolve it at their own level first, and HR is for conduct issues, not ordinary disagreements. Option A is wrong because separating the people avoids the conflict rather than resolving it, and it disrupts the work. Option B is wrong because refusing to speak to each other is already affecting the team; ignoring it lets the damage grow even if the original trigger was minor.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q3.During a project review, the project manager must decide between two options for resolving a disagreement with a vendor. There is no time for extended discussion because a contractual deadline is tomorrow. The vendor's position and the project's position are equally strong. Which conflict resolution style is MOST appropriate?
Explanation: This is the classic case where compromise is the right answer: collaboration is the ideal, but it needs time that the situation does not allow, and the parties are equally matched, so neither can simply win. Compromise — each side giving up something to reach a workable agreement before the deadline — is the best available outcome. Option B is wrong here not because collaboration is bad, but because the question explicitly removes the time it requires. Option D is wrong because the deadline is tomorrow; avoiding the conflict guarantees a missed deadline. Option A is wrong because forcing a decision on a vendor with an equally strong position damages the relationship and may breach the spirit of the contract.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q4.A team member repeatedly interrupts colleagues in meetings, dismisses their ideas with personal insults, and has caused two colleagues to ask to leave the project. What should the project manager do?
Explanation: This is a conduct issue, not a conflict to be facilitated: personal insults and behavior that drives people off the project violate basic respect and organizational norms. The correct response is to address the behavior directly and privately, document the conversation, and involve human resources or the proper process if the behavior continues. Option A is wrong because facilitating a group discussion about misconduct puts the victims on the spot and treats abuse as a difference of opinion. Option C is wrong because technical skill never excuses behavior that harms the team. Option D is wrong because waiting for a retrospective leaves the harmful behavior unaddressed for weeks while more damage is done.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q5.A product owner and a developer disagree about the priority of two features. The product owner insists feature A comes first; the developer believes feature B is more technically urgent. The project manager asks each of them why their feature matters most. What is the project manager doing?
Explanation: Asking why each feature matters moves the discussion from positions (what each person wants) to interests (why they want it). Once the interests are clear — for example, the product owner needs a demo for a customer next week, while the developer needs to fix a dependency before it blocks other work — a solution may emerge that satisfies both, such as a small slice of feature A for the demo plus the dependency fix. Option A is wrong because asking questions is the opposite of forcing; it is facilitation. Option D is wrong because understanding interests is an active step toward resolution, not avoidance. Option C is wrong because the project manager has not agreed with anyone; they are gathering information.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q6.A safety inspector flags a construction method the team is using as dangerous and demands it stop immediately. The team lead disagrees and wants to discuss alternatives first. What should the project manager do?
Explanation: Safety is the one situation where force/direct is the right style: when people may be harmed, the project manager must act immediately and without negotiation. The reasoning chain is: (1) safety overrides schedule, cost, and team preferences; (2) discussion can happen after the danger is removed, not before; (3) the project manager owns the decision. Option A is wrong because collaboration takes time the situation does not allow — people are at risk now. Option D is wrong because a dangerous method at half pace is still dangerous. Option B is wrong because the project manager cannot delegate a safety decision to the people who are arguing about it.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q7.In an agile project, the development team and the product owner disagree about how much work can be completed in the next sprint. What is the BEST way to resolve this?
Explanation: In agile ways of working, sprint planning is a collaborative event: the team brings its knowledge of capacity and the product owner brings priorities, and they agree the sprint scope together. This is collaboration/problem-solve applied to agile practice, and it respects the self-organizing nature of the team. Option D is wrong because a project manager imposing sprint scope removes the team's ownership and usually produces an unrealistic commitment. Option B is wrong because the product owner owns the backlog's order, not the team's capacity — they cannot commit the team to work the team cannot do. Option C is wrong because the team deciding alone ignores the product owner's priorities, which is half of the decision.
Exam objective: PMP ECO Task: Manage conflicts (People)
Q8.A project manager notices that disagreements in the team have increased since the project moved into its most complex phase. Team members argue about technical approaches in meetings but reach decisions and continue working well together afterward. How should the project manager interpret this?
Explanation: Disagreement about technical approaches that ends in decisions and good working relationships afterward is healthy task conflict — it means the team is thinking hard about difficult work and feels safe enough to disagree. The project manager's role is to facilitate it (keep discussions focused on the work, make sure everyone is heard) rather than suppress it. Option D is wrong because there is no dysfunction here: decisions are being reached and the team works well together. Option B is wrong because storming is a stage of team formation, not a label for every disagreement, and a team that resolves its disagreements is not going backwards. Option A is wrong because there is no misconduct — arguing about technical approaches is legitimate professional debate.
Exam objective: PMP ECO Task: Manage conflicts (People)