PMP Stakeholder Management: Identify, Plan & Engage

When I first sat down to map out my PMP study plan, I assumed stakeholder management would be the easy domain. After all, I had been working with stakeholders for over a decade, running steering committees, handling difficult sponsors, and negotiating scope with end users. How hard could it be to answer exam questions about something I did every single day? It turns out, quite hard. The PMP exam tests stakeholder management with a precision that forced me to unlearn a few habits and recognise that the way I had been engaging stakeholders informally was not always aligned with how PMI expects the work to be done.

In this guide I want to walk you through everything I learnt about PMP stakeholder management, from the four processes through to the engagement assessment matrix, the salience model, and the kinds of situational questions that show up on exam day. I will also share the templates I built for my own projects, the stakeholder register format that finally clicked for me, and the strategies I now use when a senior executive turns from supportive to resistant overnight.

By the end of this article, you will have a working knowledge of every tool, technique, and behaviour the exam expects, plus 10 practice questions to test yourself before you walk into the testing centre.

Until the fifth edition of the PMBOK Guide, stakeholder management was buried inside communications. PMI separated it out because research and practitioner feedback kept showing the same pattern: projects fail not because the schedule slipped, but because someone important was not bought in. I have watched a perfectly delivered technical implementation get shelved because the head of operations was never properly engaged. The work was correct. The stakeholder was not.

PMI treats stakeholder management as the social contract layer of a project. Scope, schedule, and cost are all measurable. Stakeholders are not. They have moods, politics, hidden agendas, and competing priorities. The knowledge area exists to give us a structured way to identify those humans, understand them, plan how to engage them, and then keep adjusting as the project changes.

The exam reflects this. You will see questions where the technically correct answer is wrong because it ignores a stakeholder’s expectations. You will also see questions where talking to a stakeholder is the answer even when it feels obvious, because PMI wants to reward the project manager who proactively engages rather than the one who waits for problems to surface.

Tip from my own prep: if a question mentions a sponsor or executive feeling surprised, the right answer almost always involves earlier engagement, not just better reporting.

The knowledge area contains four processes, distributed across three process groups:

Notice that Identify Stakeholders sits in Initiating. This is critical. On the exam, if you find a key stakeholder mid-project, your first move is to update the stakeholder register and revisit the engagement plan, not to start managing them in isolation. PMI wants you to feed new information back into the plan.

The four processes are also iterative. You do not identify stakeholders once and forget them. Each phase, each major change, and each new risk can introduce stakeholders or shift their interest. I learnt this the hard way on a finance migration where regulatory stakeholders only emerged in month four, by which point the engagement strategy needed a full rewrite.

The Identify Stakeholders process answers a simple question: who has a stake in this project? PMI casts a wide net. A stakeholder is anyone who can affect, be affected by, or perceive themselves to be affected by the project. That last clause matters. Perception alone makes someone a stakeholder.

Key inputs: - Project charter (especially the sponsor and high-level objectives) - Business documents (business case, benefits management plan) - Agreements (contracts with vendors introduce stakeholders) - Enterprise environmental factors and organisational process assets

Key tools and techniques: - Expert judgement - Data gathering: questionnaires, brainstorming, interviews - Data analysis: stakeholder analysis, document analysis - Data representation: stakeholder mapping (power/interest, salience, direction of influence) - Meetings

Key outputs: - Stakeholder register - Change requests - Project management plan updates - Project documents updates
I always start with the charter and the sponsor’s network, then expand outward by interviewing the obvious leaders in each affected function. After that I look at vendors, regulators, end users, and adjacent teams whose roadmaps could collide with mine.

The stakeholder register is the single most important artefact of this knowledge area. It needs to be useful, not just complete. Here is the template I now use:

A few rules I follow: - Never use job titles only. Real names matter because individuals leave, and your replacement may need different handling. - Keep the register confidential. Some fields, especially political notes, should not be shared widely. - Refresh it every phase gate at minimum, and after any major reorganisation.

A weak register lists 40 stakeholders with no strategy. A strong register has 12 to 20 prioritised stakeholders with specific actions next to each.

Once I know who my stakeholders are, I have to plan how to engage them. The output of this process is the stakeholder engagement plan, which lives inside the project management plan. PMI wants to see thoughtful, deliberate engagement, not ad hoc reactions.

The plan typically covers: - Current and desired engagement levels for each key stakeholder - Scope and impact of change for each stakeholder - Relationships and overlaps among stakeholders - Communication requirements for each engagement category - Methods for updating the plan as the project evolves

I treat the engagement plan as a behavioural contract with myself. It commits me to specific cadences, channels, and content for each priority stakeholder. When I get pulled into the weeds of execution, the plan is what reminds me to spend 30 minutes a week with the CFO even when nothing is on fire.

On the exam, if a question mentions that stakeholder engagement is inconsistent, weak, or surprise-prone, the answer often points back to the stakeholder engagement plan, either creating it, updating it, or following it.

PMI gives us several mapping techniques. The most common is the power/interest grid:

I have used this on nearly every project. It is simple, fast, and gives you a clear engagement default for each quadrant. There are variants: power/influence, influence/impact, and the impact/influence matrix. The mechanics are the same; only the axes change.

The salience model is more nuanced. It uses three attributes: - Power: ability to impose will - Legitimacy: appropriateness of involvement - Urgency: time-sensitivity of claim

Stakeholders with all three are called definitive stakeholders and demand top attention. Those with one are latent. Those with two are expectant. I find the salience model useful when politics matters more than hierarchy, because a stakeholder with no formal power but high legitimacy and urgency can still derail a project.

Worked example: a frontline supervisor with no budget authority blocked our rollout because his urgency and legitimacy as the voice of safety made him impossible to bypass. The salience model would have flagged him earlier than the power/interest grid did.

PMI defines five engagement levels and uses them in the Stakeholder Engagement Assessment Matrix:

The matrix shows current (C) and desired (D) engagement for each stakeholder. The gap between C and D drives the engagement strategy. If the CFO is currently Neutral and I need them Supportive, my plan must include actions to move them one step.

You will not need every stakeholder to be Leading. That is a common rookie misread of the matrix. Some stakeholders only need to be Neutral, and trying to push them further wastes energy. The exam tests this directly: the right desired level depends on what the project actually needs from that person.

This is the executing process where I do the actual work of engaging stakeholders, not just planning it. Tools and techniques include:

• Expert judgement on politics and culture
• Communication skills: feedback, presentations
• Interpersonal and team skills: conflict management, cultural awareness, negotiation, observation, political awareness
• Ground rules
• Meetings

What I have found most powerful here is observation. I watch how my sponsor reacts during a steering committee. I notice when someone goes quiet. I track who sends one-line email replies and who writes paragraphs. These signals tell me far more than any formal survey ever could.

Outputs include change requests, project management plan updates, and project documents updates. If engagement is failing, that is itself a finding worth raising as a change request, especially if it implies a scope, risk, or schedule impact.

The monitoring process closes the loop. I am asking: is my engagement strategy working? Tools include:

• Data analysis: alternatives analysis, root cause analysis, stakeholder analysis
• Decision making: multicriteria decision analysis, voting
• Data representation: updated stakeholder engagement assessment matrix
• Communication skills, interpersonal and team skills
• Meetings

The output that matters most is work performance information about stakeholder engagement. This feeds reporting and triggers updates to the engagement plan, communications management plan, and risk register.

I have learnt to keep monitoring honest. It is easy to convince yourself that engagement is fine because no one has complained. Silence is not consent. Silence is often resistance that has not yet found its voice. I run periodic one-to-ones precisely to surface what is not being said in the larger meetings.

You cannot engage stakeholders without communicating with them. The communications management knowledge area and stakeholder management are inseparable, which is why the exam often mixes them. A stakeholder question will sometimes have a communication answer, and vice versa.

Three things I always plan: - Channel: email, chat, video call, in-person, formal report - Cadence: weekly, monthly, on milestone, on exception - Content: status, decisions needed, risks, asks

For a high-power, high-interest stakeholder I might combine a 15-minute weekly walk, a Friday email summary, and a monthly steering deck. For a low-power, low-interest stakeholder a quarterly newsletter may be enough. Matching the channel to the stakeholder is the single highest leverage thing I do.

PMI does not name specific influence tactics, but they are implied throughout the framework. Here are the ones I use most:

• Reciprocity: offer something useful (data, introductions, visibility) before asking for support.
• Coalition building: bring along peers who already agree, then approach the resistant stakeholder together.
• Framing: align the project’s benefits to the stakeholder’s personal or functional goals.
• Quick wins: deliver something small and visible that builds credibility.
• Direct conversation: ask what would make them supportive, then listen.

The biggest mistake I see new project managers make is escalating too early. Escalation should be a last resort, not a first move. The exam reflects this preference: if there is an answer involving talking directly to the stakeholder first, it is almost certainly correct over escalating to the sponsor or PMO.

Scenario one: a key stakeholder moves from Supportive to Resistant after a leadership change. What do I do? I do not panic, and I do not escalate. I request a one-to-one to understand what changed. I update the stakeholder register, revise the engagement plan, and only then communicate any adjustments to the sponsor.

Scenario two: a new regulator is identified halfway through the project. The exam-ready answer is to update the stakeholder register, conduct stakeholder analysis, update the engagement plan, and revisit risk and communications plans. The wrong answer is to immediately schedule a meeting with the regulator without doing the analysis.

Scenario three: a team member tells me a peer department feels left out. I do not assume. I verify by talking to the peer department directly. If they are indeed a missed stakeholder, I add them to the register, classify them, and plan engagement. I also reflect on what failed in my original identification process.

Watch for these patterns: - The obvious answer is escalation. Usually wrong unless direct conversation has been exhausted. - The answer says do nothing or wait. Almost always wrong. PMI rewards proactive engagement. - The answer involves only the sponsor. Stakeholders extend far beyond the sponsor. - A question implies a stakeholder is being managed but never identified. The fix is the stakeholder register, not the engagement actions. - A question mixes scope and stakeholder language. Look at what is changing: if expectations are changing, it is stakeholder; if deliverables are changing, it is scope.

I also watch for distractor answers that involve doing analysis when action is needed, or doing action when analysis is needed. PMI is deliberate about the sequence.

Q1.A stakeholder is identified late in execution. What do you do first? 

Answer: update the stakeholder register.

Q2.The CFO is Neutral but the project needs Supportive. What is the right tool? 

Answer: Stakeholder Engagement Assessment Matrix to plan the move.

Q3.A regulator emerges with high urgency and legitimacy but low power. Which model fits best? 

Answer: Salience model.

Q4.A vendor is unhappy with communication frequency. Which plan do you update? 

Answer: communications management plan, then stakeholder engagement plan.

Q5.A previously Leading stakeholder becomes silent. What is the first action? 

Answer: schedule a one-to-one to understand.

Q6.The sponsor wants a different reporting cadence. What do you do? 

Answer: update the communications plan and the stakeholder engagement plan.

Q7.A team member identifies a missed stakeholder. What is the next step? 

Answer: validate, then update the stakeholder register and engagement plan.

Q8.Which process is in the Initiating group? 

Answer: Identify Stakeholders.

Q9.Which output is unique to Manage Stakeholder Engagement?

Answer: change requests stemming from engagement actions.

Q10.Engagement levels go from Unaware to which highest level?

Answer: Leading.