Study guide

10.1 Sources and Impacts of Conflict

APM Project Management Qualification PMQ

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ

2 Life Cycles

2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations

3 Governance Arrangements

3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives

4 Sustainability

4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures

5 Business Case

5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change

6 Procurement

6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods

7 Reviews & Assurance

7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance

8 Transition & Benefits Management

8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits

9 Stakeholder Engagement & Communication

9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication

10 Conflict Resolution

10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model

11 Leadership

11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence

12 Team Management

12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams

13 Diversity & Inclusion

13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment

14 Ethics, Compliance & Professionalism

14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape

15 Requirements & Solutions

15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation

16 Quality Management

16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria

17 Integrated Planning

17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters

18 Schedule Management

18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation

19 Resource Management

19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling

20 Budgeting & Cost Control

20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances

21 Risk & Issue Management

21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management

22 Change Control

22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans

10.1 Sources and Impacts of Conflict

Key Takeaways Explain This Topic AI

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.

Last updated: August 2026

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