People — Conflict Management & Leadership
The People domain accounts for 33% of the exam (2026 ECO). This module establishes the posture the PMI expects: a project manager who acts as a servant leader, addresses conflict early, directly and privately, and consistently favors collaboration to solve problems rather than forcing, avoiding, or escalating prematurely.
Estimated time : 50 min
Learning objectives
- Distinguish leadership from management per the PMI and adopt the servant-leader posture.
- Identify the 5 levels of conflict escalation (Speed Leas model) to calibrate your response.
- Master the 5 conflict-resolution modes (Thomas-Kilmann) and know which one the PMI favors.
- Apply the PMI reflex: address conflict early, privately, directly, focused on the problem and the present.
- Leverage emotional intelligence (Goleman model) to prevent and defuse tension.
Key concepts
- Servant Leadership
- A posture where the project manager serves the team first: removing impediments, shielding the team from distractions, facilitating and growing people rather than commanding. It is the default posture expected on the exam, especially in agile.
- PMBOK 8 (Resources) ; Agile Practice Guide §4.2
- Conflict
- An inevitable and natural divergence in any project. Well managed it is constructive; poorly managed it becomes destructive. The PM does not seek to eliminate it but to channel it.
- PMBOK 8 ; Performance domain « Resources »
- Thomas-Kilmann modes (TKI)
- Five ways to handle conflict along two axes (assertiveness × cooperation): Avoid, Accommodate, Compromise, Force, Collaborate. Collaborate is the only durable win-win mode.
- PMBOK 8 — Models, Methods & Artifacts (Conflict)
- Escalation levels (Speed Leas)
- Five levels of rising intensity: (1) Problem to solve, (2) Disagreement, (3) Contest, (4) Crusade, (5) World war. The higher the conflict climbs, the earlier and firmer the intervention must be.
- PMBOK 8 — Models, Methods & Artifacts
- Emotional intelligence (EI)
- The ability to recognize and manage one's own emotions and those of others. Four components (Goleman): self-awareness, self-management, social awareness (empathy), relationship management.
- PMBOK 8 ; ECO People
- Ground rules
- Explicit agreements set WITH the team on expected behaviors (communication, decisions, disagreements). They prevent many conflicts and serve as a reference when conflict erupts.
- ECO People ; PMBOK 8
1. Why People is 33%: the PMI posture
A project is, above all, a human endeavor
The PMP exam does not assess your ability to recite processes, but your ability to make the right decision when dealing with people. Under the 2026 ECO, the People domain weighs 33% (down from 42%): it remains major and tests your leadership behavior, how you handle tension, and your ability to grow a team.
PMBOK 8 keeps the principles orientation while reintroducing processes/ITTOs. Of its 6 principles (PMBOK 7 had 12), two frame this module directly.
- People · 33%
- Process · 41%
- Business Environment · 26%
PMP exam weighting by domain (ECO).
PMBOK 8 principles directly engaged by this module
| Principle | What it means for the PM |
|---|---|
| Build an empowered culture | Establish shared ground rules, psychological safety, self-organization, and resolve conflict constructively. |
| Be an accountable leader | Adopt servant leadership: serve, motivate, remove obstacles, rather than command and control. |
The fundamental PMI reflex
Faced with a human problem, the project manager ACTS personally and FIRST with the people involved. They do not flee, do not impose a unilateral decision, and do not escalate to the sponsor or HR before attempting a direct, collaborative resolution.
Artifact → decision → PMI action map
Artifact
ECO + PMBOK 8 + study plan
Decision
Which ECO competency does this chapter strengthen?
PMI action
Connect concept, scenario, counterexample, and explained question.
Avoid: Memorizing without linking the concept to a project decision.
Recommendations
- Read every People question looking for the PM's proactive action: it is almost always the right lead.
- Tie each situation to a PMBOK 8 principle: "collaborative" and "leadership" dominate this domain.
Tips
- Memory hook: People = Proactive. The PM never just reacts, they act.
Chapter quiz
1.What is the weighting of the People domain on the PMP exam?
2.Faced with a people problem, what is the default PMI posture?
3.Which PMBOK 8 principle underpins building a healthy team climate?
2. Leadership per the PMI & the servant leader
Leadership ≠ Management
The PMI clearly separates the two. Management deals with systems and processes (plan, organize, control); leadership deals with people (set direction, inspire, influence). A great PM does both, but the exam rewards the leadership dimension.
Management vs Leadership (PMBOK 8)
| Management | Leadership |
|---|---|
| Uses positional authority | Uses relationships and influence |
| Maintains / administers | Develops / innovates |
| Focuses on systems & control | Focuses on people & trust |
| Asks "how and when?" | Asks "what and why?" |
Servant leadership: the default posture
The servant leader inverts the pyramid: they put themselves at the team's service. Their first question is not "what should the team do for me?" but "what does the team need to succeed, and how can I provide it?".
- Remove the impediments blocking the team.
- Shield the team from external distractions and interruptions.
- Facilitate rather than decide for the team.
- Coach and develop people (help them grow).
- Encourage self-organization and empowerment.
Leadership styles to know
Directive, transactional (reward/punish), transformational (inspires and elevates), servant (serves the team), charismatic, laissez-faire (hands-off). When in doubt, and especially in agile, the answer leans toward servant leadership.
Emotional intelligence (EI)
EI is the #1 conflict-prevention tool. A PM who senses a member's rising frustration can step in before it erupts.
The 4 components of EI (Goleman)
| Component | Definition |
|---|---|
| Self-awareness | Recognizing your own emotions as they arise. |
| Self-management | Regulating your reactions, staying calm under pressure. |
| Social awareness (empathy) | Perceiving and understanding others' emotions. |
| Relationship management | Using that understanding to influence, defuse, and collaborate. |
Self-awareness
Recognize your own emotions.
Social awareness (empathy)
Perceive others' emotions.
Self-management
Regulate your reactions under pressure.
Relationship management
Influence, defuse, collaborate.
The 4 components of emotional intelligence (Goleman).
Artifact → decision → PMI action map
Artifact
Team charter / RACI / conflict log
Decision
Who must decide, contribute, or be realigned?
PMI action
Facilitate, clarify roles, document agreement, and monitor behavior.
Avoid: Forcing or escalating before seeking the root cause.
Recommendations
- If one answer offers to "command/control" and another to "facilitate/coach", favor the latter.
- Map each leader behavior to an EI component: it clarifies questions about emotions.
Tips
- EI mnemonic: "Self then Others" — self-awareness → self-management → empathy → relationships.
- Servant leader = "I serve, I remove obstacles". Never "I decide for you".
Chapter quiz
1.Which statement best describes leadership (vs management) per the PMI?
2.An agile coach spends most of their time removing impediments and shielding the team. Which style do they embody?
3.Staying calm and regulating your reactions under pressure is which EI component?
3. Conflict management
Conflict is natural — and sometimes useful
The PMI views conflict as inevitable and even healthy when it is about ideas: it improves decisions and drives innovation. The danger is not conflict itself but its unmanaged escalation into the personal and emotional.
Main sources of conflict in projects
- Schedules (planning priorities) — the #1 most frequent source.
- Project priorities.
- Resources (human and material).
- Technical opinions.
- Administrative procedures, cost, and — last — personalities.
Remember
Counter-intuitively, personality clashes are the LEAST frequent source of project conflict. Most conflicts are structural (schedule, priorities, resources) — and therefore addressable by the PM.
The 5 escalation levels (Speed Leas)
Diagnosing the level lets you calibrate the response: level 1-2 is resolved by facilitation; level 4-5 may require firmer intervention, even mediation.
Conflict escalation scale
| Level | Name | Characteristic |
|---|---|---|
| 1 | Problem to solve | Differing views, cooperative tone. |
| 2 | Disagreement | People protect themselves, keep their distance. |
| 3 | Contest | People want to win; language turns personal. |
| 4 | Crusade | People want the other gone; us-vs-them logic. |
| 5 | World war | Destroying the other becomes the goal; intractable. |
World war
Destroying the other becomes the goal; intractable.
Crusade
People want the other gone; us-vs-them.
Contest
People want to win; language turns personal.
Disagreement
People protect themselves, keep their distance.
Problem to solve
Differing views, cooperative tone.
The 5 conflict escalation levels (Speed Leas).
The 5 resolution modes (Thomas-Kilmann)
TKI modes — least to most constructive
| Mode | Description | Outcome |
|---|---|---|
| Withdraw / Avoid | Postpone, flee, ignore the problem. | Lose-lose: the conflict returns. |
| Smooth / Accommodate | Emphasize agreement, yield to preserve harmony. | Temporary; the root remains. |
| Compromise / Reconcile | Each side gives up part for a partial deal. | Give-and-take: no one fully satisfied. |
| Force / Direct | Impose one's view via power. | Win-lose: fast but breeds resentment. |
| Collaborate / Problem-Solve | Integrate views to satisfy everyone. | Win-win: the only durable solution. |
Thomas-Kilmann grid (hover each mode).
The mode the PMI favors
Collaborate / Problem-Solve is the reference answer: it is the only mode that addresses the root cause and yields a durable win-win. The others are acceptable only in specific cases (Force if safety is at stake; Avoid if emotions are too high to talk right now).
Worked example: Collaborate rather than Compromise
Two analysts fight over a single shared test environment: each needs it all day to hit a deadline. The temptation is to split it down the middle (compromise): half a day each. But neither can finish a full test run in half a day — each loses, and the conflict will recur next sprint.
Instead the PM facilitates an exploration of the NEED behind the demand. Digging in, the PM finds analyst A only needs the database, while analyst B only needs the API layer: their usage barely overlaps. The collaborative solution — spin up a second lightweight environment for B in the morning, or parallelize the datasets — lets both meet their deadline. No one concedes: it is win-win.
Same conflict, two modes: what each produces
| Criterion | Compromise (half a day each) | Collaboration (probe the need) |
|---|---|---|
| Deadlines met | Neither. | Both. |
| Satisfaction | Each loses a little (give-and-take). | Each wins (win-win). |
| Root cause | Untouched: the conflict returns. | Addressed: real needs separated. |
The exam reflex here
When an option offers to "split it fairly / cut the difference", it is almost always a compromise — a plausible trap. Look for the option that first explores the underlying need and invents a solution where each gets what matters most: that is Collaborate.
Artifact → decision → PMI action map
Artifact
Team charter / RACI / conflict log
Decision
Who must decide, contribute, or be realigned?
PMI action
Facilitate, clarify roles, document agreement, and monitor behavior.
Avoid: Forcing or escalating before seeking the root cause.
Recommendations
- Memorize the TKI set and that "Collaborate" is almost always the right exam answer.
- If the question describes a safety/life emergency, "Force" may then be correct — read the context.
Tips
- Conflict mnemonic: Collaborate (best) → Compromise → Force → Accommodate → Avoid (worst).
- "Compromise" ≠ "Collaborate". Compromise makes each lose a little; collaboration makes everyone win.
Chapter quiz
1.Which resolution mode produces the most durable win-win outcome?
2.Indefinitely postponing a conflict hoping it resolves itself is which mode?
3.Among project conflict sources, which is the LEAST frequent?
4.Two members fight over a single shared tool each says they need all day. Which response best reflects Collaborate (not Compromise)?
4. The PMI reflex when facing conflict
The expected decision sequence
When an exam question describes a conflict, the PMI expects a precise sequence. Memorize it: it separates the right answer from the traps.
- Acknowledge the conflict early — don't wait for it to worsen.
- Understand the situation — gather facts from those involved, privately.
- Bring the parties together to confront the problem (not the people), directly.
- Facilitate a collaborative (win-win) resolution, using the ground rules.
- Escalate only if direct resolution fails or exceeds your authority.
The 4 classic PMI traps
1) Escalate immediately to the sponsor or HR — no, act first. 2) Force a decision to "save time" — no, except in an emergency/safety case. 3) Ignore / let the team "sort it out" — no, avoidance worsens it. 4) Discuss the conflict in public or by group email — no: always privately, face to face, on the problem and the present.
Answer keywords
Good answers: "meet the parties", "understand the root cause", "facilitate", "collaborate", "confront the problem". Bad answers: "escalate first", "impose", "ignore", "replace the member", "in a plenary meeting".
Negotiation mini-case: positions vs interests
A negotiation stays stuck as long as people argue over POSITIONS (what each side demands). It unblocks the moment you trace back to the INTERESTS (the real need behind the demand). This is the heart of principled negotiation: separate the people from the problem and seek mutual gain.
Case: the sponsor demands a June 30 delivery; the team insists it needs two more weeks. As long as the discussion is about the date (the positions), it is a win-lose tug-of-war. The PM then facilitates the question "why that date / why that delay?" to uncover the underlying interests.
Tracing from position to interest unblocks the solution
| Party | Position (what is demanded) | Interest (the real need) |
|---|---|---|
| Sponsor | "Everything must ship by June 30." | Showing a credible demo at the early-July client trade show. |
| Team | "We need two more weeks." | Not shipping an unstable product that would damage their credibility. |
The interests do not conflict: the sponsor wants a credible demo, the team wants quality. The win-win solution: ship on June 30 a smaller but stable increment covering exactly the journey shown at the show, and schedule the rest two weeks later. Both interests are met, even though the positions looked irreconcilable.
The PMI negotiation reflex
Never negotiate over positions. Ask "why?" and "why not?" to surface interests, separate the person from the problem, then look for mutually beneficial options judged against objective criteria. This is exactly the collaborative (win-win) posture the exam expects.
Artifact → decision → PMI action map
Artifact
Team charter / RACI / conflict log
Decision
Who must decide, contribute, or be realigned?
PMI action
Facilitate, clarify roles, document agreement, and monitor behavior.
Avoid: Forcing or escalating before seeking the root cause.
Recommendations
- Before answering, spot each option's verb: facilitate/collaborate (good sign) vs impose/escalate/ignore (bad sign).
- If two options seem good, pick the most proactive and collaborative — not the fastest.
Tips
- One-line reflex: "I bring the people involved together, privately, to understand and solve it together."
Chapter quiz
1.Where and when should an interpersonal conflict be addressed per the PMI?
2.Which action is a classic trap to avoid when a conflict emerges?
3.What is the very first recommended step when facing a conflict?
4.A sponsor demands a delivery date; the team finds it untenable. The negotiation is stuck. What does the PM do FIRST?
Decision toolkit
PMP decision trees & running case
Use this when two answers look right: qualify the context, choose the artifact, then act.
Team conflict
Two people or groups block a decision or blame each other.
1. The conflict is new or moderate.
Decision: Address it early, privately, with the involved parties.
Action: Facilitate a fact-based discussion and seek the root cause.
2. The conflict involves roles or responsibilities.
Decision: Clarify work governance.
Action: Update the RACI, team charter, or communication plan.
3. The conflict persists after facilitation.
Decision: Escalate only with evidence and options.
Action: Present impacts, alternatives, and a recommendation to the sponsor/manager.
Trap: Forcing a solution or escalating immediately is rarely the first PMI action.
Responsible escalation
The project manager can no longer resolve a blocker alone.
1. The PM has not yet spoken with the parties involved.
Decision: Do not escalate too early.
Action: Meet the parties, clarify facts, impacts, and options.
2. The blocker exceeds the PM's authority.
Decision: Escalate with a recommendation.
Action: Present context, options, impact, and the decision needed.
3. There is an ethical or compliance violation.
Decision: Use the appropriate formal channel.
Action: Document without accusation and follow organizational policy.
Trap: Escalating without analysis or options transfers the problem instead of managing it.
Resistant stakeholder
A key user rejects the solution, slows approvals, or blocks adoption.
1. Resistance comes from lack of understanding.
Decision: Adapt communication.
Action: Connect the change to their benefits, impacts, and expectations.
2. Resistance comes from a real business risk.
Decision: Do not treat it as personal opposition.
Action: Analyze the concern, update risks/requirements, and co-create the response.
3. Adoption remains low.
Decision: Strengthen the change management plan.
Action: Add training, champions, feedback loops, and adoption metrics.
Trap: Ignoring a resistant stakeholder often turns adoption risk into benefits failure.
AI & sustainability project: energy optimization
Charter
Objective: reduce energy consumption by 12% with a responsible AI model.
Backlog / WBS
Hypotheses, experiment backlog, model card, ethical thresholds, controlled pilots.
Stakeholders
- ESG sponsor, data science, operations, IT, AI compliance, field users.
- Success measured by savings, adoption, explainability, and no negative HSE impact.
Risks
- Data bias, non-explainable model, operator rejection.
- Energy optimization that degrades quality or safety.
Change
Request: automate a critical decision. Response: assess risk, human control, compliance, and acceptability.
EVM
Connect model/deployment cost to measured benefits; include AI operating costs.
Closure
Model monitoring, operations handover, carbon/energy benefits tracking, responsible audit.
Practical examples
Scheduling conflict between two leads
Scenario : The back-end lead and the front-end lead argue over the delivery order of two features; the tone rises during the daily.
Project manager's action : Meet the two leads separately then together, refocus on the sprint's value goal, and facilitate a shared prioritization (collaborate) — not decide for them.
Member blocked by an external dependency
Scenario : A developer cannot proceed because a third-party team hasn't delivered an API; her frustration grows.
Project manager's action : Act as a servant leader: take ownership of removing the impediment (contact the third-party team, negotiate a date) to unblock the person, instead of asking her to wait.
Recurring tension in a distributed team
Scenario : In a multi-timezone virtual team, repeated chat misunderstandings create friction.
Project manager's action : Co-define ground rules for communication, set up a regular synchronous channel, and handle each tension over video (face to face), never in a public thread.
Exam strategy
- People questions are situational: they test a decision, not a definition. Always ask yourself "what should the PM do FIRST / NEXT?".
- By default the PM acts personally and proactively. Be wary of "escalate", "do nothing", or "impose" answers.
- In agile/hybrid contexts the reflex is servant leadership: facilitate, coach, remove impediments.
- For conflict, the right answer often contains "bring the parties together", "understand", "collaborate" — not "decide for them".
Module assessment
1.Recognizing your own emotions as they arise is which EI component?
2.In an agile team, what is the servant leader's primary role when facing an impediment?
3.Two TKI modes are often confused. Which one makes each party "lose a little"?
4.A conflict has reached the "crusade" level (Leas level 4). What does this level indicate?
5.A member asks the PM to "decide for them" on a team disagreement. Most servant-leader-aligned response?