I.2 — Manage Conflicts

I.2 · Last updated: 11/10/2026

Ground rules now belong to the conflict task

I.2 — Manage Conflicts is the second task in the People domain of the 2026 ECO, a domain that carries 33% of the exam. What sets it apart from its 2021 version is a topic it has absorbed, the team's ground rules. In older material they stood as a task of their own, and in 2026 they were moved inside this one as a tool for managing conflict.

The ECO lists six enablers for the task, and the last two show that change:

• 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 old I.1 is today's I.2

Domain I shrank to eight tasks in 2026, while the numbering in older material ran to at least I.12. Conflict management slid one place in the process, so the topic that was I.1 in 2021 is now I.2. The old I.2, for its part, was "lead a team", and that topic now lives under I.3 — Lead the Project Team.

In practice this means that if you are hunting for conflict questions in older material, you should look under I.1. Do not generalize that one-step shift to the rest of the domain, though. I.3 alone took over at least five separate 2021 numbers, and no regular pattern of shifting emerged. For the overall picture of the numbering trap, see what changed in the 2026 PMP exam.

The book does not treat conflict as a malfunction

The Guide opens the subject by accepting it: conflict is inevitable in a project environment (PMBOK® 8, Guide p.156). The sentence that follows is the one that decides exam answers. Successful conflict management results in greater productivity and positive working relationships, and when differences of opinion are managed properly they can lead to increased creativity and better decision-making (PMBOK® 8, Guide p.156).

So the book sees conflict as a situation that produces value when it is handled well, and nothing in the passage suggests it should be stamped out. That is why options such as "prevent the conflict" or "keep the parties apart" are usually eliminated on the exam. The behavior the exam expects is management of the conflict, and making it disappear is a different goal.

Three sources, two of them structural

The first enabler asks you to identify sources, and the book names three of them: scarce resources, scheduling priorities, and personal work styles (PMBOK® 8, Guide p.156).

What stands out is that two of the three are structural. Scarcity of resources and schedule pressure both come from the project's constraints, which means the system itself is often behind a conflict more than any clash of personalities.

The same paragraph points to 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). This is the reason the ECO moved its two ground-rule enablers into this task. Ground rules work as a mechanism that lowers conflict before it starts, and they lose most of their value if they only come out of the drawer after a fight has broken out.

The Standard reaches the same point from the side of culture. It says an empowered project culture needs full clarity on individual roles, responsibilities, team agreements, and guiding processes (PMBOK® 8, Standard p.53). A team where nobody is sure who does what has already laid the ground for conflict.

Five techniques, each with its place

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

• Withdraw/avoid. Retreating from an actual or potential conflict, or postponing the issue so as to be better prepared or to let others resolve it.
• Smooth/accommodate. Emphasizing areas of agreement over areas of difference, and conceding one's own position to the needs of others to keep harmony and the relationship.
• Compromise/reconcile. Looking for a solution that brings some degree of satisfaction to everyone so the conflict is settled temporarily or partially. This occasionally ends in lose-lose.
• Force/direct. Pushing one's own viewpoint at the expense of others and offering only win-lose solutions, usually backed by a position of power to resolve an emergency. The outcome is often win-lose.
• Collaborate/problem-solve. Bringing together views and insights from different perspectives. It needs a cooperative attitude and open dialogue, typically leads to consensus and commitment, and makes a win-win outcome possible.

On the exam the right answer is usually collaborate/problem-solve. Even so, the book's remark that every technique has its place deserves to be taken seriously. Forcing can be entirely appropriate in an urgent safety decision, and so can withdrawing from a trivial detail.

Context picks the technique

The ECO asks you to implement an agreed-on resolution strategy and, in a separate enabler, to analyze the context. The factors the book lists tie the two together. Among the main factors that influence the choice of method are these (PMBOK® 8, Guide p.157):

• The importance and intensity of the conflict
• The time pressure for resolving it
• The relative power of the people involved
• The importance of maintaining a good relationship
• The motivation to resolve the conflict on a long-term or short-term basis

Two of the five concern the relationship, one concerns power, and one concerns time. Details buried in an exam scenario, such as who reports to whom or how close the deadline is, usually point to one of these factors, and that factor is what decides the right technique.

The team first, then the project manager, formal procedure last

The passage with the most direct link to the exam describes who handles a conflict and in what order (PMBOK® 8, Guide p.156):

1. When differences become a negative factor, project team members are initially responsible for resolving them.
2. If the conflict escalates, the project manager should help facilitate a satisfactory resolution.
3. If disruptive conflict continues, formal procedures may be used, including disciplinary actions.

One principle applies to every step. Conflict should be addressed early, usually in private, and with a direct, collaborative approach.

The order translates cleanly into exam terms. The project manager's first move is to leave the team room to solve the problem itself, and stepping in comes later. When the project manager does have to step in, the role is to facilitate, which is a different thing from acting as referee. Formal procedure sits at the end as a last resort. The book also links the topic to the project manager's own success, since how well project managers manage their teams often depends on their ability to resolve conflicts (PMBOK® 8, Guide p.156).

Why the project form breeds conflict

There is also a structural reason why this task sits so near the front of the People domain. The Standard says projects create a unique need for effective leadership. In regular business operations roles and responsibilities are usually established and consistent, while a project may bring together several organizations, departments, functions, or vendors that do not interact on a regular basis. Because projects can carry higher stakes and expectations than routine operations, a wider range of managers, executives, and stakeholders try to influence them, and according to the book this diversity of influence often creates higher degrees of confusion and conflict (PMBOK® 8, Standard p.46).

Seen this way, conflict on a project is a natural consequence of the project form far more often than it is a defect in the team. The book also names the means of coping with it. Emotional intelligence is what lets the project manager navigate conflicts and stress (PMBOK® 8, Standard p.47). The same skill is expected on the stakeholder side, where negotiation and conflict management appear among the key skills to develop in the Stakeholders performance domain (PMBOK® 8, Guide p.67). For the link to stakeholder engagement, see I.4 — Engage Stakeholders.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ 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 describes the book; it does not replace it.