Study guide
9.1 Stakeholder Analysis, Influence and Engagement
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
9.1 Stakeholder Analysis, Influence and Engagement
Key Takeaways Explain This Topic AI
Stakeholder analysis, influence and engagement form a chain: analysis tells you who matters and why, influence tells you how change actually happens, and engagement is the action you take.
Identification must go beyond the obvious sponsors and users to include regulators, suppliers, unions, communities, and anyone who can block adoption.
Power/interest analysis sets the intensity of engagement; attitude and influence set its style.
Influence mapping exposes people with little formal authority whose endorsement decides whether a change is adopted.
Analysis that never changes engagement behaviour is decoration — the output of the analysis is a differentiated plan, not a matrix.
Last updated: August 2026
Why stakeholder engagement matters on the APM PMQ
Stakeholder engagement and communication management sits in Area C ( People and behaviours ) as learning objective 10 . On the PMQ you must understand the relationship between stakeholder analysis, influence and engagement , and how analysis feeds an effective communication management plan . People topics carry 25–35% of exam coverage, so weak stakeholder answers cost marks across multiple question types.
A stakeholder is any individual, group, or organisation that can affect , be affected by , or perceive itself to be affected by a project’s decisions, activities, or outcomes. That definition includes supporters and opponents, formal authorities and informal influencers, and people who only believe they will be impacted. Ignoring a perceived impact does not remove the stakeholder — it usually creates resistance later.
Weak exam answers list stakeholder names. Strong answers show a chain: identify → analyse (power, interest, influence, attitude) → choose engagement strategy → act and communicate → reassess . Analysis without engagement is paperwork; engagement without analysis is random activity that overloads some people and misses the ones who can stop the project.
Exam frame: Analysis tells you who matters and how ; engagement is what you deliberately do to build the support and decisions the project needs.
Identifying stakeholders
Identification is the first step and should be systematic, not limited to the people who attend kick-off.
- Source of identification Typical stakeholders found
- Business case and benefits map Sponsor, benefits owners, operational managers who must change ways of working
- Organisation structure / OBS Functional heads supplying resources, PMO, finance, legal, HSE, IT
- Project scope and interfaces Users, customers, adjacent projects, facilities, data owners
- Contracts and supply chain Suppliers, subcontractors, landlords, framework providers
- Regulation and compliance Regulators, auditors, professional bodies, unions
- External environment Communities, media, elected officials, pressure groups, partners
- Life-cycle events New owners after transition, temporary specialists, go-live support teams
Techniques include workshops, brainstorming with the core team, interviews with the sponsor, process mapping (who touches the change), and reviewing similar past projects. Record results in a living stakeholder register (or equivalent): identity, role, interests, expectations, power/influence, attitude, engagement strategy, and relationship owner.
Revisit identification when scope, organisation, suppliers, or life-cycle stage changes. A stakeholder who was low interest at concept may become high interest at cutover. Linear projects often re-map at each stage; iterative work re-maps as product increments expose new user groups.
Scenario A — incomplete identification
A hospital introduces a new outpatient booking system. The project team engages clinicians and IT but skips call-centre staff who handle exceptions. At go-live, call volumes spike and the benefits case for reduced missed appointments collapses. The missing stakeholders were always affected; analysis failed at identification, so engagement and training never reached them.
Stakeholder analysis: power, interest, influence and more
Stakeholder analysis assesses attributes that matter for engagement design. Common dimensions:
Dimension Question Why it matters
Power / authority Can they decide, fund, block, or mandate? High power requires satisfaction or close management
Interest How much do they care about the outcome? High interest needs information and involvement
Influence Can they shape others’ opinions even without formal power? Informal influencers can make or break adoption
Impact How much does the project affect them? High impact often creates high interest and change risk
Attitude / support Supportive, neutral, resistant, or unaware? Drives whether you educate, involve, negotiate, or escalate
Urgency / immediacy Do they need action now? Affects sequencing of engagement
Do not confuse power with interest , or power with influence . A regulator may have high power and moderate day-to-day interest until a compliance date approaches. A respected senior nurse may have moderate formal power but high influence over peer adoption. Analysis must capture both formal and informal reality.
Power/interest (influence) grid
The classic power/interest grid (also framed as power/influence or interest/influence depending on organisational templates) places stakeholders so engagement effort is proportionate.
Quadrant Profile Typical engagement strategy
High power, high interest Sponsor, key customer, major regulator on a critical path Manage closely — frequent two-way engagement, involve in key decisions, protect relationship, report exceptions early
High power, low interest Senior executives, corporate functions with sign-off rights but limited day-to-day curiosity Keep satisfied — concise, decision-ready information; do not overload with detail; secure approvals without boring them into disengagement
Low power, high interest End users, local community groups, operational teams living with the change Keep informed — regular updates, listening channels, involvement in design/testing where possible; they can become powerful through networks if ignored
Low power, low interest Distant observers with little stake Monitor — light touch; reassess if their position changes
These labels are starting points, not rigid boxes. A “keep satisfied” stakeholder who suddenly faces a major cutover risk may jump to “manage closely.” A “keep informed” user community that organises public opposition may gain effective power overnight.
Desired vs current engagement
Many projects also compare current engagement level with desired level (for example: unaware → resistant → neutral → supportive → leading). The gap drives the engagement plan: a resistant high-power stakeholder needs a different mix of listening, negotiation, and sponsor escalation than an unaware user group that mainly needs education.
- Current → desired gap Typical response
- Unaware → supportive Education, demos, clear WIIFM (what’s in it for me), simple channels
Resistant → neutral/supportive Understand interests, address losses, involve in design of mitigations, use trusted intermediaries
- Neutral → leading Give meaningful roles, celebrate contribution, link their goals to project success
- Supportive but low power → sustained support Keep informed and valued so they remain advocates
- Influence mapping
Influence mapping goes beyond a single grid. It charts who influences whom — networks of advice, trust, and decision dependency. Useful when formal charts hide real politics.
How to use an influence map:
Plot key stakeholders and mark formal reporting lines lightly.
Add arrows for actual influence (who the sponsor listens to; who staff follow; who the press quotes).
Identify blockers , champions , and bridges (people who can connect the project to a resistant group).
Sequence engagement: brief a trusted influencer before a mass announcement; ask the sponsor to open doors the project manager cannot.
Watch coalitions — several medium-power stakeholders can combine into high effective power.
Scenario B — influence over formal power
A council digital project has a supportive sponsor but a resistant service manager with strong informal authority among team leaders. Power/interest alone shows the service manager as medium power, high interest. Influence mapping shows team leaders will not adopt the new process without that manager’s endorsement. Engagement strategy: manage the service manager closely; involve them in design choices they can shape; ask the sponsor for a joint session; do not rely only on all-staff emails.
Relationship: analysis → influence → engagement
This relationship is the heart of LO10(a).
- Step Output Engagement implication
- Identify Stakeholder list / register Nobody engaged if not known
- Analyse Power, interest, influence, attitude, impact Effort and style become proportionate and targeted
- Assess influence paths Influence map, coalitions, bridges Choose who to engage first and through whom
Plan engagement Strategy per stakeholder/group; desired levels Meetings, workshops, governance seats, co-design, escalation routes
- Engage Two-way activity, not one-way broadcast Build trust, surface issues, secure decisions and adoption
- Review Updated attitudes and risks Reclassify and change tactics when context shifts
Engagement means deliberately building and maintaining relationships so stakeholders contribute information, decisions, resources, and acceptance. It is broader than communication (messages and channels), though communication is a primary tool. Engagement can include co-design workshops, user representation on boards, site visits, pilot participation, negotiation of impacts, and visible sponsor championship.
Principles for effective engagement strategies:
Match intensity to power and impact — scarce project management time goes first to high-power and high-impact relationships.
Prefer early engagement — influence on requirements and design is cheaper than late resistance at go-live.
Be two-way — listening is as important as telling; analysis of concerns feeds risk, requirements, and benefits plans.
Assign relationship owners — every key stakeholder needs a named person (PM, sponsor, business change lead) accountable for the relationship.
Align with governance — high-power stakeholders often need formal board/steering routes as well as informal contact.
Record sensitive judgements carefully — attitude ratings can be political; control access and keep language professional.
Link to success criteria — engagement exists to protect objectives, benefits, and controlled delivery, not to run endless consultations without decisions.
Engagement tactics by situation
- Situation Engagement emphasis
- High power supporter Maintain; use as champion; protect from surprises
High power resistor Deep listening; interest-based negotiation; options analysis; sponsor-to-sponsor dialogue; escalate residual threat
- High interest users Involvement in requirements, testing, training design; feedback loops
- Low interest, high power Short exception-based briefings; clear decisions requested; no noise
- External community / media Transparent milestones, single spokesperson, factual updates, issue management
Supplier stakeholders Contractual forums plus collaborative problem-solving; do not rely on contract alone for behaviour
Scenario C — analysis drives engagement choice
A manufacturing ERP upgrade classifies the CFO as high power, currently low interest (keep satisfied) and shop-floor supervisors as low power, high interest (keep informed). Mid-project, inventory cutover risk threatens month-end close. Analysis is updated: CFO interest spikes → move to manage closely with a focused risk briefing and decision options. Supervisors remain high interest; engagement adds floor-walkers and a pilot line so they can influence practical procedures. The project does not send both groups the same 40-page status pack — that would satisfy neither.
- Common traps on PMQ answers
- Treating stakeholder management as “send more emails.”
Engaging only supporters and hoping resistors disappear.
Freezing the register after initiation.
Confusing the grid with governance: analysis informs who sits where; it does not replace the sponsor or board.
Ignoring informal influence and community perception.
Over-engaging low-power, low-interest parties until the team has no time for critical relationships.
Answer pattern for long-response questions
When a scenario involves support, resistance, or politics:
Identify the stakeholders and what they care about.
Analyse power, interest, influence, and attitude (use a grid if helpful).
State the engagement strategy per key party (manage closely / keep satisfied / keep informed / monitor, plus specific actions).
Explain influence paths (who must be won first; role of sponsor).
Link actions to project success (decisions, resources, adoption, risk reduction).
Note review — how you will know engagement is working and when to reclassify.
That chain demonstrates the LO10 relationship between stakeholder analysis, influence, and engagement — the foundation for the communication plan covered in the next section.