Managing team conflict

Conflict is inevitable on projects. People with different expertise, priorities and pressures are asked to make many decisions quickly with limited resources, and they will disagree. Handled well, conflict improves decisions: it brings hidden assumptions into the open, tests ideas and prevents groupthink. Handled badly, it damages relationships, slows work and drives good people away. This lesson focuses on conflict within the project team: its sources, how to diagnose its intensity, the five classic approaches and how to choose among them. PMP-121 extends these ideas to stakeholders and negotiation.

Healthy and unhealthy conflict

Researchers distinguish task conflict (disagreements about the work: goals, methods, priorities, technical choices) from relationship conflict (personal friction, dislike, perceived disrespect). Task conflict, kept at a moderate level in a psychologically safe team, tends to improve decisions. Relationship conflict almost always harms performance. The danger is that unmanaged task conflict can turn into relationship conflict when people start to take disagreements personally.

A project manager's job is therefore not to eliminate conflict but to keep it focused on the work, resolve it before it escalates, and make sure decisions get made. Teams with no visible conflict are not necessarily healthy; they may be avoiding difficult issues, a pattern Lencioni calls artificial harmony (lesson 5).

Sources of conflict on projects

Classic research by Thamhain and Wilemon in the 1970s ranked the most common sources of conflict on projects. Their list is still widely cited in PMP preparation, and the top sources remain familiar today.

A key insight is that personality is rarely the root cause, even when people describe conflict that way. "He's impossible to work with" often turns out to mean "we disagree about priorities and nobody has clarified them". Before treating a conflict as a personality clash, check whether a schedule, priority, resource or procedural issue lies underneath. Many conflicts are prevented by good planning, clear roles, ground rules and decision rights; the earlier lessons in this course are, in a sense, conflict prevention.

Diagnosing the level of conflict

Speed Leas's five levels of conflict, popularized for agile teams by Lyssa Adkins, help gauge intensity and choose a response. Conflict can move up the levels if unresolved, and the language people use is a good indicator.

At levels 1 and 2, the best response is usually to let the team work it out, perhaps with some facilitation. Rushing in to resolve every disagreement undermines self-organization and teaches the team to escalate everything. At levels 3 and above, the project manager needs to step in more actively, because positions are hardening and relationships are at risk.

The five conflict approaches

Kenneth Thomas and Ralph Kilmann described five conflict-handling modes based on two dimensions: assertiveness (how much you try to satisfy your own concerns) and cooperativeness (how much you try to satisfy the other party's concerns). PMI material uses similar names, sometimes with alternatives in brackets.

For the exam, remember a general order of preference when time and importance allow: collaborate first, because it addresses root causes and builds commitment; then compromise; and treat forcing and withdrawing as situational tools rather than defaults. Smoothing can preserve relationships but tends to leave the underlying issue unresolved. However, each mode has situations where it is the best choice, and questions often test whether you can spot them: a safety issue calls for forcing; a trivial disagreement over meeting room colours calls for avoiding; a heated exchange may need a short cooling-off break before collaboration is possible.

A process for resolving team conflict

When a team conflict needs active resolution, a simple structured process helps the project manager stay neutral and focused on the problem.

• Prepare: gather facts, identify who is involved, consider the level of conflict and choose a suitable setting. Private conversations are usually better than public confrontation.
• Set the ground rules: remind people of the team charter's conflict agreements; agree to listen without interrupting and focus on the issue, not the person.
• Understand each perspective: ask each person to describe the situation, what matters to them and why. Listen for interests (underlying needs) rather than positions (stated demands).
• Define the problem jointly: restate it in neutral terms that both can accept. "We need a test schedule that lets both releases meet their dates" is better than "Sara wants to take the environment from Tom."
• Generate options: brainstorm without judging; look for solutions that meet both sides' interests.
• Agree a solution: choose an option using agreed criteria, define actions and owners, and record the agreement.
• Follow up: check that the solution is working and that relationships have recovered.

The distinction between positions and interests, made famous by Fisher and Ury in Getting to Yes, is central. A position is what someone says they want ("I need the test environment all next week"); an interest is why they want it ("my release must be tested before the client demo on Thursday"). Positions often conflict; interests frequently do not. Once the interests are clear, creative solutions appear. PMP-121 develops this into a full negotiation method.

Ground rules and conflict

The ECO's "Manage conflicts" task includes communicating conflict management principles to the team and external stakeholders, establishing an environment that fosters adherence to common ground rules, and managing ground rule violations. In practice this means agreeing a conflict process in the team charter (lesson 4), such as "raise it directly with the person first; if unresolved in a week, involve the project manager; if still unresolved, the sponsor decides", and making sure everyone knows it. When conflict involves people outside the team, such as a vendor or another department, the same principles apply, but the project manager may need to use governance channels and negotiation.

Some conflicts are not ordinary disagreements. Under Canadian occupational health and safety law, harassment and violence, including bullying and repeated humiliating behaviour, must be addressed through the employer's policy and investigation process; for federally regulated employers, the Work Place Harassment and Violence Prevention Regulations under the Canada Labour Code set specific requirements. A project manager who sees such behaviour should act promptly and involve human resources rather than mediating it as a team conflict.

Common pitfalls

Project managers new to conflict often fall into predictable traps. Some avoid conflict altogether, hoping it will go away; it rarely does, and it usually escalates. Some take sides too quickly, often with the person they like or who spoke first. Some resolve every disagreement themselves, which disempowers the team. Some handle conflict in public, embarrassing people and hardening positions. And some treat the symptom, such as a heated email exchange, without looking for the cause, such as unclear priorities. The process above, combined with an understanding of the level of conflict and the five modes, helps avoid these traps.