about 4.1% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Conflict on a project is not a sign that something has gone wrong. It is a sign that people care about
different things and are close enough to each other to notice. PMI's position is blunt: conflict is
inevitable, and it is not inherently bad. Handled openly and early, it produces better
decisions and stronger trust. Suppressed, it goes underground and comes back as missed handoffs, quiet
sabotage, and people who stop telling you the truth.
On a GCHS rehab job, conflict shows up in familiar shapes: the framing sub and the plumber both need the
same wall cavity on the same day; the designer wants a wider door than the structural engineer will approve;
a crew lead thinks an inspector is being unreasonable; two team members simply cannot stand each other. Each of
those needs a different move, and the exam expects you to know which.
Sources of conflict, from most to least common
Classic research by Thamhain and Wilemon, published in PMI's library, ranks schedules,
project priorities, and manpower resources as the top three sources of project conflict, with personality last. That matters on the exam, because it tells you where
to look first for root cause.
Schedules: sequencing, dependencies, who goes first
Project priorities: what matters most when everything cannot be first
Resources: people, equipment, budget, access to the site
Personality: least common, and usually a symptom of one of the above left unresolved
When an exam item hands you a personality clash, look for the structural cause hiding underneath it. Two
crew leads who snipe at each other every Monday usually have an unresolved resource or priority dispute, not a
character defect.
The five conflict-resolution modes
These come from the Thomas-Kilmann framework and PMI uses them directly. Each is a combination of how much
you assert your own concern and how much you cooperate with the other party's. There is no universally correct
mode, but there is a universally preferred one on the exam.
Mode
Also called
What it looks like
Use it when
Result
Collaborate
Problem solve
Both parties dig into the underlying needs and design a solution that meets both
The issue matters, there is time, and the relationship is ongoing
Win / win (durable)
Compromise
Reconcile
Each side gives something up to reach a middle position
Positions are entrenched, time is short, a temporary settlement is acceptable
Lose / lose (partially); often temporary
Smooth
Accommodate
Emphasize areas of agreement, concede your position to keep harmony
The issue is minor to you and major to them, or you need goodwill for later
Buys calm; underlying issue survives
Force
Direct, compete
One party imposes the decision, often by positional power
Genuine emergency, safety, ethics, or legal compliance
Win / lose (fast, and costly to trust)
Withdraw
Avoid
Retreat from the disagreement or defer it
You need cooling-off time or more information, or the issue is genuinely trivial
Nothing is resolved; can be a legitimate temporary tactic
Key points
Collaborate / problem solve is the default best answer when the item gives you any
time and any willingness on both sides. It is the only mode that produces a durable win-win.
Force is right only for safety, ethics, legal, or true emergency. An unsafe scaffold
gets a forced decision immediately; you do not facilitate a dialogue about fall protection.
Withdraw is not always wrong. If tempers are hot, a short cooling-off period before a
facilitated conversation is a legitimate first step, but it must be followed by resolution.
Compromise is tempting because it sounds fair. On the exam it is usually the second best
answer, chosen when collaborate is unavailable.
How PMI wants a project manager to actually handle it
The sequence matters more than the vocabulary. A reliable pattern for situational items:
1. Notice it early. Small conflicts are cheap. Conflict that has escalated to formal
complaints has already cost you.
2. Go direct and private. Speak with the people involved, individually first if
emotions are high. Never correct someone in front of the crew.
3. Understand root cause before proposing anything. Ask open questions. Listen for the
interest under the position: the plumber's position is I need Tuesday; the interest may be
my second crew is committed elsewhere Wednesday.
4. Bring them together and facilitate. The PM is a neutral facilitator, not a judge.
The goal is an agreement they build, because they will honor that one.
5. Consult the agreed rules. Team charter, ground rules, and the escalation path exist
precisely for this moment.
6. Document and follow up. Log the agreement, then check that it held.
7. Escalate only if the conflict is outside the team's authority or cannot be resolved.
Escalation is a last resort, not an opening move.
Escalation is almost never the first answer
On the exam, escalate to the sponsor, notify HR, or raise it to the steering
committee are usually distractors placed to catch the instinct to hand the problem upward. They become
correct only when the matter genuinely exceeds the PM's authority: contractual disputes, harassment,
safety violations that a party refuses to correct, or a decision that changes the project's baselines.
Conflict in adaptive and hybrid environments
Adaptive teams are designed to surface disagreement continuously rather than store it up. The mechanisms
are structural, and the exam expects you to reach for them:
Retrospective: the standing forum for interpersonal and process friction. If a
recurring team conflict is described and a retrospective is an option, it is often the right venue.
Daily standup: surfaces blockers and collisions within a day, but it is not the place
to resolve them; take the discussion offline immediately after.
Working agreements / ground rules: the team's pre-agreed rules for how disagreement is
handled, written before anyone is angry.
Product owner: the single voice for priority conflicts about what gets built. Priority
disputes between stakeholders are routed there, not settled by the team.
Coaching: a servant leader coaches the team toward resolving its own conflicts rather
than becoming the permanent referee.
In hybrid GCHS work, a frequent conflict is between the contractual, baselined portion of the job and the
evolving portion. A designer iterating on finishes with the homeowner can collide with a subcontractor working
to a frozen submittal. The PM resolves that by making the boundary explicit and routing changes through the
right channel, rather than by picking a side.
Emotional intelligence, psychological safety, and the conditions for healthy conflict
Teams argue productively only where it is safe to be wrong out loud. Psychological safety
is the shared belief that speaking up will not be punished. Where it is absent, conflict does not disappear;
it just stops being visible to the PM.
Emotional intelligence is the PM's tool for this: self-awareness (noticing your own
reaction), self-regulation (not acting on it), social awareness or empathy (reading the room and the person),
and relationship management (steering the interaction). A PM who notices their own irritation rising and
chooses to ask a question instead of making a statement is doing the skill, not the theory.
Practical moves that raise safety: separate the person from the problem, attack the issue and not the
individual, invite dissent explicitly, thank people who raise bad news, and never resolve conflict by rank
when you can resolve it by reasoning.
Safety and ethics override everything
If an exam scenario involves a safety hazard, a code violation, harassment, or falsified documentation,
collaboration and consensus are not the answer. Stop the unsafe work or address the violation
immediately, then handle the process afterward. Lead-safe practices, fall protection, and
structural integrity on an occupied home are not negotiable items in a dialogue.
Negotiating agreements without breaking relationships
Much project conflict is really a negotiation, with subs, funders, inspectors, or internal departments.
PMI's leaning is principled negotiation: focus on interests rather than stated positions, generate several
options before choosing, and judge them against objective criteria such as the specification, the code, market
pricing, or the funding agreement. That keeps the argument about the standard instead of about who is more
stubborn, and it preserves a relationship you will need again next month.
Practice Questions
1. In the Thamhain and Wilemon research on project managers, which is the MOST common source of conflict on projects?
Cost estimates
Administrative procedures
Personality differences
Schedules, priorities, and resources
Answer: d. Structural issues (schedules, priorities, and resources) dominate project conflict, while personality clashes are the least common and are usually symptoms of an unresolved structural dispute. Assuming personality first sends the PM looking in the wrong place for root cause.
2. Two subcontractors need access to the same wall cavity on the same day and are arguing on site. There is time in the schedule to work this out. Which conflict-resolution mode should the project manager use?
Withdraw: let them settle it themselves
Collaborate: explore both needs and design a sequence that works for both
Smooth: emphasize that they normally get along well and ask one to give way this once
Force: direct one of them to yield
Answer: b. With time available and both parties present, collaboration produces a durable win-win and preserves a working relationship they will need again. Forcing gets speed at the price of trust, and smoothing papers over a real sequencing problem that will simply recur.
3. Which conflict-resolution mode produces a genuine win-win outcome?
Compromise
Collaborate / problem solve
Smooth / accommodate
Withdraw / avoid
Answer: b. Only collaboration digs into the underlying interests and builds a solution that satisfies both parties. Compromise is the common wrong pick; it splits the difference, so both sides give something up, making it a partial lose-lose.
4. A project manager sees a crew member working on a roof without fall protection. What should the project manager do FIRST?
Stop the work immediately
Schedule a conversation with the crew lead after the shift
Add the observation to the issue log
Facilitate a team discussion about safety culture
Answer: a. Safety overrides collaboration; the PM directs, and directs now. Every other option leaves a person exposed to a fall while a process runs. The coaching conversation and the systemic follow-up happen after the hazard is removed.
5. Two team members have a heated argument in front of the whole crew. Emotions are running high. What is the BEST immediate action?
Ask HR to intervene
Tell them to drop it and get back to work
Have both explain their positions to the group so everyone can weigh in
Separate them, allow a brief cooling-off period, then meet with each privately before bringing them together
Answer: d. A short withdrawal is a legitimate tactic when emotions are too high for productive dialogue, but it must be followed by private conversations and a facilitated resolution. Public debate escalates and humiliates, calling HR is premature escalation, and ordering them to drop it drives the conflict underground.
6. When is forcing an appropriate conflict-resolution mode?
When safety, ethics, legality, or a true emergency requires an immediate decision
Whenever the schedule is tight
When one party is more senior than the other
Whenever the project manager has more authority than the parties involved and time is short
Answer: a. Force is reserved for situations where the cost of deliberation is unacceptable: safety, ethics, legality, or a true emergency. Using positional power routinely because it is faster damages trust and teaches the team to stop raising issues.
7. Two crew leads have sniped at each other every Monday for a month, and there is no known history of personal friction between them. What should the project manager do FIRST?
Recommend anger-management coaching for both
Investigate whether an unresolved schedule, priority, or resource dispute is behind it
Reassign one of them to a different crew
Document the behavior for a future performance review and revisit it if it continues next month
Answer: b. Personality clashes are the least common source of conflict and usually mask a structural cause underneath. Jumping to coaching, reassignment, or a paper trail treats the symptom instead of the schedule, priority, or resource issue actually driving it.
8. An adaptive team keeps having the same disagreement about testing standards, sprint after sprint. Which forum is BEST suited to resolve this recurring pattern?
The sponsor review
The daily standup
The retrospective
A formal grievance procedure
Answer: c. The retrospective is the standing forum for interpersonal and process friction, and a recurring issue is exactly what it exists to surface and resolve. The standup surfaces blockers but is not the place to work through them.
9. A project manager is negotiating a delivery date with a lumber supplier who has quoted a firm position. Which approach does PMI recommend?
Escalate to the supplier's regional manager immediately
Insist on the originally quoted date because the contract says so and the schedule depends on it
Focus on each side's interests and generate options judged against objective criteria
Split the difference between the two proposed dates
Answer: c. Principled negotiation focuses on interests rather than stated positions and judges options against an objective standard such as market pricing or the funding agreement. Splitting the difference is a compromise reflex that skips the more durable option.
10. Two stakeholders disagree about which of two competing features should be built first in an adaptive project. Who resolves this?
The sponsor
The project manager, using their authority
The product owner, as the single voice for priority decisions
The team, by majority vote
Answer: c. Priority disputes between stakeholders are routed to the product owner, the single point for what gets built and in what order. The PM facilitates process, not backlog priority, and a team vote bypasses the role that owns that decision.
11. A subcontractor refuses to correct a documented safety violation despite repeated requests from the crew lead. What is the appropriate next step?
Escalate, since the matter is outside the team's authority to resolve
Document it and let the inspector discover it independently
Continue collaborating to find a compromise until the subcontractor agrees to correct the violation
Withdraw and revisit the issue next week
Answer: a. Escalation is a last resort, but a refused safety correction is exactly the kind of matter that exceeds the team's authority and legitimately becomes one. Continuing to negotiate or waiting leaves the hazard live.
12. Which term describes the shared belief among a team that speaking up with a concern or a mistake will not be punished?
Situational leadership
Emotional intelligence
Servant leadership
Psychological safety
Answer: d. Psychological safety is that shared belief, and without it conflict does not vanish, it just stops being visible to the project manager. Emotional intelligence is the PM's personal skill set, not the team's collective belief.
13. During a heated meeting, a project manager notices her own irritation rising and, instead of reacting, pauses to ask a clarifying question. Which emotional intelligence component is she demonstrating?
Self-regulation
Social awareness
Empathy
Relationship management
Answer: a. Self-regulation is noticing a reaction and choosing not to act on it, which is precisely the pause described. Social awareness is reading the other person's state, a different skill applied at a different moment.
14. During a daily standup, two developers reveal they are blocked by the same conflicting dependency. What should the project manager do?
Ignore it since standups are for status only and the team will raise it if it matters
Note it, then take it offline right after the standup
Resolve the conflict on the spot in front of the whole standup
Add it to the retrospective agenda for next month
Answer: b. The standup surfaces blockers and collisions but is not the place to resolve them; the right move is to take the discussion offline right after. Resolving it live turns a fifteen-minute status check into a working session for everyone else, and waiting a month lets the blocker sit unresolved.
Glossary
Collaborate / problem solve
A conflict-resolution mode that explores both parties' underlying needs and designs a solution meeting both; the default best answer when time and goodwill allow.
Compromise / reconcile
Each side gives something up to reach a middle position; a workable but often temporary settlement.
Smooth / accommodate
Conceding your own position to preserve harmony when the issue matters more to the other party than to you.
Force / compete
One party imposes the decision by positional power; reserved for safety, ethics, legal, or true emergency situations.
Withdraw / avoid
Retreating from or deferring a disagreement, useful for cooling off but not a resolution by itself.
Principled negotiation
A negotiation approach that focuses on interests rather than positions and judges options against objective criteria.
Psychological safety
The shared team belief that speaking up will not be punished, a precondition for conflict to surface productively.
Emotional intelligence
Self-awareness, self-regulation, social awareness, and relationship management, used by the project manager to steer conflict constructively.