10.1 Sources and Impacts of Conflict
Key Takeaways
- Project conflict has structural sources — competing priorities, scarce shared resources, unclear roles, schedule and cost pressure, and interface ambiguity — as well as interpersonal ones.
- Matrix structures generate conflict by design because staff answer to both a functional manager and a project.
- Conflict is not inherently negative: task-focused disagreement surfaces risks, tests assumptions, and improves decisions.
- Conflict becomes destructive when it turns from the task to the person, or when it is suppressed and resurfaces as disengagement.
- The project manager’s aim is to keep conflict task-focused and resolved at the lowest effective level, not to eliminate disagreement.
Why conflict resolution matters on the APM PMQ
Conflict resolution sits in Area C (People and behaviours) as learning objective 11. The syllabus expects you to understand sources of conflict within a project, that conflict can have positive and negative impacts, and ways conflict can be addressed, including the Thomas-Kilmann Conflict Mode Instrument.
On the PMQ, weak answers moralise ("conflict is bad") or prescribe one style for every situation. Strong answers diagnose the source, judge constructive vs destructive impact, choose an appropriate mode, and link the response to objectives, relationships, and governance. Long-response scenarios often involve stakeholders with legitimate but incompatible needs — your task is applied people-management, not avoidance or pure force.
Conflict is disagreement, opposition of interests, or friction that affects how people work together. It is almost inevitable on projects because temporary teams combine different functions, suppliers, priorities, and success measures under time and resource constraints.
Sources of conflict within a project
Conflict rarely appears without a trigger. Exam scenarios usually map to one or more of the sources below. Name the source first; the resolution path follows.
| Source | Typical trigger | Example signals |
|---|---|---|
| Schedule | Unrealistic dates, concurrent peaks, late dependencies | Missed milestones blamed between teams; overtime disputes; "who delayed whom" arguments |
| Resource | Scarce people, equipment, budget, or facilities | Two work packages need the same specialist; functional managers withhold staff for BAU |
| Priority | Competing objectives or portfolio ranking | Stakeholder A wants quality polish; Stakeholder B wants earliest go-live |
| Technical / methods | Different professional judgements on solution design | Architect vs engineer vs operations disagree on approach |
| Scope and requirements | Ambiguous needs, changing requirements, gold-plating | "That was always implied" vs "that was never in scope" |
| Commercial / contractual | Payment, risk allocation, variations, performance | Supplier claims client delay; client claims poor quality |
| Personality and style | Communication preferences, ego, trust history | Personal attacks, withdrawn silence, clique behaviour |
| Cultural / diversity | Different norms on hierarchy, feedback, time, risk | Misread silence as agreement; public challenge seen as disrespect |
| Role and authority ambiguity | Unclear RACI, dual reporting in a matrix | Two people believe they own the same decision |
| Values and ethics | Safety, compliance, or fairness vs delivery pressure | Pressure to skip a test or under-report a risk |
How sources interact
Sources compound. A resource shortage creates schedule pressure; schedule pressure hardens priority fights; priority fights become personality conflict if trust is low. On long responses, trace the chain: structural cause → behavioural symptom → mode and process response. Treating only the interpersonal heat without fixing the structural source (for example missing RACI or under-resourced critical path) invites recurrence.
Scenario: mixed sources
A matrix IT project needs a cybersecurity specialist for penetration testing in the same week that a major production incident needs the same person. The resource conflict is real. The application owner and the security lead also disagree on residual risk acceptance (technical / priority). Emails become personal (personality). The project manager must address capacity and decision rights — not only "tell them to get along."
Positive and negative impacts of conflict
The syllabus is explicit: conflict can help or harm. Impact depends on intensity, duration, power balance, and how leaders handle it.
Constructive (positive) impacts
When managed well, conflict can:
- Surface hidden risks and assumptions — disagreement forces issues onto the agenda before they become crises.
- Improve decision quality — alternative options are tested rather than rubber-stamped.
- Increase ownership — people who debate and then commit tend to support implementation.
- Clarify roles and priorities — conflict exposes gaps in RACI, tolerances, or requirements.
- Strengthen relationships if resolution is fair — trust can rise after hard but respectful problem-solving.
- Drive innovation — constructive challenge questions "the way we always do it."
Constructive conflict stays task-focused (ideas, data, options) rather than person-focused (blame, status). It has a time box: parties move to a decision and act.
Destructive (negative) impacts
Unmanaged or poorly handled conflict can:
- Delay schedule through stalemate, rework, or passive resistance.
- Increase cost (idle resources, claims, turnover, legal fees).
- Damage quality when people hide problems or rush past controls to "win."
- Erode morale and motivation — stress, absenteeism, loss of key people.
- Fracture stakeholder relationships and sponsor confidence.
- Create toxic climate — fear, politics, information hoarding.
- Trigger escalation to formal dispute (commercial or industrial) that consumes management attention.
Exam trap: Saying conflict is always negative. APM expects balanced recognition of positive and negative impacts, then a judgement on this situation.
Impact judgement table
| Signal | More likely constructive | More likely destructive |
|---|---|---|
| Focus | Issues, evidence, options | Personalities, blame, history |
| Communication | Direct, respectful, multi-way | Avoidance, gossip, threats |
| Outcome path | Decision criteria and owner clear | Stalemate or win-at-all-costs |
| After-effect | Clearer plan; relationships intact or stronger | Residual resentment; hidden workarounds |
| Link to objectives | Improves fit to success criteria | Optimises one party at expense of project |
Which statement best reflects APM PMQ thinking on the impacts of conflict?
In a matrix organisation, team members regularly receive competing instructions from their functional manager and the project manager. How should this conflict best be characterised?