Task 1: Manage Conflict

Conflict is inevitable on projects. Stakeholders have competing interests, resources are finite, team members come from different backgrounds, and deadlines create pressure. The PMP Exam Content Outline (ECO) lists Manage Conflict as the very first task in the People domain — and for good reason. A project manager who cannot effectively navigate conflict will watch their project stall, their team fracture, and their stakeholder relationships deteriorate.

This study guide covers everything you need to know about ECO Task 1: the enablers that describe what PMI expects you to do, the five conflict resolution styles, the stages of conflict escalation, and — most importantly — how to answer conflict-related questions on the PMP exam.

ECO Enablers for Task 1

The PMP Exam Content Outline defines three enablers for managing conflict. Each describes a concrete action a project manager should take, and each maps directly to exam scenarios:

Interpret the source and stage of the conflict. Before you can resolve a conflict, you must understand where it comes from (personality clash, resource scarcity, scheduling pressure, technical disagreement, or communication breakdown) and how far it has escalated.
Analyze the context for the conflict. Context matters enormously. A disagreement between two senior architects during design is very different from a heated argument between a developer and a sponsor during a steering committee meeting. Evaluate the people involved, the project phase, the organizational culture, and what's at stake.
Evaluate, recommend, and reconcile the appropriate conflict resolution solution. This is where the PM applies the right technique for the situation. Not every conflict benefits from the same approach — the PMP exam will test your ability to match the resolution style to the scenario.

These enablers align closely with PMBOK 7's Leadership and Stakeholders principles, as well as the Team performance domain. The emphasis in PMBOK 7 is on collaborative, servant-leadership approaches rather than authoritarian conflict suppression.

The Five Conflict Resolution Styles

This is the most heavily tested concept within Task 1. PMI draws from the Thomas-Kilmann Conflict Mode Instrument, which identifies five distinct approaches. Every PMP candidate must know these cold — not just their definitions, but when each is appropriate and what PMI considers the "best" answer in different scenarios.

Style	Description	When to Use	PMI's View
Collaborating (Win-Win)	Both parties work together to find a solution that fully satisfies everyone's concerns. Involves open dialogue, shared problem-solving, and creative alternatives.	When the relationship is important, time is available, and both sides are willing to engage. Ideal for complex technical disagreements and long-term partnerships.	Highly favored. PMI considers this the ideal approach whenever feasible. It builds trust, strengthens the team, and produces the best long-term outcomes.
Compromising (Give-and-Take)	Both parties give up something to reach a middle-ground solution. Neither side gets everything they want, but both get enough to move forward.	When time is limited, the stakes are moderate, and the parties have equal power. Useful for temporary fixes or when collaboration stalls.	Acceptable fallback. PMI views compromising as practical but not ideal. It's a "lose-lose" relative to collaborating — neither party is fully satisfied.
Forcing (Win-Lose)	One party imposes their solution on the other. Power, authority, or positional leverage drives the outcome rather than mutual agreement.	In emergencies requiring immediate action, when an unpopular decision must be enforced (safety, compliance), or when the relationship doesn't matter.	Last resort. PMI almost never favors forcing. It damages relationships and suppresses valuable input. Only acceptable in true emergencies.
Smoothing (Accommodating)	Emphasizes areas of agreement while downplaying differences. The goal is to preserve harmony and the relationship, even at the expense of the substantive issue.	When the issue is trivial compared to the relationship, when you need to buy time, or when you recognize you're wrong and the other party's position is stronger.	Temporary only. PMI accepts smoothing as a short-term tactic, but the underlying issue remains unresolved and will resurface.
Avoiding (Withdrawal)	One or both parties retreat from the conflict entirely — postponing, sidestepping, or ignoring the issue altogether.	When the issue is trivial, when emotions are too high for productive discussion, when others can resolve it better, or when the cost of engagement exceeds the benefit.	Rarely correct. PMI generally considers avoiding as the worst option. It lets problems fester. Only correct in very limited circumstances.

📝 PMP Exam Tip: The "PMI Answer" for Conflict

On the exam, the correct answer for conflict resolution questions almost always involves face-to-face, private discussion between the conflicting parties. PMI wants the project manager to:

Address the conflict directly (don't ignore it)
Meet with the parties individually first, then together if needed
Focus on the problem, not the personalities
Seek a collaborative (win-win) solution as the first option
Escalate only after direct resolution attempts have failed

If you see an answer choice that says "meet privately with each team member to understand their perspective," that's almost certainly the right answer.

Sources and Stages of Conflict

Understanding why conflict arises and how far it has progressed is the first enabler. PMI identifies seven primary sources of project conflict, originally from the Thamhain and Wilemon research:

Seven Sources of Conflict on Projects

Schedules — Disagreements about timing, deadlines, sequencing, and whether milestones are realistic.
Project priorities — Competing views on which tasks, features, or deliverables matter most.
Resources (human and material) — Contention over who gets which people, equipment, or budget allocation.
Technical opinions — Disagreements about the best technical approach, architecture, tooling, or methodology.
Administrative procedures — Conflicts over process, reporting structures, approval workflows, and governance.
Cost and budget — Disputes about estimates, spending, contingency usage, and who covers overruns.
Personality clashes — Interpersonal friction, communication style differences, and ego conflicts.

On the exam, the most common conflict sources tested are schedules and resources — these are statistically the most frequent project conflicts in practice. But don't ignore personality clashes; PMI often pairs them with emotional intelligence scenarios.

Stages of Conflict Escalation

Conflict doesn't appear fully formed. It escalates through recognizable stages, and the project manager's approach should change depending on the stage:

Stage 1: Discomfort — Something feels off. Body language changes, communication becomes slightly guarded. Best addressed early with a private, informal conversation.
Stage 2: Incident — A minor event triggers visible frustration. A sharp email, a sarcastic remark. Address quickly before it hardens into resentment.
Stage 3: Misunderstanding — The parties begin interpreting each other's actions negatively. Assumptions replace facts. Facilitate a structured conversation to clarify intent.
Stage 4: Tension — The relationship is strained. Communication breaks down. The conflict is now affecting work. Formal mediation may be necessary.
Stage 5: Crisis — Open hostility. The team is divided. Work stops or suffers severely. Intervention is mandatory — this may require escalation to a sponsor or HR.

PMI's message is clear: intervene early. A discomfort-stage conflict that could be resolved with a 10-minute conversation becomes a crisis that threatens the entire project if ignored.

Conflict Resolution in Predictive vs. Agile Environments

Aspect	Predictive (Waterfall)	Agile
PM's Role	Direct mediator; formally resolves disputes through authority or escalation to sponsor	Servant leader; facilitates team self-resolution; removes impediments rather than imposing solutions
Conflict Visibility	Often surfaces during formal reviews, status meetings, or when milestones are missed	Surfaces naturally during daily standups, retrospectives, and sprint reviews — conflicts are harder to hide
Preferred Approach	Collaborating or compromising, documented in an issue log with formal resolution tracking	Team self-organization; the Scrum Master or Agile PM facilitates conversation but lets the team own the solution
Escalation Path	PM → Functional Manager → Sponsor → Steering Committee	Team attempts resolution → Scrum Master facilitates → Product Owner if scope/priority conflict → Escalate only as last resort

How Conflict Questions Appear on the PMP Exam

PMP exam questions about conflict are almost always situational. You'll be given a scenario and asked what the project manager should do. Here are the patterns to recognize:

Pattern 1: "Two team members are arguing about..."

The correct answer nearly always involves the PM facilitating a private conversation between the two individuals. Look for answer choices that mention meeting with each person individually, then bringing them together. Avoid choices that involve: public confrontation, immediately escalating to a manager, ignoring the issue, or imposing a solution without hearing both sides.

Pattern 2: "A stakeholder disagrees with another stakeholder about..."

Stakeholder-to-stakeholder conflict requires the PM to analyze the conflict's source, understand each stakeholder's interests, and facilitate a resolution that serves the project's objectives. The correct answer will reference analyzing the source of the conflict, reviewing the stakeholder engagement plan, and seeking common ground.

Pattern 3: "The project is in crisis because..."

If the conflict has already reached crisis stage, direct intervention is required. But PMI still wants you to address the root cause, not just the symptoms. Look for answers that combine immediate de-escalation with a plan to address the underlying issue.

⚠️ Common Wrong Answer Trap: "Escalate to the Sponsor"

The PMP exam frequently includes "escalate to the project sponsor" as an answer choice for conflict questions. This is almost never the correct answer. PMI expects the project manager to own conflict resolution. Escalation should only happen after you have exhausted all direct resolution attempts, documented your efforts, and determined that the conflict is beyond your authority to resolve. If you see an answer that begins with the PM taking direct action (meeting, facilitating, analyzing), choose that over escalation.

Key Principles from PMBOK 7

The PMBOK 7 Guide's principle of Stewardship requires project managers to act with integrity and care when managing team dynamics. The Leadership principle emphasizes adapting your conflict approach to the situation — there is no single "right" style. The Team performance domain explicitly addresses the need for a healthy, collaborative team environment, which can only exist when conflicts are resolved constructively.

Additionally, PMBOK 7's Tailoring principle reminds us that conflict management approaches should be tailored to the organizational culture, the people involved, and the project context. What works in a startup with a flat hierarchy may not work in a government agency with strict protocols.

Study Checklist for Task 1

✅ Can you name all five conflict resolution styles and describe when each is appropriate?
✅ Do you know which style PMI considers ideal (collaborating) and which is least favored (avoiding)?
✅ Can you identify the seven sources of project conflict?
✅ Do you understand the five stages of conflict escalation and the appropriate response at each stage?
✅ Can you distinguish how conflict management differs between predictive and agile environments?
✅ Are you able to recognize the "PMI answer pattern" for conflict scenarios — private, face-to-face, collaborative resolution?

Task 1 sets the tone for the entire People domain. Master it, and you'll have a framework that applies to nearly every interpersonal question on the exam. Continue to Task 2: Lead a Team to build on these people-management fundamentals.

← Back to ECO Study Guide Index | Practice People Domain Questions →