Conflict on Projects: How to Turn Tension into Progress
Every project manager who has run a real project has experienced it: the moment a disagreement stops being about the work and starts being about the people involved. Voices get sharper. Emails get longer. The weekly status meeting feels like a courtroom. Conflict on projects is not exceptional — it is structural. Resources are scarce, priorities compete, roles are often ambiguous, and people under pressure revert to their default behaviours. The question is not how to prevent conflict but how to respond to it in ways that keep the project moving.
Why Conflict Is Inevitable on Projects
Projects are temporary organisations assembled from people who do not normally work together, given a mandate to deliver something new under time and budget pressure. That combination is a conflict incubator. Functional managers and project managers disagree about how to allocate a team member's time. Subject-matter experts disagree about technical approaches. Sponsors have one definition of success; delivery teams have another. Stakeholders who were not adequately involved in requirements discovery discover at the end that what was built is not what they needed.
Add personality differences, differing risk tolerances, and the stress that comes with compressed timelines, and it becomes clear why conflict is not an aberration but a normal feature of project work. The project manager who goes into a project expecting harmony is setting herself up to be surprised — and unprepared.
The Conflict Escalation Model
Conflict rarely arrives fully formed. It escalates through recognisable stages. The first is disagreement: a difference of opinion about a technical approach, a priority, or a resource allocation. At this stage, the conflict is about the work, and it can be resolved through discussion, data, and decision-making.
If disagreement is not resolved, it personalises. The dispute is no longer about the approach — it is about the person advocating for it. Language shifts: "That approach won't work" becomes "You never understand the technical constraints." At this stage, the conflict has become harder to resolve because it now involves identity and face-saving, not just problem-solving.
Left unaddressed, personalised conflict escalates to confrontation: open hostility, coalition-building, deliberate obstruction. At this stage, the conflict has become a project risk in its own right, consuming energy and attention that should be directed at delivery. The project manager's job is to intervene early — ideally at the disagreement stage, before personalisation sets in.
Five Conflict Resolution Styles
The Thomas-Kilmann Conflict Mode Instrument describes five ways people respond to conflict, distinguished by their degree of assertiveness (pursuing your own concerns) and cooperativeness (attending to the other party's concerns).
Avoiding. Low assertiveness, low cooperativeness. Withdrawing from the conflict or postponing it. Appropriate when the issue is trivial, when tensions need time to cool, or when you do not yet have the information needed to resolve it. Overused, it allows small disagreements to fester into large ones.
Accommodating. Low assertiveness, high cooperativeness. Giving way to the other party's position. Appropriate when you realise you are wrong, when the relationship matters more than the outcome, or when the issue is more important to them than to you. Overused, it leads to resentment and a perception that you lack conviction.
Competing. High assertiveness, low cooperativeness. Pursuing your position firmly, at the other party's expense. Appropriate in genuine emergencies, when an unpopular decision must be implemented, or when you are certain you are right and the stakes are high. Overused, it destroys relationships and stifles the contributions of others.
Compromising. Moderate assertiveness, moderate cooperativeness. Finding a middle ground that partially satisfies both parties. Appropriate when a quick resolution is needed, when both parties have equal power, or when collaboration is not possible. The risk is that neither party gets what they actually need, and the resolution is merely acceptable rather than good.
Collaborating. High assertiveness, high cooperativeness. Working together to find a solution that fully satisfies both parties. The most time-intensive approach, but the one most likely to produce durable resolution and strengthen the relationship. Best suited to situations where the issue is too important to compromise and sufficient trust exists to have an honest conversation.
The Project Manager as Facilitator, Not Judge
The project manager's role in conflict resolution is not to adjudicate — to decide who is right and declare a winner. It is to facilitate: to create the conditions in which the parties can work through their disagreement and arrive at a resolution themselves. This distinction matters. A PM who consistently imposes resolutions creates compliance but not buy-in. It also creates dependency: every future conflict becomes a referral to the PM.
Effective facilitation starts with active listening — genuinely understanding each party's concern before attempting to resolve it. It continues with separating positions (what each party says they want) from interests (why they want it). Often, parties with opposing positions have compatible underlying interests, and a solution that addresses the interests is available even when a compromise between positions is not.
Task Conflict vs. Relationship Conflict
Research on team dynamics consistently distinguishes two types of conflict. Task conflict — disagreements about the work itself, the approach, the priorities — is often productive. Teams that engage in vigorous task conflict tend to make better decisions and produce better outcomes than teams that avoid it. Relationship conflict — interpersonal tension, attribution of bad motives, personal attacks — is almost uniformly destructive.
The project manager's goal is to keep conflict in the task domain for as long as possible and to intervene quickly when it begins to personalise. That requires creating norms that make task conflict safe — making it clear that disagreement about ideas is expected and welcomed — while making it equally clear that personalisation is not acceptable.
When to Escalate to the Sponsor
Not every conflict can or should be resolved at the project level. When a conflict involves a resource allocation decision that exceeds the project manager's authority, when two functional managers are in genuine disagreement about priority, or when the conflict has escalated to a level that is affecting project delivery, escalation to the project sponsor is appropriate.
Escalate with a framing that presents the conflict as a business decision requiring leadership alignment, not as a complaint about the parties involved. Bring a recommendation, not just a problem. "We have a conflict between X and Y about Z. I recommend approach A for these reasons. I need your support to implement it." That framing respects the sponsor's time and positions the PM as a problem-solver rather than a referee.
XNM Consulting builds high-performing project and programme delivery capabilities for complex organisations. Learn more on our Program and Project Delivery page.