PMP Conflict Management: Techniques and When Each One Fits

What People Task 2 asks of you on the 2026 PMP

"Manage conflicts" is Task 2 of the People domain, which carries 33% of the exam under the 2026 Exam Content Outline (revised August 11, 2026). Read as a whole, the task asks you to understand a conflict before you respond to it, to settle it in a way the people involved can accept, and to keep the team's ground rules working so fewer conflicts start in the first place. It also expects people inside and outside the team to know how disagreements are handled on your project.

Conflict also shows up outside Task 2: competing stakeholder expectations, vendor negotiations, and two managers wanting the same person at the same time. The approaches below apply to all of them.

Five conflict approaches compared for PMP scenarios

A widely taught model of conflict behavior, developed by Kenneth Thomas and Ralph Kilmann, places five modes on two dimensions. Assertiveness is how far you pursue your own concerns. Cooperativeness is how far you try to satisfy the other person's. PMP prep courses often use older paired labels for the same five, shown in brackets.

The model's authors say each of us can use all five modes, and they do not name one mode that suits every situation. That matters for the exam, because People is a third of it and conflict shows up across its tasks. Full PMP prep on Passy is not on sale yet; its page shows the planned size of the People-domain bank in full PMP prep.

Why the PMP has no official conflict ranking, and how scenarios still point to an answer

PMI's outline names no preferred conflict technique, and no ranking appears in the PMI documents checked for this guide. Lists claiming that PMI always prefers one mode in a fixed order are study shortcuts, not PMI rules.

Scenarios still have defensible answers, because the stem gives you clues. Work through these questions in order:

1. Is safety, the law, or a compliance obligation at stake? Then the requirement wins now. You are enforcing the obligation, not your personal preference.
2. Is this a self-managing team's own issue? The Scrum Guide describes Scrum Teams as self-managing, deciding internally "who does what, when, and how." Help the team use its working agreements before you step in with a decision.
3. Do the people involved have the time and information to solve it together? Then collaborate, and bring data to the conversation.
4. Is a temporary settlement needed fast, with both sides holding real positions? Compromise, and set a date to revisit it.
5. Are emotions too high to talk? Pause and set a time to come back. Avoiding works as a step, not as the resolution.
6. Does the issue matter much more to them than to you? Accommodate, and save your influence for issues that matter.

Escalation is not one of the five modes. It is what your governance rules call for when the parties cannot resolve something within their authority. The Business Environment domain guide covers escalation paths and thresholds.

Six PMP conflict situations worked through

All people, companies, and projects below are invented.

1. Two engineers, two designs (predictive). On a hospital wing renovation, the lead structural engineer and the lead mechanical engineer disagree about routing ductwork through a load-bearing area. The design freeze is three weeks away.

• Strongest choice: collaborate. Bring both to a working session with the drawings, cost estimates, and code requirements, and agree on decision criteria before discussing options.
• Why not force: the project manager is not the technical authority, and imposing an answer loses one expert's commitment.
• Why not compromise: splitting the difference in a structural design can produce something worse than either option.

2. One database administrator, two managers (matrix organization). Two functional managers each schedule the same database administrator for the same two weeks in March.

• Strongest choice: collaborate first, with the schedule data in front of both managers. Options include resequencing one piece of work, splitting the time, or bringing in temporary help.
• Where compromise fits: if both deadlines truly carry equal weight, an agreed split may be the practical answer.
• When to escalate: if the managers cannot agree, take it to the sponsor or resource owner your governance names, with the options laid out.

3. A skipped safety step (forcing is right). On a utility upgrade, a subcontractor crew wants to skip a lockout step to recover a day. The site safety coordinator objects.

• Strongest choice: competing, on the safety rule. The step stays. Deal with the lost day separately, through schedule recovery.
• Why not compromise: a partial safety procedure is not a middle ground worth offering.

4. A meeting that boils over (avoiding as a first step). A vendor review turns into a shouting match between your quality lead and the vendor's account manager.

• Strongest choice: stop the discussion, set a time to reconvene the next morning, and ask both sides to bring the inspection data. Then collaborate.
• Why this is not avoidance as a habit: the pause has a time limit and a plan behind it.

5. A report template (accommodating). A team member feels strongly about the format of the weekly status summary. You do not mind either way.

• Strongest choice: accommodate. Use their format, and keep your influence for the decisions that affect delivery.

6. A sprint-length disagreement (agile team). Two developers argue in every planning session about moving from two-week to one-week sprints.

• Strongest choice: the team decides. Suggest taking it to the next retrospective, where the team inspects how it works, and offer to facilitate. Avoid deciding for a self-managing team.
• Why not smooth it over: "let's all get along" leaves a recurring disagreement unresolved.

To check whether you would choose the same way under exam pressure, start with the 20 free PMP practice questions. The first is a conflict between two developers on an agile team, and every answer comes with an explanation. For more volume later, the PMP page describes People-domain scenarios planned for full prep, each with a written explanation.

Ground rules and violations on a PMP team

Ground rules, often called working agreements, are the team's own commitments about how it works together: meeting habits, response times, how decisions get made, and how disagreements get raised. They hold up better when the team writes them, usually as part of a team charter. The PMP team leadership guide covers building one.

When a ground rule is broken, a sequence like this keeps the response proportionate:

1. Talk to the person privately and early. Small violations grow when nobody mentions them.
2. Point to the agreement, not to your opinion. The team made the rule, and you are holding everyone to it.
3. Listen for a cause. A rule that someone keeps breaking may not fit the team anymore.
4. Take a broken rule back to the team. If the rule itself is the problem, the team revises it, for example in a retrospective.
5. Use formal channels for repeated or serious conduct. Harassment, safety, and ethics issues go to the organization's process right away, not to a team discussion.

Here is an example. A distributed team agreed that everyone joins a 9:30 a.m. daily check-in. One developer, who recently moved two time zones west, keeps missing it. A private conversation reveals that the meeting now falls at 7:30 a.m. for him. The team moves the check-in later. The rule was the problem, not the person. The Agile Manifesto puts "individuals and interactions over processes and tools," and fixing the agreement instead of punishing the developer follows that value.

Explaining these principles early helps too. At kickoff, tell the team and outside stakeholders, including vendors, how disagreements get raised, who decides what, and when issues go up the governance chain. People who know the route are less likely to go around it.

After working through the six situations and the ground-rule example, note which approach you reached for first and whether the stem supported it. Once full prep opens, it is planned to save the conflict questions you miss so you can try them again. For the rest of the domain, the PMP People domain guide maps all eight tasks, and the guide to PMP scenario questions shows how to read the stem before choosing.