I.2 — Manage Conflicts

I.2 · Last updated: 24/08/2026

Where this task sits

I.2 — Manage Conflicts is the second task in the People domain of the 2026 ECO. The domain carries 33% of the exam.

It has six enablers:

• Identify conflict sources
• Analyze the context for the conflict
• Implement an agreed-on resolution strategy
• Communicate conflict management principles with the team and external stakeholders
• Establish an environment that fosters adherence to common ground rules
• Manage and rectify ground rule violations

The last two are worth noting: in 2026, ground rules live inside the conflict task. In older material they were a task of their own. The ECO now positions ground rules as the remedy for conflict rather than as independent work.

🔴 Do not trust the number

Domain I came down to eight tasks in 2026; in older material the numbers ran at least as far as I.12. For this task the result is:

• In 2021, I.1 was manage conflicts. In 2026 that topic is I.2.
• In 2026, I.2 is manage conflicts. That number's 2021 counterpart was "lead a team," and that topic is now I.3.

So the subject shifted by one: you have to look at the old I.1, not the old I.2. Across the rest of the domain the shift is not uniform — I.3 absorbed six separate 2021 tasks at once.

Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

Conflict is inevitable — and not always harmful

The Guide opens the subject with a concession: conflict is inevitable in a project environment (PMBOK® 8, Guide p.156).

Then comes the sentence that decides exam answers: 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 (PMBOK® 8, Guide p.156).

Conflict, in other words, is not a fault to suppress but a condition that produces value when managed. That is why options saying "prevent the conflict" or "separate the parties" are usually wrong — what is asked for is management, not elimination.

Conflict sources, and what reduces them

The ECO's first enabler says "identify sources." The book names three: scarce resources, scheduling priorities, and personal work styles (PMBOK® 8, Guide p.156).

All three are strikingly structural: two of them are resources and schedule, that is, project constraints. The source of conflict is usually the system rather than the personality.

The same sentence supplies the remedy: team ground rules, group norms, and solid project management practices such as communication planning and role definition can reduce the amount of conflict (PMBOK® 8, Guide p.156).

That is exactly why the ECO's two ground-rule enablers sit in this task: ground rules are not a document you consult after conflict appears but a mechanism that reduces it in advance.

The Standard reaches the same place from the culture side: for an empowered project culture there should be full clarity on individual roles, responsibilities, team agreements, and guiding processes (PMBOK® 8, Standard p.53).

The five resolution techniques

The Guide gives five general techniques for resolving conflict and explicitly notes that each technique has its place and use (PMBOK® 8, Guide p.157):

• Withdraw/avoid — retreating from an actual or potential conflict situation; postponing the issue to be better prepared or to be resolved by others.
• Smooth/accommodate — emphasizing areas of agreement rather than areas of difference; conceding one's position to the needs of others to maintain harmony and relationships.
• Compromise/reconcile — searching for solutions that bring some degree of satisfaction to all parties in order to temporarily or partially resolve the conflict. This approach occasionally results in a lose-lose situation.
• Force/direct — pushing one's viewpoint at the expense of others; offering only win-lose solutions, usually enforced through a power position to resolve an emergency. This often results in win-lose.
• Collaborate/problem-solve — incorporating multiple viewpoints and insights from differing perspectives; requires a cooperative attitude and open dialogue that typically leads to consensus and commitment. This approach can result in win-win.

On the exam, collaborate/problem-solve is usually the right answer — but the book's caveat that each technique has its place matters: forcing may be right in an urgent safety decision, and withdrawing may be right on a trivial detail.

What determines the technique

The ECO says implement an "agreed-on" resolution strategy and makes "analyze the context" a separate enabler. The book's context list feeds exactly those two.

Factors that influence conflict resolution methods (PMBOK® 8, Guide p.157):

• Importance and intensity of the conflict,
• Time pressure for resolving it,
• Relative power of the people involved,
• Importance of maintaining a good relationship, and
• Motivation to resolve it on a long-term or short-term basis.

Two of the five look at relationship, one at power, one at time. In exam scenarios, the details embedded in the situation — who reports to whom, how close the deadline is — usually point at one of these.

The escalation ladder

This is the passage with the most direct exam counterpart — a four-step sequence (PMBOK® 8, Guide p.156):

1. If the differences become a negative factor, project team members are initially responsible for their resolution.
2. If conflict escalates, the project manager should help facilitate a satisfactory resolution.
3. Conflict should be addressed early and usually in private, using a direct, collaborative approach.
4. If disruptive conflict continues, formal procedures may be used, including disciplinary actions.

The order pays off directly: the project manager's first move is not to intervene but to leave room for the team to resolve it. When intervention is needed, the role is facilitator, not judge. And formal procedure is the last step, not the first.

The book ties off the consequence: the success of project managers in managing their teams often depends on their ability to resolve conflicts (PMBOK® 8, Guide p.156).

Why projects generate more conflict

Finally, a structural explanation for why this task sits second in the People domain.

The Standard says projects create a unique need for effective leadership: unlike general business operations, where roles and responsibilities are often established and consistent, projects may involve multiple organizations, departments, functions, or vendors that do not interact on a regular basis. Moreover, projects may carry higher stakes and expectations than regular operational functions. As a result, a broader array of managers, executives, senior contributors, and other stakeholders may attempt to influence a project. This diversity of influence often creates higher degrees of confusion and conflict (PMBOK® 8, Standard p.46).

Conflict on projects, then, is not a team defect but a natural consequence of the project form.

The book supplies a tool as well: emotional intelligence enables the project manager to navigate conflicts and stress (PMBOK® 8, Standard p.47). The same skill is asked for on the stakeholder side — among the key skills to develop in that performance domain are negotiation and conflict management (PMBOK® 8, Guide p.67).

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p.X
• A Guide to the Project Management Body of Knowledge — cited as Guide p.X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page explains the book; it does not replace it.