Skip to main content
← Back to Preview Pages

Conflict Management and Resolution

Free Preview

Apply conflict resolution strategies — from collaborating to forcing — based on the source, stage, and context of project disputes as taught in the People domain.

Conflict Management and Resolution

Conflict is inevitable in projects. The People domain requires project managers to interpret the source and stage of conflict, analyze context, and recommend appropriate resolution strategies.

Sources of Conflict in Projects

Project conflicts arise from seven primary sources ranked by frequency:

  1. Schedule priorities — disagreements over task sequencing and deadlines
  2. Scarce resources — competition for people, equipment, or budget
  3. Technical opinions — differing approaches to solving problems
  4. Administrative procedures — disagreements over how work should be managed
  5. Cost estimates — conflicting views on budget and expenditures
  6. Personality clashes — interpersonal friction between team members
  7. Project priorities — competing views on what matters most

The Thomas-Kilmann Conflict Model

The TKI defines five conflict-handling modes based on two dimensions: assertiveness (satisfying your own concerns) and cooperativeness (satisfying others).

Five Modes:

  • Collaborating (Problem-Solving) — High assertiveness + High cooperativeness. Both parties work to find a win-win solution. PMI preferred approach for long-term resolution.
  • Compromising — Medium on both. Each party gives something up. Temporary settlement when time is limited.
  • Accommodating (Smoothing) — Low assertiveness + High cooperativeness. You concede when the issue matters more to the other party.
  • Competing (Forcing) — High assertiveness + Low cooperativeness. Win-lose. Used when quick decisive action is vital or for safety-critical decisions.
  • Avoiding (Withdrawing) — Low on both. Retreat or postpone. Appropriate when the issue is trivial or emotions need to cool.

Conflict Resolution Process

  1. Identify — recognize early, don't ignore warning signs
  2. Analyze the source — task-related, relationship-related, or process-related
  3. Select the appropriate mode — match TKI mode to the situation
  4. Facilitate resolution — focus on interests not positions
  5. Document agreements — record decisions and follow up
  6. Monitor outcomes — ensure resolution holds

Agile vs Predictive Approaches

In predictive environments, the PM mediates directly. In agile, teams self-manage conflicts; the Scrum Master facilitates only when the team cannot resolve independently. Agile surfaces conflicts through daily standups, retrospectives, and self-organizing norms. The key principle: address conflict at the lowest level before escalation.

When to Escalate

Escalate when: the conflict impacts the critical path, involves ethical violations, requires authority beyond the PM, or when the team has tried and failed to resolve it. Escalation is not failure — it is responsible project management.

Key Terms

Thomas-Kilmann ModelFramework with five conflict modes based on assertiveness and cooperativeness: Collaborating, Compromising, Accommodating, Competing, Avoiding.
CollaboratingWin-win resolution where all parties find a solution satisfying everyone. PMI preferred long-term approach.
CompromisingEach party gives up something for a mutually acceptable but partial solution.
Forcing/CompetingWin-lose approach for urgent or safety-critical decisions where one party prevails.
Smoothing/AccommodatingEmphasizing agreement areas and downplaying differences. One party yields.
Withdrawing/AvoidingRetreating from conflict. Appropriate for trivial issues or cooling-off periods.
Root Cause AnalysisTechnique identifying the underlying reason for conflict rather than addressing symptoms.

Common Traps

  • Assuming collaborating is ALWAYS correct. The exam tests situational judgment — forcing may be right for urgent safety issues.
  • Confusing compromising with collaborating. Compromising means both lose something. Collaborating means nobody gives up core needs.
  • Thinking the PM always resolves conflicts directly. In agile, teams self-manage first.
  • Forgetting conflict can be positive. Task-related disagreement often improves solutions.
  • Selecting avoiding as default. It is a deliberate strategy for specific situations only.

Ready to study more?

Create a free account to access all study pages and practice questions.

Get Started FreeTry Demo Exam