Project Stakeholder Management (PMBOK Knowledge Area 13) is the collection of four processes that identify people, groups or organisations that could affect or be affected by the project, analyse their expectations and potential impact, and develop strategies to effectively engage them in project decisions and execution. The four processes are: Identify Stakeholders (cataloguing all who have an interest in the project), Plan Stakeholder Engagement (developing strategies to engage each stakeholder appropriately), Manage Stakeholder Engagement (communicating and working with stakeholders to meet their needs and address issues), and Monitor Stakeholder Engagement (monitoring stakeholder relationships and adjusting strategies). The central insight is that stakeholder engagement is not the same as communication — communication delivers information; engagement influences attitudes and behaviour. The most important stakeholder management work happens in informal conversations, relationship building and political navigation, not in formal status reports.
Stakeholder management is the knowledge area that most directly determines whether a project succeeds or fails in the eyes of the people who matter. A project that delivers every technical requirement on time and within budget can still be perceived as a failure if key stakeholders were not engaged, their concerns were ignored, or the delivered product does not meet their unstated but real expectations. Conversely, a project that faces significant challenges can succeed if stakeholders are engaged, trust has been built, and the PM navigates political complexity with skill.
PMBOK added Stakeholder Management as a standalone knowledge area in the 5th edition, recognising that the previous treatment of stakeholders as primarily a communications management concern was insufficient. Stakeholder management is a distinct discipline — it requires understanding of human psychology, organisational politics, influence and persuasion, and the ability to navigate competing interests across groups with different power, concern and investment in the project's outcome.
This guide covers all four PMBOK processes with full ITO breakdowns, the Stakeholder Register, the Stakeholder Engagement Assessment Matrix, the five engagement levels, the power/interest grid, the salience model, and how stakeholder management operates in Agile, waterfall and hybrid environments.
Foundational Concepts
Who Is a Stakeholder? — Broader Than Most PMs Think
A stakeholder is any individual, group or organisation that may affect, be affected by, or perceive itself to be affected by a decision, activity or outcome of a project. This definition is deliberately broad — it includes not just the obvious project participants (sponsor, team members, customers) but anyone whose interests intersect with the project in any way.
The scope of the stakeholder universe surprises many PMs. Internal stakeholders include the project sponsor, project board members, team members, functional managers whose resources are committed to the project, the PMO, and other project managers affected by shared resources or schedule dependencies. External stakeholders include customers and users, suppliers and contractors, regulators and government bodies, local communities and the public (for infrastructure and construction projects), media (for high-profile projects), and industry bodies. Even competitors can be stakeholders if a project's outcome affects market conditions or regulatory frameworks in ways that affect them.
💡
The critical distinction: engagement vs communication. Many PMs conflate stakeholder management with communications management. They are related but fundamentally different. Communication delivers information — it ensures stakeholders receive the right data at the right time. Engagement influences attitudes and behaviour — it creates the understanding, buy-in, and active support that enable project success. A stakeholder who receives all the right communications but remains resistant to the project is a communications success and an engagement failure. The most important stakeholder management work happens informally — in corridor conversations, one-to-one meetings, relationship-building over time — not in formal reports.
Stakeholder Identification: A Continuous Activity
Stakeholder identification is not a one-time planning activity. New stakeholders emerge throughout the project lifecycle — as scope evolves, new organisational connections emerge, and the project's visibility grows. A regulatory body that becomes relevant when scope is extended, a community group that mobilises when construction activity begins, or an internal department that realises the project will affect their processes — all are stakeholders who may not have been visible at project initiation. The PM must actively and continuously scan for new stakeholders throughout the project.
The Four Processes
Project Stakeholder Management — The 4 PMBOK Processes
13.1
Identify Stakeholders
Initiating (and iteratively throughout) · Identifies all people and organisations impacted by the project and analyses their interests, involvement and potential impact
+
Identify Stakeholders is the process of regularly identifying project stakeholders and analysing their interests, involvement, interdependencies, influence and potential impact on project success. It runs in the Initiating Process Group but is explicitly iterative — it must be repeated at the start of each phase and whenever significant changes occur. Its primary output is the Stakeholder Register.
The Stakeholder Register records: identification information (name, role, organisation, contact details), assessment information (major requirements, main expectations, potential influence, phase of greatest interest), and stakeholder classification (internal/external, supporter/neutral/resistor, engagement level). This document is the foundation of all subsequent stakeholder management activities.
Key techniques for stakeholder identification:
Expert judgement: Drawing on the PM's and team's experience of who typically has a stake in projects of this type, combined with subject matter expertise about the project's technical and organisational context.
Data gathering — questionnaires and surveys: Used to systematically gather stakeholder information from identified parties and to surface additional stakeholders they may identify.
Brainstorming: Group technique to generate a comprehensive initial list of potential stakeholders — covering all organisational units, external parties and interest groups.
Stakeholder analysis models: Systematic frameworks for classifying stakeholders by their attributes — power, interest, influence, impact, urgency. The Power/Interest Grid, the Salience Model and the Stakeholder Cube are all analysis models used to organise stakeholder data and inform engagement strategy.
Meetings: Discussions with the sponsor, key team members, and initial stakeholders to identify further stakeholders and gather initial assessment information.
Inputs
Project Charter
Business Documents (Business case)
Project Management Plan (Communications, Stakeholder Engagement Plans)
Planning Process Group · Develops approaches to involve stakeholders based on their needs, expectations, interests and potential impact
+
Plan Stakeholder Engagement is the process of developing approaches to involve stakeholders in the project appropriately, based on an analysis of their needs, expectations, interests and potential impact on the project. Its primary output is the Stakeholder Engagement Plan — a component of the Project Management Plan that defines specific strategies for moving each stakeholder from their current engagement level to the desired engagement level.
The most important analytical tool in this process is the Stakeholder Engagement Assessment Matrix (see the detailed explanation below). This matrix maps each stakeholder's current engagement level against the desired engagement level, making the engagement gap visible and actionable. Where current and desired levels differ, engagement strategies must be developed to close the gap.
The Stakeholder Engagement Plan defines: the specific strategies for engaging each stakeholder group, the communication approaches that will support engagement, the key messages to be communicated, the timing and frequency of engagement activities, the relationships and interdependencies between stakeholders, and the approach to managing resistance.
Assumption and constraint analysis: This process also examines assumptions about stakeholder engagement (what we believe is true about stakeholders' interests and attitudes) and constraints (limitations on how stakeholders can be engaged — time, geography, organisational norms, legal requirements). Incorrect assumptions about stakeholder engagement are a common source of engagement failure.
Inputs
Project Charter
Project Management Plan (Communications, Resource, Risk, Scope, Schedule Management Plans)
Data analysis (assumptions and constraints analysis, root cause analysis)
Decision making (prioritisation / ranking)
Data representation (mind mapping, stakeholder engagement assessment matrix)
Meetings
Outputs
Stakeholder Engagement Plan
13.3
Manage Stakeholder Engagement
Executing Process Group · Communicates and works with stakeholders to meet their needs, address issues and foster appropriate involvement
+
Manage Stakeholder Engagement is the executing process that involves communicating and working with stakeholders to meet their needs and expectations, address issues as they occur, and foster appropriate stakeholder involvement in project activities and decisions. It is the process of putting the Stakeholder Engagement Plan into action — the daily, weekly and ongoing work of building relationships, managing expectations, resolving concerns, and navigating political complexity.
This process requires the PM to use the full range of interpersonal skills: active listening (genuinely attending to stakeholder concerns rather than waiting for a turn to speak), influencing (persuading stakeholders to take actions or adopt positions that serve the project without formal authority), negotiation (finding mutually acceptable positions when stakeholder interests conflict with project requirements), and political awareness (understanding the organisational dynamics, power relationships and informal influence networks that shape stakeholder behaviour).
Managing resistance: Stakeholder resistance is one of the most common and consequential challenges in project delivery. Resistance rarely disappears by being ignored — it typically grows. Effective resistance management begins with understanding the root cause: Is the stakeholder resistant because of fear (job loss, change to working practices)? A genuine technical concern? A political position? Historical bad experiences with similar projects? Different root causes require different responses — and a response that addresses the wrong root cause will not resolve the resistance.
The Issue Log is the primary management tool for tracking unresolved stakeholder concerns, disagreements and problems that require escalation or decision. Issues that cannot be resolved at the PM level must be escalated to the project sponsor or steering group through defined escalation procedures.
Inputs
Project Management Plan (Communications, Risk, Stakeholder Engagement Plans)
Monitoring & Controlling Process Group · Monitors stakeholder relationships and tailors strategies for engaging stakeholders through modification of plans and approaches
+
Monitor Stakeholder Engagement is the monitoring and controlling process that assesses whether stakeholder engagement strategies are working, tracks changes in stakeholder attitudes and engagement levels, and updates engagement strategies when the current approach is not achieving the desired stakeholder behaviour. It is fundamentally an assessment and adaptation process — asking continuously "are our engagement strategies working, and what needs to change?"
The process uses the Stakeholder Engagement Assessment Matrix to compare current engagement levels against desired levels. When the gap between current and desired engagement is increasing (a stakeholder who was previously Supportive is moving toward Neutral), the PM must investigate why and adjust the engagement strategy accordingly. Stakeholder engagement is dynamic — attitudes change as the project progresses, as organisational context shifts, and as the project's implications become clearer.
Data analysis techniques:
Alternatives analysis: Evaluating different engagement strategies when current approaches are not achieving desired engagement levels.
Root cause analysis: Investigating why a stakeholder's engagement level is declining or why a particular engagement strategy is not working.
Stakeholder engagement assessment matrix: Comparing current vs desired engagement levels to identify where strategies need to be intensified or revised.
The outputs of Monitor Stakeholder Engagement include change requests (to update the Stakeholder Engagement Plan or Communications Management Plan), updated project documents (particularly the Stakeholder Register and Issue Log), and work performance information documenting the current state of stakeholder engagement across the project.
Inputs
Project Management Plan (Resource, Communications, Stakeholder Engagement Plans)
PMBOK defines five levels of stakeholder engagement that represent the spectrum from active opposition to active championship. Each stakeholder's current level is assessed and compared to their desired level. The engagement gap — the difference between current and desired — drives the engagement strategy for that stakeholder.
Stakeholder Engagement Levels — From Resistant to Leading
Unaware
Unaware
The stakeholder is unaware of the project and its potential impacts — positive or negative. They have no engagement because they do not know the project exists or that it is relevant to them. Unaware stakeholders may be newly identified during the project lifecycle, or stakeholders who have been kept out of the communication loop.
Raise awareness through targeted communication about the project's existence and relevance to their interests. Introductory briefings, stakeholder mapping communications.
Resistant
Resistant
The stakeholder is aware of the project and its potential impacts but is actively opposed to or resistant to the project or its outcomes. Resistance may be based on genuine concerns about impact, political opposition, conflicting interests, fear of change, or historical bad experiences. This is the most challenging engagement level — and the most dangerous if unaddressed.
Understand the root cause of resistance before attempting to address it. Listen actively. Acknowledge legitimate concerns. Find ways to address their specific interests. Avoid confrontation — seek common ground. Involve resistant stakeholders in solution design where possible.
Neutral
Neutral
The stakeholder is aware of the project but neither supports nor opposes it. They may be indifferent, waiting to see how the project develops before forming a view, or simply not engaged enough to have a position. Neutral stakeholders are at risk of becoming resistant if the project affects their interests in ways they did not anticipate — or potential supporters if their interests can be aligned with the project's objectives.
Identify what would move them to Supportive. Connect the project's objectives to their professional interests. Provide relevant information that demonstrates value to them. Address potential concerns proactively before they become resistance triggers.
Supportive
Supportive
The stakeholder is aware of the project and its potential impacts and actively supports the project and the project management team. They provide assistance when needed, facilitate the team's access to resources and information, and generally enable rather than impede project progress. This is the target engagement level for most stakeholders.
Maintain and nurture the relationship. Keep them informed and involved. Recognise and acknowledge their support. Protect them from unnecessary administrative burden. Ensure they remain informed of project progress and developments that affect them.
Leading
Leading
The stakeholder is actively engaged in ensuring the project succeeds — they champion the project to others, use their influence to remove obstacles, make resources available proactively, and advocate for the project at senior levels. Leading stakeholders are the most valuable allies a PM can have. The project sponsor ideally operates at this level. Not all stakeholders need to be at Leading — it is the desired level only for those whose active championship creates the most value.
Engage deeply and frequently. Involve them in decisions. Give them visibility into project challenges so they can help remove obstacles. Leverage their influence appropriately on behalf of the project. Respect their time and maintain the relationship genuinely, not just instrumentally.
Engagement Assessment Matrix
The Stakeholder Engagement Assessment Matrix
The Stakeholder Engagement Assessment Matrix maps each stakeholder's current (C) engagement level against their desired (D) engagement level. Where C and D differ, an engagement strategy must be developed to close the gap. Where C and D are the same, the current engagement approach is working and should be maintained.
Stakeholder
Unaware
Resistant
Neutral
Supportive
Leading
Project Sponsor (Dir. Operations)
C/D
IT Director
C
D
Finance Manager
C
D
End User Community Lead
C
D
External Regulator
C/D
Procurement Manager
C
D
C = Current level · D = Desired level · C/D = Current and desired are aligned
Reading the matrix: The IT Director is currently Resistant but needs to be Supportive — a significant engagement gap requiring active investigation and a specific engagement strategy to address their resistance. The Finance Manager is Neutral but needs to be Supportive — a one-step gap that requires connecting the project's benefits to their financial priorities. The Procurement Manager is Unaware and needs to be Supportive — an urgent communication gap that must be addressed before procurement activities begin. The External Regulator is correctly maintained at Neutral — neither resistance nor active support is desired or appropriate for this stakeholder type.
Analysis Models
Stakeholder Analysis Models
The Power/Interest Grid
The Power/Interest Grid (also called the Power/Interest Matrix) is the most widely used stakeholder classification tool. It maps stakeholders on two dimensions — their level of power (authority to affect project decisions or outcomes) and their level of interest (the degree to which they are concerned with the project's outcomes) — producing four quadrants that suggest different engagement strategies.
Power / Interest Grid — Stakeholder Engagement Strategy by Quadrant
Power ↕
Low Interest
High Interest
High Power
Keep Satisfied
Meet their needs proactively
High power, low interest. Can significantly affect the project but do not currently engage closely. Must be managed carefully — their disengagement can shift to blockage quickly if dissatisfied.
Manage Closely
Maximum effort and engagement
High power, high interest. The most critical stakeholders. Require frequent, personal engagement. Must be involved in key decisions. Their support enables; their opposition can derail.
Low Power
Monitor
Minimal communication effort
Low power, low interest. Least critical in the short term. Keep informed with periodic, minimal communications. Monitor for changes in power or interest that would move them to a different quadrant.
Keep Informed
Regular, targeted updates
Low power, high interest. Interested but limited ability to affect the project directly. Keep well-informed through regular communication. Can become influential advocates if well-managed, particularly in large change programmes.
The Salience Model — Three Dimensions of Stakeholder Priority
The Salience Model (Mitchell, Agle and Wood, 1997) classifies stakeholders across three dimensions — power, legitimacy and urgency — to determine their salience (the degree to which they command managerial attention). Stakeholders with all three attributes are the most salient and demand immediate attention.
⚡Power
The ability to impose one's will on others — whether through formal authority, resource control, technical expertise, political influence, or legal rights. Powerful stakeholders can enforce their preferences regardless of legitimacy or urgency.
📜Legitimacy
The perception that a stakeholder's claims or actions are appropriate, proper or desirable within the context of the project. A stakeholder with a legitimate claim has a recognised right to be engaged — whether through legal standing, contractual relationship, or accepted social norms.
⏰Urgency
The degree to which a stakeholder's claims call for immediate attention — time-sensitive or critical to the stakeholder. Urgency without power or legitimacy creates pressure but not necessarily influence; urgency combined with either power or legitimacy demands rapid response.
The Salience Model identifies seven types of stakeholders based on which combination of attributes they possess: Dormant (power only), Discretionary (legitimacy only), Demanding (urgency only), Dominant (power + legitimacy), Dangerous (power + urgency), Dependent (legitimacy + urgency) and Definitive (power + legitimacy + urgency — the highest priority). A stakeholder with all three attributes demands immediate and sustained management attention.
The Stakeholder Register
The Stakeholder Register — What It Contains
The Stakeholder Register is the primary stakeholder management document — progressively elaborated from initial identification through project close. Unlike many project documents that are produced once and referenced, the Stakeholder Register must be actively maintained throughout the project — as stakeholders' roles, interests and engagement levels change, the register must reflect current reality.
Stakeholder
Role
Power
Interest
Attitude
Current Engagement
Desired Engagement
Key Concerns
Sarah Chen
Project Sponsor (Dir. Operations)
High
High
Supportive
Supportive
Leading
Delivery on schedule; board visibility
James Abbott
IT Director
High
Medium
Resistant
Resistant
Supportive
Resource impact on BAU IT; data security
Finance Team
Budget Stakeholder
Medium
High
Neutral
Neutral
Supportive
Cost controls; budget reporting accuracy
End Users
Primary Beneficiary
Medium
High
Supportive
Supportive
Leading
Usability; training; transition support
Regulator
Compliance Authority
High
Medium
Neutral
Neutral
Neutral
Regulatory compliance; timely submissions
Interrelation to Other Knowledge Areas
How Stakeholder Management Connects to Every Other Knowledge Area
🔗KA01 — Integration Management
The Stakeholder Engagement Plan is a subsidiary component of the Project Management Plan, integrated under KA01. Stakeholder buy-in is essential for project integration decisions — change requests, exception reports and scope decisions all require sponsor and project board engagement. The PM's effectiveness as an integrator depends heavily on their stakeholder relationships — a PM who has built trust with the sponsor can navigate complex change decisions far more effectively than one who has an adversarial relationship.
📐KA02 — Scope Management
Requirements gathering (Collect Requirements) is a stakeholder engagement activity. The quality of requirements depends on the quality of stakeholder engagement — stakeholders who are not genuinely engaged provide surface-level requirements that miss underlying needs. Validate Scope (customer acceptance of deliverables) is the culmination of stakeholder engagement throughout delivery — formal acceptance is more likely when stakeholders have been engaged throughout the process rather than presented with a completed product for sign-off. Scope changes that affect stakeholders must be communicated and re-engaged proactively.
📅KA03 — Schedule Management
Key stakeholders (particularly the sponsor and steering group) must be engaged when schedule variances exceed defined thresholds. Schedule communication to different stakeholders requires different formats — a detailed Gantt for the PM, a milestone summary for the steering group, a sprint board for the Agile team. Stakeholder schedule expectations must be understood and managed from the start — a sponsor whose mental model of the project timeline is significantly different from the baseline will become resistant when the planned completion date is communicated formally.
💰KA04 — Cost Management
Financial stakeholders (sponsor, finance director, CFO) have specific cost reporting needs that must be understood and planned for. Cost overrun communications are among the most politically sensitive stakeholder interactions a PM faces — the manner, timing and framing of cost variance reporting directly affects stakeholder relationships and the PM's personal credibility. Budget approval, reserve release and change order authorisation all require stakeholder engagement at appropriate authority levels.
⭐KA05 — Quality Management
Quality acceptance criteria must be agreed with key stakeholders — particularly the customer and users who will determine whether the delivered product meets their expectations. Unstated quality expectations are among the most common causes of stakeholder dissatisfaction — when stakeholders accept a deliverable formally but are privately unhappy with aspects of it that were never formally specified, the project has a quality issue that quality management failed to capture. Stakeholder engagement in defining acceptance criteria prevents this.
👥KA06 — Resource Management
Team members are stakeholders. Functional managers who control resource allocation are critical stakeholders whose engagement directly affects the project's ability to acquire and retain the team. In matrix organisations, the PM must manage functional managers as stakeholders with their own interests, concerns and authority — not simply as resource providers. The interpersonal and leadership skills from KA06 (emotional intelligence, conflict management, influence) are the same skills required for effective stakeholder management in KA13.
📣KA07 — Communications Management
Communications Management and Stakeholder Management are the most closely interrelated knowledge areas — they use some of the same tools and outputs. The Stakeholder Register drives the Communications Management Plan — stakeholder information needs (from KA13) determine what communications are planned (in KA07). The distinction: KA13 focuses on understanding and influencing stakeholder attitudes and behaviour; KA07 focuses on delivering the right information to the right people. Effective communication supports engagement, but is not the same as engagement.
⚠️KA08 — Risk Management
Stakeholder behaviour is a major source of project risk. Sponsor withdrawal, key stakeholder resistance to change, political opposition, and conflicting stakeholder priorities are all risks in the Risk Register. The Stakeholder Register is an input to risk identification — each stakeholder's interests and influence level suggests potential risk scenarios. Risk communication must be calibrated to stakeholder risk tolerance and engagement level — a stakeholder in the Resistant quadrant who receives an alarming risk report may escalate their resistance rather than helping manage the risk.
🛒KA09 — Procurement Management
Sellers are stakeholders — they have interests, concerns and influence that must be managed alongside internal stakeholders. Supplier relationship management is a stakeholder management activity. During Conduct Procurements, potential suppliers must be managed as stakeholders with their own engagement needs. Post-award, key supplier contacts should be in the Stakeholder Register at the Supportive level — a supplier who is Neutral or Resistant to the project's success poses delivery risk that is partly a stakeholder management problem, not just a contract management problem.
Agile and Hybrid Approaches
Stakeholder Management in Agile, Waterfall and Hybrid Environments
🏛️ Stakeholder Management in Waterfall
Traditional waterfall stakeholder management follows the four-process PMBOK model with formal governance structures:
Comprehensive stakeholder identification at initiation, revisited at each phase
Formal Stakeholder Register maintained throughout lifecycle
Stakeholder Engagement Plan developed during planning
Structured stakeholder communication through defined channels (status reports, steering group meetings, stakeholder briefings)
Formal stage gate reviews as primary structured stakeholder engagement points
Issue log for tracking unresolved stakeholder concerns
Escalation procedures defined and exercised through governance framework
Formal change management (business change management) for stakeholders affected by project outcomes
Strength: Structured governance with clear accountability and formal engagement touchpoints. Challenge: Periodic formal engagement can miss the continuous relationship management that prevents issues from escalating.
🔄 Stakeholder Management in Agile
Agile embeds stakeholder engagement directly into the delivery rhythm rather than managing it as a separate discipline:
Product Owner: The primary stakeholder liaison — translating business stakeholder needs into backlog priorities, representing the customer in sprint planning and reviews, and managing stakeholder expectations about scope and delivery
Sprint reviews: Structured stakeholder engagement every sprint — working software is demonstrated, feedback is collected, and the backlog is adjusted. Real working product creates genuine engagement conversations, not theoretical requirement discussions
Daily standups: Transparency about what is being worked on — removes information asymmetry that creates stakeholder anxiety
Collaborative planning: Stakeholders involved in backlog prioritisation — their priorities directly shape what the team works on next
Continuous stakeholder feedback integrated into each sprint cycle
Co-location with key stakeholders (when feasible) to enable continuous informal engagement
Strength: Continuous, high-quality stakeholder engagement built into the cadence. Challenge: Managing multiple divergent stakeholder interests within a single product backlog requires skilled facilitation.
Hybrid Stakeholder Management
Hybrid environments maintain formal governance-level stakeholder management (steering groups, exception reports, formal change communications) while using Agile practices to create more continuous and direct stakeholder engagement at the delivery level. The Product Owner bridges the governance stakeholders (sponsor, steering group) and the delivery team, translating strategic direction into sprint priorities and translating delivery progress into governance reporting. This dual accountability is one of the most demanding aspects of hybrid stakeholder management.
Exam Tips
Stakeholder Management — 7 Exam Tips for PMP and APM PMQ
1
Stakeholder identification is an initiating process — but it is iterative throughout the project. The exam tests whether candidates understand that Identify Stakeholders happens first in the Initiating Process Group but must be repeated at the start of each phase and whenever significant changes occur. New stakeholders can emerge at any point — treating identification as a one-time planning activity is a common mistake in both practice and exam scenarios.
2
Engagement ≠ Communication — this distinction is frequently tested. Communication delivers information. Engagement influences attitudes and behaviour. A stakeholder who receives all the right communications but remains Resistant is a communications success and an engagement failure. The exam tests whether candidates understand that stakeholder management requires active relationship management, not just information distribution.
3
Know the five engagement levels in order: Unaware → Resistant → Neutral → Supportive → Leading. The exam frequently presents scenarios where a stakeholder is at one level and asks what the PM should do to move them to the desired level. Understand what characterises each level and what engagement strategies are appropriate for moving between them. The gap between current and desired drives the engagement strategy.
4
Understand the Power/Interest Grid quadrants and their strategies. High Power / High Interest = Manage Closely (maximum engagement). High Power / Low Interest = Keep Satisfied (proactive management). Low Power / High Interest = Keep Informed (regular communication). Low Power / Low Interest = Monitor (minimal effort). The exam describes a stakeholder profile and asks what engagement strategy to apply — map it to the correct quadrant.
5
Address resistance by understanding its root cause — not by increasing communication volume. A resistant stakeholder who receives more frequent status updates will not become less resistant — and may become more so. The correct approach to resistance is active listening, root cause investigation, and a response that addresses the specific reason for resistance. Sending more reports is a communications management response; managing resistance is a stakeholder management challenge.
6
Sellers and team members are stakeholders. The PMP exam takes a broad view of the stakeholder universe. When a question describes a situation involving a difficult supplier, a disengaged team member, or a resistant functional manager, it may be testing stakeholder management knowledge — not just procurement or resource management. Anyone who "may affect, be affected by, or perceive themselves to be affected by" the project is a stakeholder.
7
The Stakeholder Register is confidential — its level of sensitivity must be managed carefully. The Stakeholder Register contains assessments of stakeholders' attitudes, power and interests — information that could damage relationships if shared inappropriately. The exam may test whether candidates understand that the Stakeholder Register is a planning tool for the PM and project team, not a document to be distributed to all stakeholders. Different sections may have different distribution restrictions.
Apply This Knowledge Area in Your PMP or APM PMQ Exam
Stakeholder management — including the four processes, five engagement levels, Power/Interest Grid and Stakeholder Engagement Assessment Matrix — is examined in both the PMP and APM PMQ. The APM PMQ tests stakeholder engagement as a core leadership and PM competency across multiple learning outcomes.
The four PMBOK processes in Project Stakeholder Management (Knowledge Area 13) are: (1) Identify Stakeholders (Initiating Process Group, and iteratively throughout) — identifying all individuals, groups and organisations that may affect or be affected by the project, and analysing their interests, involvement, influence and potential impact. Primary output: Stakeholder Register. (2) Plan Stakeholder Engagement (Planning Process Group) — developing strategies and approaches to involve stakeholders appropriately based on their needs, expectations and potential impact. Primary output: Stakeholder Engagement Plan. (3) Manage Stakeholder Engagement (Executing Process Group) — communicating and working with stakeholders to meet their needs, address issues as they occur, and foster appropriate involvement in project decisions and execution. (4) Monitor Stakeholder Engagement (Monitoring and Controlling Process Group) — monitoring stakeholder relationships, evaluating engagement effectiveness, and adjusting strategies when current engagement is not achieving desired levels.
The five PMBOK stakeholder engagement levels, from lowest to highest engagement, are: Unaware — the stakeholder does not know about the project or its potential impacts; Resistant — the stakeholder is aware of the project but actively opposes it or its outcomes; Neutral — the stakeholder is aware of the project but neither supports nor opposes it; Supportive — the stakeholder is aware of the project and actively supports it and the project team; Leading — the stakeholder is actively engaged in ensuring the project succeeds, championing it to others and using their influence proactively on the project's behalf. These levels are used in the Stakeholder Engagement Assessment Matrix, where each stakeholder's current level is mapped against their desired level to identify the engagement gap and the strategies needed to close it.
The Stakeholder Engagement Assessment Matrix is a tool used in Plan Stakeholder Engagement and Monitor Stakeholder Engagement to compare each stakeholder's current engagement level against their desired engagement level. The matrix has rows for each stakeholder and columns for each of the five engagement levels (Unaware, Resistant, Neutral, Supportive, Leading). Each stakeholder's current engagement level is marked with a C and their desired engagement level with a D. Where C and D are the same, the engagement strategy is working and should be maintained. Where C and D differ, an engagement strategy must be developed to move the stakeholder from their current to their desired level. For example, an IT Director marked as C=Resistant and D=Supportive has a two-level engagement gap requiring active investigation of resistance root causes and a targeted engagement strategy to address them.
The Power/Interest Grid (also called the Power/Interest Matrix) is a stakeholder classification tool that maps stakeholders on two dimensions — their power (ability to affect project decisions and outcomes) and their interest (degree of concern with the project's outcomes) — producing four quadrants with different recommended engagement strategies. High Power / High Interest stakeholders should be Managed Closely — they require maximum engagement effort, frequent personal communication, and involvement in key decisions. High Power / Low Interest stakeholders should be Kept Satisfied — they must be managed carefully as their disengagement can shift to active blocking quickly. Low Power / High Interest stakeholders should be Kept Informed — regular, targeted communication acknowledges their interest without over-investing engagement effort. Low Power / Low Interest stakeholders should be Monitored — minimal communication effort, watching for changes in power or interest that would move them to a different quadrant.
Stakeholder management and communications management are closely related but fundamentally different disciplines. Communications management focuses on information delivery — ensuring the right information reaches the right people, in the right format, at the right time, through the right channel. It is primarily a logistics and planning discipline that creates and manages the flow of information. Stakeholder management focuses on relationship management and influence — understanding stakeholder interests, concerns and attitudes, and actively working to engage them in ways that create understanding, trust and support for the project. A stakeholder who receives all the right communications but remains resistant to the project is a communications success and a stakeholder management failure. The most impactful stakeholder management work happens informally — in one-to-one conversations, relationship-building activities and political navigation — not in formal status reports. Communications management supports stakeholder management but cannot substitute for it.
Agile embeds stakeholder engagement directly into the delivery rhythm rather than managing it as a separate periodic discipline. The Product Owner serves as the primary stakeholder liaison — maintaining the product backlog as a reflection of prioritised stakeholder needs, representing customer and business stakeholder interests in sprint planning, and demonstrating working software at sprint reviews. Sprint reviews are the primary structured stakeholder engagement event — every sprint cycle, working software is demonstrated to stakeholders and their feedback is collected and incorporated into the next sprint's backlog. This creates a continuous, high-quality feedback loop that replaces the periodic milestone-based engagement of traditional waterfall projects. Stakeholder priorities are expressed through backlog prioritisation rather than formal requirement sign-off documents. The result is stakeholder engagement that is more frequent, more interactive, and more closely connected to actual delivery progress — but which requires skilled facilitation to manage competing stakeholder priorities within a single product backlog.