Conflict Management in Projects: A Practical Guide
Experienced project managers do not expect conflict-free projects. They expect conflict — and they have a plan for it. The research on team performance is unambiguous: teams that surface and resolve disagreements constructively outperform teams that suppress conflict or pretend it does not exist. The project manager's job is not to create harmony at all costs; it is to build an environment where disagreements are surfaced early, addressed directly, and resolved in ways that preserve working relationships and keep the project moving.
Where Project Conflict Comes From
Project conflict has predictable sources. Recognising them early is the first step toward managing them effectively:
Resource competition: When multiple projects compete for the same specialists, equipment, or budget, conflict between project managers and functional managers is almost inevitable. This is an organisational design problem as much as a people problem.
Priority disagreements: Stakeholders frequently disagree about what is most important — which features, which quality standards, which delivery dates. These disagreements, left unresolved, surface as project-level conflict.
Technical disputes: Engineers, architects, and specialists often have strong views about the right technical approach. These disputes can be healthy — they surface options and test assumptions — or destructive, if they become personal or stall decision-making.
Personality and communication style clashes: Some conflict has less to do with the substance of disagreement than with how people communicate. A direct communicator and an indirect communicator can misread each other chronically, even when they broadly agree on the substance.
Ambiguous roles and accountabilities: When it is unclear who has decision authority — or when authority is nominally assigned but not actually respected — conflict fills the vacuum.
The Thomas-Kilmann Conflict Modes
The Thomas-Kilmann Conflict Mode Instrument (TKI) identifies five approaches to conflict, each defined by the combination of assertiveness (how strongly you pursue your own concerns) and cooperativeness (how strongly you attend to the other party's concerns):
Competing (high assertiveness, low cooperativeness). Appropriate when a quick, decisive action is needed, when you are certain you are right on a matter with significant consequences, or when protecting an organisational interest against someone acting in bad faith. Overused, it destroys trust and suppresses legitimate concerns.
Collaborating (high assertiveness, high cooperativeness). The ideal mode when both parties' concerns are too important to compromise on — working through it together produces a better outcome than either party could reach alone. It takes time and goodwill. It is also the right approach when you need buy-in, not just compliance.
Compromising (moderate assertiveness, moderate cooperativeness). Useful when a workable solution is needed quickly and neither party is willing (or able) to invest the time required for true collaboration. Compromise means both parties get something and give something. It is not a failure mode, but it should not be the default.
Avoiding (low assertiveness, low cooperativeness). Appropriate when the issue is trivial, when emotions are too high for a productive conversation right now, or when you need more information before engaging. Chronic avoidance of real conflicts is one of the most destructive patterns on projects — it allows problems to compound until they are much harder to resolve.
Accommodating (low assertiveness, high cooperativeness). Appropriate when you realise you are wrong, when the issue is more important to the other party than to you, or when you need to build goodwill for a more important issue later. Like avoidance, it becomes destructive when it is the default response to all conflict.
The key insight from the TKI model is that no single mode is always right. A skilled conflict manager reads the situation and consciously selects the appropriate approach — rather than defaulting to whichever mode comes most naturally.
The Project Manager's Role in Conflict
The project manager is rarely the right person to be the decision-maker in a substantive conflict. Their role is usually better framed as facilitator: creating the conditions in which the people who do have the authority and expertise can reach a resolution.
Practically, this means structuring the conversation rather than entering it as a party. It means ensuring both sides articulate their actual interests — not just their stated positions. It means identifying the criteria by which a decision will be evaluated before proposing solutions. And it means documenting the resolution and its rationale in writing, so that the same conflict does not re-emerge three weeks later when memories diverge.
When to Escalate
Escalation is not a failure. It is the appropriate response when: the conflict has reached an impasse that the parties cannot resolve at their level; when the issue involves authority or resource decisions that belong to a sponsor or steering committee; or when the conflict has escalated to behaviour (personal attacks, exclusion, bad-faith negotiation) that requires intervention.
Good escalation is not "going over someone's head to complain." It is a structured process: document the issue, document what resolution was attempted and why it failed, articulate the decision needed from the escalation point, and propose a timeline for resolution. Escalation done well is a sign of professional maturity, not weakness.
Rebuilding Trust After Conflict
Conflict that is resolved — even imperfectly — does not have to permanently damage a working relationship. What matters is whether the resolution process was perceived as fair and whether both parties feel heard. Small behaviours after the fact reinforce or undermine the resolution: following through on commitments made during the resolution, acknowledging the other party's perspective publicly, and resisting the temptation to relitigate settled issues.
Project managers who invest in team health as a continuous discipline — regular retrospectives, honest one-on-ones, clear role definitions updated when circumstances change — spend less time managing acute conflict because they surface and address tensions before they become crises.
XNM Consulting helps project managers and organisations build the leadership capabilities needed to deliver complex programmes. Learn more about our .