PMP lesson · People & Team Leadership · Leading the team · lesson 3 of 4 · about 8 minutes
Conflict management: five techniques and when to use each
All approachesFree full lesson
Goal: After this lesson you can name the five conflict techniques, know which is usually best, and recognise the situations where another technique is right.
1The situation
Two arguments in one day
Morning: two controls engineers disagree about sensor placement on the robot cell. The discussion is getting louder, and the design is due next week.
Afternoon: during a test, the team argues about whether to stop the line after an unexpected robot movement near the fence.
The first conflict needs everyone's ideas. The second needs a decision in seconds. The PMP expects you to know the difference.
2Five techniques
Each technique has a PMP name pair. Learn both names:
Technique
What happens
Result
Collaborate / problem-solve
Explore all views and interests; find a solution that meets both
Win-win, lasting
Compromise / reconcile
Each side gives up something
Partial satisfaction
Smooth / accommodate
Emphasise agreement; one side yields
Peace, but the issue may return
Withdraw / avoid
Postpone or step away
Temporary; issue unresolved
Force / direct
Decision imposed by authority
Fast; win-lose
Default: collaborate.Exception: immediate danger → force/direct. A short withdraw can be right when emotions are high and the decision can wait.
How the PM handles team conflict
Let the team try to resolve it first; facilitate if needed. Address it early, privately when it involves individuals, and focus on the work, not personalities. Escalate only after real attempts have failed or when it is outside the team's authority.
3The five techniques and when they fit
Collaborate / problem-solve · win-win; open discussion of interests
←
Usually the best; needs time and trust
Compromise / reconcile · each side gives something
←
When collaboration fails or time is short; lose-lose elements
Smooth / accommodate · emphasise agreement, yield on a point
←
Preserve the relationship on minor issues
Withdraw / avoid · postpone, step back
←
Temporarily, to let emotions cool, when the decision can wait
Collaboration is the usual exam answer, but each technique has a situation where it is right.
Where conflict comes from
Most common sources of conflict on projects
1. Schedules and priorities
2. Scarce resources
3. Technical opinions
4. Administrative procedures
5. Cost · personalities (personality is usually the least frequent root cause)
Conflict about the work is normal and can improve decisions. Address it early, privately where appropriate, and focus on issues, not people.
4Worked example: the two arguments
Given: Sensor placement disagreement · unexpected robot movement
Sensor placement, decision in a week
Collaborate
Bring both engineers together with data; find a design both support
Discussion turns personal
Withdraw briefly
Pause; continue tomorrow with the measurements
Unexpected robot movement
Force / direct
Stop the line now; investigate afterwards
Afterwards
Collaborate again
Root-cause review with the whole team
The same day needed three techniques. The skill is matching the technique to the situation.
5Wrong vs right: the common traps
✘ Wrong thinking
“Collaborate is always the answer.”
✔ Right thinking
Usually, but immediate safety hazards need force/direct.
✘ Wrong thinking
“Avoiding conflict is always wrong.”
✔ Right thinking
A short withdrawal to let emotions cool can be appropriate when the decision can wait.
✘ Wrong thinking
“The PM should decide technical disagreements to save time.”
✔ Right thinking
Help the people involved collaborate first; impose decisions only when needed.
✘ Wrong thinking
“Compromise is the best because everyone gets something.”
✔ Right thinking
Compromise often leaves both sides partly unhappy; collaboration seeks a better solution.
✘ Wrong thinking
“Discuss one person's behaviour in the team retrospective.”
✔ Right thinking
Address individual behaviour privately.
6How it looks on the exam
Exam-style question 1. Two team members disagree about a technical approach. The decision is needed next week. What should the project manager do FIRST?
A. Decide the approach
B. Encourage them to collaborate on a solution
C. Escalate to their functional managers
D. Remove one of them from the project
Show the answer and the decode
Answer: B.
In simple English
A technical disagreement with time available.
What is the question really asking?
The first step.
Key words / trigger
“disagree about a technical approach”
PMP logic
Collaboration is the default when there is time; it creates a solution both can support.
Why the wrong answer looks attractive
Deciding seems efficient, but it skips the team's knowledge and creates a loser.
Exam-style question 2. There is an immediate safety hazard on the line, and team members disagree about whether to stop production. Which conflict approach fits?
A. Collaborate for as long as needed
B. Force/direct
C. Withdraw
D. Smooth
Show the answer and the decode
Answer: B.
In simple English
Danger now; disagreement about stopping.
What is the question really asking?
The right technique.
Key words / trigger
“immediate safety hazard”
PMP logic
In an emergency, the leader decides and directs immediately.
Why the wrong answer looks attractive
Collaboration is usually best, but not when people are in danger.
7Remember this
Your memory card
Five: collaborate, compromise, smooth, withdraw, force
Default collaborate; force/direct for immediate danger
Short withdraw when emotions run high and time allows
Address conflict early, privately, on the issue, not the person