Project Stakeholder Management Guide 2026 + Builder

Project stakeholder management guide 2026 for project managers: identify stakeholders, map power and interest, plan engagement, engage and monitor, with a free Power-Interest Grid Builder

Every project has people who can speed it up or stop it cold: a sponsor who controls the budget, a team lead who quietly resists the change, a regulator who can delay sign-off by months. No Gantt chart captures that. Project stakeholder management is how project managers find these people early, understand what each one needs, and keep the right ones involved at the right level from kickoff to closure.

Key Takeaways
  • It is a cycle, not a task: identify stakeholders, analyze them, plan engagement, then engage and adjust for the whole project. PMBOK 8 treats Stakeholders as one of its seven performance domains.
  • Use the power-interest grid: manage closely, keep satisfied, keep informed or monitor. Spend most of your time on the high-power, high-interest corner.
  • Sponsors make or break projects: actively engaged executive sponsors are the top driver of project success, and 26% of organizations blame failed projects mainly on poor sponsor support.
  • Build personal power: formal authority is often weak in a matrix organization, so expert, referent and relational power do most of the work.
Map your stakeholders with the free grid builder

This guide is written for project managers who want a practical method, not theory. You will learn the four-step stakeholder management process, how to use a power-interest grid, how traditional and Agile projects handle stakeholders differently, and which of the 14 types of power actually help a project manager. Real cases, from Healthcare.gov to London 2012, show what happens when stakeholder management works and when it fails. You can also map your own project with the free Power-Interest Grid Builder and download a free Excel stakeholder register.

What Is Project Stakeholder Management?

What is project stakeholder management: a stakeholder is anyone who can affect or be affected by the project, such as the sponsor, project team, customers and users, suppliers, regulators and the community

A project stakeholder is any person, group or organization that can affect the project, be affected by it, or believes it will be affected. Stakeholder management is the work a project manager does to identify those people, understand their needs and influence, and keep them engaged so the project delivers what it promised.

Earlier editions of the PMBOK Guide treated stakeholder management as a knowledge area with its own processes. The PMBOK Guide Eighth Edition, released in late 2025, makes Stakeholders one of seven performance domains, alongside governance, scope, schedule, finance, resources and risk. Communication is no longer a separate area: it runs through every domain, and above all through stakeholder work. The message for project managers is simple: stakeholder management is part of daily project leadership, not a form you fill in once.

Typical project stakeholders include:

  • The project sponsor: funds the project, owns the business case and removes obstacles the project manager cannot.
  • The project team: the people doing the work, plus the functional managers who lend them to the project.
  • Customers and end users: the people who will pay for, use or live with the result.
  • Executives and steering committee members: they set priorities and can redirect or cancel the project.
  • Suppliers and vendors: PMBOK 8 explicitly treats them as stakeholders, not just contracts.
  • Regulators, legal and compliance teams: low interest most of the time, but they can stop a project at a gate.
  • The community: neighbours, advocacy groups and the public, especially on construction and public sector projects.

Stakeholder management and stakeholder engagement are related but not identical. Management is the overall strategy: who matters, how much and why. Engagement is the day-to-day work of talking, listening and involving people. Stakeholder engagement is where most of a project manager’s time actually goes.

The Stakeholder Management Process in 4 Steps

The stakeholder management process in 4 steps for project managers: 1 identify, 2 analyze and prioritize, 3 plan engagement, 4 engage, monitor and adjust, repeated across the project

Whatever methodology your project uses, stakeholder management follows the same four steps. The difference between strong and weak project managers is that strong ones keep repeating steps 2 to 4 as the project changes.

Step 1: Identify Stakeholders

Start with the project charter, the business case, the org chart and the list of systems or processes the project will change. Then run a short brainstorming session with the core team and ask: who decides, who pays, who uses, who builds, who approves and who could complain? Do not stop at senior names. Stakeholder identification works best when you start from the people who will have to change the most and work up to the people with authority. Our 80+ stakeholder identification templates can speed this up.

Step 2: Analyze and Prioritize

For each stakeholder, capture four things: their power over the project, their interest in it, their current attitude (supportive, neutral or resistant) and what they need from the project. Plot them on a power-interest grid, covered in the next section, to decide where to spend your limited time. Note the gap between where each key stakeholder is today and where you need them to be, for example from neutral to supportive before user acceptance testing.

Step 3: Plan Engagement

Turn the analysis into a stakeholder engagement plan: what each group needs to know, how often, through which channel and from whom. A sponsor may need a weekly 15-minute call; end users may need a demo every sprint and a feedback channel. Use a RACI matrix to make decisions and approvals explicit, and see our stakeholder engagement planning templates for ready-made formats.

Step 4: Engage, Monitor and Adjust

Carry out the plan, then watch for signals: missed meetings, late approvals, side conversations, new people joining a steering committee. Stakeholder positions shift when the project moves from planning to execution, when the scope changes or when a sponsor leaves. Review your stakeholder register at every phase gate, or every few sprints, and keep your project status reports aligned with what each audience needs to hear.

The process in practice

Real-life example

Healthcare.gov launched before anyone owned the requirements

When Healthcare.gov opened on October 1, 2013, many users could not create accounts or enroll. The U.S. Government Accountability Office later found that requirements kept changing late in development, that oversight was inconsistent, and that there was confusion over who was authorized to make key decisions in the final weeks. Every stakeholder was identified, but no one managed their competing demands. For project managers, the lesson is that steps 2 to 4 matter as much as step 1: someone must own requirements and decisions.

Source: U.S. GAO, report GAO-14-694 (2014)

From the field

“CMS launched Healthcare.gov without verification that it met performance requirements.”

U.S. Government Accountability Office (source)

By the numbers

  • $56M to $209Mgrowth in obligations for the main marketplace contract from 2011 to 2014
  • 47%of unsuccessful projects miss their goals because of poor requirements management

Source: U.S. GAO, 2014; PMI Pulse of the Profession, 2013

The Power-Interest Grid: Where to Spend Your Time

Power-interest grid for project stakeholders: manage closely for high power and high interest, keep satisfied for high power and low interest, keep informed for low power and high interest, monitor for low power and low interest

The power-interest grid is the most widely used stakeholder analysis tool. Its earliest version is credited to researcher Aubrey Mendelow in 1991. You score each stakeholder on two axes, power (how much they can change or block the project) and interest (how much they care about the outcome), and each quadrant gets a different engagement strategy:

  • Manage closely (high power, high interest): the sponsor, key business owners, major customers. Involve them in decisions, share risks early and meet them often.
  • Keep satisfied (high power, low interest): executives who approve budgets, legal, security. Keep updates short and decision-focused, and consult them before anything touches their area.
  • Keep informed (low power, high interest): end users, subject matter experts, downstream teams. Share progress, invite feedback, involve them in demos and testing. They are often your best early warning system.
  • Monitor (low power, low interest): a light touch is enough, but check regularly. A quiet stakeholder can move up the grid the moment the project reaches their team.

Two mistakes are common. The first is treating the grid as a one-time exercise: power and interest change, so redraw it at every phase. The second is ignoring attitude. A resistant stakeholder in the top right corner is your biggest project risk, which is why some project managers manage stakeholders the same way they manage risks, as described in this stakeholder management paper from PMI. The Power-Interest Grid Builder below adds attitude to every point so resistant key players stand out.

The grid in practice

Real-life example

Sidewalk Labs underestimated Toronto’s low-power stakeholders

In 2017, Alphabet’s Sidewalk Labs and Waterfront Toronto announced Quayside, a high-tech neighbourhood on Toronto’s waterfront. Residents, privacy advocates and civic leaders raised concerns about data collection and how much of the waterfront the company wanted to control. A privacy adviser resigned, the Canadian Civil Liberties Association went to court, and the plan was cut back from a proposed 190-acre district to a 12-acre site. In May 2020, Sidewalk Labs walked away, citing economic uncertainty. Groups that looked like keep-informed stakeholders at the start ended up with enough power to stall the project.

Source: CBC News and StateScoop

From the field

“That’s not good enough.”

Ann Cavoukian, former Ontario privacy commissioner, on resigning as a Sidewalk Labs adviser in 2018 (source)

By the numbers

  • 190 acresthe district Sidewalk Labs first pushed Toronto officials to allow
  • 12 acresthe site it settled for before abandoning the project in 2020

Source: StateScoop, May 2020

Power-Interest Grid Builder: Map Your Stakeholders

Use this free tool to map the stakeholders on your own project. It opens with a sample CRM rollout so you can see how it works. Each stakeholder appears on the grid as a numbered dot colored by attitude, and the tool builds an engagement plan with a strategy, rhythm and channel for each quadrant.

  1. Enter your project name, then replace the sample stakeholders with your own (up to 25).
  2. Score power and interest from 1 to 5 and choose each stakeholder’s current attitude.
  3. Check the watch list for resistant key players, then copy the plan or download it as a text file or a CSV register you can open in Excel.

Power-Interest Grid Builder

List your stakeholders, score their power and interest from 1 to 5, and get a live grid plus an engagement plan you can copy or download.

Stakeholders

Your power-interest grid

SupportiveNeutralResistant

Summary

Watch list

Engagement plan

Based on Mendelow’s power-interest grid. A score of 3 counts as high, so borderline stakeholders get more attention, not less. Nothing you type is stored or sent.

Traditional vs Agile Stakeholder Management

Traditional vs Agile stakeholder management: traditional projects use formal plans and milestone reviews with centralized decisions, while Agile projects involve stakeholders every sprint through reviews and backlog prioritization

Both approaches manage stakeholders. They differ in how often stakeholders are involved, how formal the communication is and who makes decisions.

In a traditional, predictive project, the project manager identifies stakeholders early, documents them in a stakeholder register and follows a communication plan. Stakeholders review deliverables at defined milestones and approve changes through formal change control. Decisions stay with the project manager, the sponsor and the steering committee. This works well when requirements are stable and approvals are regulated, for example in construction or public sector projects, but it can keep stakeholders at arm’s length and favours triple constraints of time, cost and scope over feedback.

Agile approaches bring stakeholders inside the delivery rhythm. In Scrum, the team presents the results of each sprint to key stakeholders at the sprint review, and the product owner turns their feedback into backlog priorities. Feedback arrives every few weeks rather than at the end, and active collaboration replaces formal sign-offs. The risk is the opposite: stakeholders who stop coming to reviews quietly lose touch with the product. For a deeper look at Agile stakeholder management, see Drew Jemilo’s Agile Alliance session.

Traditional vs Agile Stakeholder Management at a Glance

AspectTraditional (predictive)Agile
InvolvementAt set milestones and phase gatesEvery sprint, as part of the team rhythm
FormalityStakeholder register, communication plan, formal sign-offLight documentation, working sessions and demos
DecisionsProject manager, sponsor and steering committeeProduct owner prioritizes with stakeholder input
Handling changeChange requests through change controlNew items go into the product backlog
Key eventMilestone review or steering meetingSprint review
Main riskStakeholders see the result too late to shape itStakeholders stop attending and drift away

Sprint review practice from the 2020 Scrum Guide. Most real projects are hybrids: use formal approvals where rules require them and frequent reviews everywhere else.

Types of Power a Project Manager Can Use

Types of power for project managers: positional power from the role, such as formal, reward and punitive power, and personal power, such as expert, referent and relational power

Project managers are accountable for results but rarely control the people doing the work. To deliver within the triple constraints and keep stakeholders aligned, they rely on influence. The PMBOK Guide Sixth Edition (2017) listed 14 forms of power a project manager can draw on, building on research such as PMI’s paper on the types of power project managers use to gain support. They fall into two groups: positional power, which comes with the role, and personal power, which you earn.

Four of them matter most in day-to-day stakeholder management.

Referent Power

Referent power is influence that comes from respect and trust. People follow you because you have been honest, fair and consistent with them over time. It is the slowest power to build and the most durable.

Real-life example: during a tense release week, a frustrated operations manager threatens to escalate. You meet them the same day, acknowledge the problem, and deliver the fix you promised by Friday. The next time you need their support for a cutover weekend, they say yes without a fight.

Expert Power

Expert power comes from knowledge people value: technical skill, industry experience or deep project management know-how. When stakeholders trust your expertise, they accept your recommendations faster, which shortens decisions.

Real-life example: a critical integration fails during testing. You lay out the root cause, two options and the impact of each on the schedule, and recommend one. The steering committee approves it in one meeting instead of three.

Reward Power

Reward power is the ability to give something people value: recognition, interesting assignments, a strong performance review or a bonus. It works well, but only if you actually control the reward. In many organizations, functional managers do, not the project manager.

Real-life example: after the team delivers a difficult milestone on time, you thank them in front of the sponsor and send specific feedback to each person’s line manager for their annual review. Motivation for the next phase stays high.

Formal Authority

Formal authority, also called positional or legitimate power, comes from your role on the project. It lets you make decisions on scope, priorities and assignments within the limits of the project charter. It is weakest in functional and weak matrix organizations, where functional managers often set priorities, as this PMI article on project failure notes. Use it for final calls, not as your first move.

Real-life example: two departments keep reopening a scope decision. You confirm the approved change with the sponsor, update the plan, reassign owners and close the debate through the official change log.

The Other 10 Types of Power

Knowing when to use each type of power is one of the essential leadership skills for project managers. The table below lists all 14 forms of power from the PMBOK Guide Sixth Edition, with a simple rule for each.

The 14 Forms of Power for Project Managers

PowerComes fromWhat it looks likeRule of thumb
Positional (formal, legitimate)Your roleAuthority from your position on the projectUse with care
RewardYour rolePraise, recognition, assignments or bonusesUse with care
Punitive (coercive)Your roleDiscipline or negative consequencesLast resort
ExpertYouSkills, experience and certifications others valueBuild it
ReferentYouRespect and trust people have in youBuild it
Personal (charismatic)YouCharm and personal appealUse with care
InformationalYour networkControl of who gets which information, and whenBuild it
RelationalYour networkConnections and alliances across the organizationBuild it
SituationalThe situationInfluence gained in a specific moment, such as a crisisUse with care
PersuasiveYour approachArguments that move people to actBuild it
IngratiatingYour approachFlattery or common ground to win favourUse with care
Pressure-basedYour approachLimiting choices to force complianceLast resort
Guilt-basedYour approachAppealing to obligation or dutyLast resort
AvoidingYour approachRefusing to take part or decideLast resort

Forms of power listed in the PMBOK Guide Sixth Edition (2017). The rule of thumb column is ProjectManagers.net guidance for project managers, not part of the standard.

No project manager needs all 14. Most successful ones lean on expert, referent, relational and persuasive power, use positional and reward power for final calls, and keep the pressure-based forms for genuine emergencies.

Benefits of Effective Stakeholder Management

Benefits of effective stakeholder management for projects: stronger sponsor support, fewer late surprises and conflicts, better requirements and decisions, and higher adoption of the project result

Good stakeholder management shows up in measurable project results, not just better relationships. The main benefits for project managers are:

  • Stronger sponsor support: an engaged sponsor clears roadblocks, makes quick decisions and defends the project when priorities shift.
  • Fewer late surprises: conflicts and objections surface during planning, when they are cheap to fix, rather than at go-live. When they do escalate, our guide to the 5 conflict levels helps you choose the right response.
  • Better requirements and decisions: stakeholders know constraints, risks and shortcuts the core team does not.
  • Higher adoption: people who helped shape a change are far more likely to use what the project delivers, which is where the business benefits actually come from.
Benefits in practice

Real-life example

London 2012 built stakeholder agreement into its structure

The Olympic Delivery Authority (ODA) had to coordinate central and local government, five host boroughs, utilities, transport operators, unions and the park’s neighbours. Its delivery partner kept close relations with the park’s neighbours in the five host boroughs, Network Rail, Crossrail, a major shopping centre and the utility companies, and the masterplanning team embedded a stakeholder engagement team within planning and design so listening became everyone’s job. The venues and infrastructure were ready on time, and the ODA published its lessons in a Learning Legacy program for other major projects.

Source: Laing O’Rourke and AECOM

From the field

“Europe’s largest construction project to the ultimate deadline and within budget.”

John Armitt, ODA Chairman, describing the Olympic Park build (source)

By the numbers

  • 81% vs 45%of high- vs low-performing organizations have actively engaged executive sponsors
  • 62%average share of projects with actively engaged sponsors in 2017, up from 59%

Source: PMI Pulse of the Profession, 2015; CIO on PMI Pulse 2017

Common Stakeholder Management Challenges (and How to Fix Them)

Common stakeholder management challenges and fixes: conflicting expectations, disengaged sponsors and stakeholders, unrealistic expectations and shifting power

Even experienced project managers run into the same common stakeholder management challenges. Here are the ones that hurt projects most, with a practical fix for each:

  • Conflicting expectations: sales wants speed, compliance wants control, finance wants a lower budget. Fix: make the trade-offs visible with data, and let the sponsor decide the priority in writing.
  • Disengagement over time: stakeholders who were eager at kickoff stop opening updates during execution, then push back at go-live. Fix: shorten updates, tailor them to what each person cares about, and ask for small decisions to keep them involved.
  • Unrealistic expectations: a date or scope promised before the project was planned. Fix: show the constraints and options early, document what is realistic, and escalate to the sponsor rather than absorbing the gap.
  • Shifting power: a reorganization, a new executive or a public controversy moves stakeholders across the grid. Fix: redraw the power-interest grid at every phase gate and after any major change.
  • Too many decision makers: when everyone can say no, no one says yes. Fix: agree on decision rights early with a RACI matrix and a clear escalation path.
Challenges in practice

Real-life example

Berlin Brandenburg Airport opened nine years late

Planned to open in 2011, BER finally opened on October 31, 2020. The project was owned by three public shareholders, plans changed again and again during construction, and many decisions were made by people far removed from the work, while key staff and their knowledge kept leaving. Structural problems and a corruption scandal added to the delays. The original budget of 1.7 billion euros more than tripled. With many powerful stakeholders pulling in different directions, no one held the scope steady.

Source: AFP via Inquirer.net and Dlubal construction analysis

From the field

“This time it’s going to work.”

Dietmar Woidke, Brandenburg premier, on the final 2020 opening date (source)

By the numbers

  • 3x+growth of BER’s original 1.7 billion euro budget during the delays
  • 26%of organizations say inadequate sponsor support is the main cause of failed projects

Source: AFP, 2019; ITWeb on PMI Pulse of the Profession 2018

4 Stakeholder Management Best Practices for New Project Managers

4 stakeholder management best practices for new project managers: involve stakeholders early, seek continuous feedback, stay transparent, and review and adjust the stakeholder map regularly

New project managers do not need complex frameworks to build credibility with stakeholders. These four habits work on any project and with any methodology.

  1. Involve stakeholders early: invite key stakeholders to scoping and planning sessions before the plan is fixed. People support what they helped create, and early input is cheaper than late rework.
  2. Seek continuous feedback: ask stakeholders what is working and what is not, about the project and about your communication. Regular feedback loops catch small issues before they become escalations.
  3. Stay transparent: share bad news early, with a proposed solution. Stakeholders forgive problems far more easily than surprises. The 5 Cs of communication are a useful checklist for every update.
  4. Review and adjust regularly: what worked during initiation rarely works during execution. Revisit your grid, attitudes and communication rhythm at every phase gate or every few sprints.
Best practices in practice

Real-life example

A stakeholder map rescued a failing supply chain rollout

In a case described in a PMI white paper, a fast-growing mobile communications company went live with a new supply chain system. Customers did not receive orders, invoices were delayed or lost, and the sales force resisted the change. A stakeholder mapping exercise, done for the first time after go-live, showed that the sponsor lacked influence with sales and that the sales director had high influence but low commitment. The company strengthened sponsorship inside sales and replaced some project leads with more credible people, which helped rescue the project.

Source: Miller and Oliver, Engaging Stakeholders for Project Success, PMI white paper

From the field

“Stakeholder mapping is not a one-off exercise.”

David Miller and Mike Oliver, Changefirst, in a PMI white paper (source)

By the numbers

  • 40% vs 30%of high vs low performers align with sponsors on success and accountability at initiation
  • 72% vs 61%of projects rated successful when teams apply a structured framework vs none

Source: PMI Pulse of the Profession 2026, via the PMI blog

Free Stakeholder Register and Power-Interest Grid Template (Excel)

Prefer a spreadsheet? Download the free Excel template to keep a stakeholder register for your project. Score power and interest, and the template places each stakeholder in the right quadrant, suggests an engagement rhythm and fills a power-interest grid automatically.

Stakeholder Register and Power-Interest Grid Template

  • Stakeholder Register: 30 rows with role, power, interest, attitude, current and desired engagement, key interests, actions, owner and next review date.
  • Power-Interest Grid: a live 2×2 grid that lists each stakeholder in the right quadrant, with counts.
  • How to Use: short instructions and the engagement strategy for each quadrant.
Download the free Excel template (.xlsx)

Works in Microsoft Excel 2019 or later, Excel for Microsoft 365 and Excel for the web. Free, no sign-up.

Looking for more free tools for project managers? Browse the Free Project Management Toolkit.

Stakeholder Management Quiz: Test Yourself

Ten quick questions to check what you learned. Pick your answer, then open the toggle to see if you were right.

How Well Do You Know Stakeholder Management?

10 questions. 9 or 10 correct means you are ready to map stakeholders on your next project.

Question 1

A department head can cancel your project but rarely follows its progress. Where do they sit on the power-interest grid?

  1. AKeep satisfied
  2. BManage closely
  3. CKeep informed
  4. DMonitor
Show answer

Answer A: Keep satisfied. High power and low interest means keep satisfied: short, decision-focused updates and early consultation on anything that touches their area.

Question 2

In PMBOK 8, how is stakeholder work organized?

  1. AAs a knowledge area with 10 processes
  2. BAs one of seven performance domains
  3. CAs part of the Communications domain
  4. DIt was removed from the guide
Show answer

Answer B: As one of seven performance domains. PMBOK 8 has seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk.

Question 3

Which stakeholder deserves the most attention?

  1. AA supportive user with low power
  2. BA neutral regulator with low interest
  3. CA resistant executive with high power and high interest
  4. DA vendor with low power and low interest
Show answer

Answer C: A resistant executive with high power and high interest. A resistant stakeholder in the manage-closely quadrant is the biggest stakeholder risk on the project.

Question 4

Who is credited with the earliest version of the power-interest grid?

  1. AKen Schwaber
  2. BSpeed Leas
  3. CFrench and Raven
  4. DAubrey Mendelow
Show answer

Answer D: Aubrey Mendelow. Aubrey Mendelow described the power-interest matrix in 1991.

Question 5

What does PMI’s research name as the top driver of projects meeting their original goals?

  1. AActively engaged executive sponsors
  2. BLarger budgets
  3. CAgile methods
  4. DDetailed Gantt charts
Show answer

Answer A: Actively engaged executive sponsors. PMI’s Pulse of the Profession research has repeatedly found that actively engaged executive sponsors are the top driver of project success.

Question 6

In Scrum, when does the team formally present its work to key stakeholders?

  1. ADaily Scrum
  2. BSprint review
  3. CSprint retrospective
  4. DOnly at the final release
Show answer

Answer B: Sprint review. At the sprint review, the Scrum Team presents its results to key stakeholders and they decide together what to do next.

Question 7

A project manager is respected because they have always kept their promises. Which power is this?

  1. APositional
  2. BReward
  3. CReferent
  4. DPressure-based
Show answer

Answer C: Referent. Referent power comes from the trust and respect others have in you.

Question 8

Which statement about stakeholder management is true?

  1. AIt is done once, at project initiation
  2. BIt only applies to external stakeholders
  3. CIt is the sponsor’s job, not the project manager’s
  4. DIt continues for the whole project
Show answer

Answer D: It continues for the whole project. Stakeholder positions change, so identification, analysis and engagement continue throughout the project.

Question 9

A stakeholder has low power but high interest. What is the right strategy?

  1. AKeep informed
  2. BManage closely
  3. CKeep satisfied
  4. DIgnore them
Show answer

Answer A: Keep informed. Low power and high interest means keep informed: regular updates, demos and a way to give feedback.

Question 10

Why is formal authority often weak for project managers?

  1. ABecause PMI forbids it
  2. BBecause functional managers often control priorities and rewards
  3. CBecause Agile projects have no managers
  4. DBecause sponsors cannot delegate
Show answer

Answer B: Because functional managers often control priorities and rewards. In functional and matrix organizations, functional managers usually control people’s priorities and rewards, so project managers rely on influence.

Video: What Is Stakeholder Management?

In this short video, project management trainer Mike Clayton explains what stakeholder management means, why it matters and how project managers can identify stakeholders and plan engagement in practice.

What Is Stakeholder Management? Project Management in Under 5

Mike Clayton of Online PM Courses covers the essentials in about 5 minutes.

Video by Online PM Courses, Mike Clayton, on YouTube.

Stakeholder Management Facts Worth Checking

10 Stakeholder Management Claims, Checked

Common claims about stakeholder management, checked against the original sources.

ClaimVerdictWhat the data says
Stakeholder management is a one-time task done at project start.FalsePMI research treats the stakeholder map as a living document to revisit whenever direction, difficulties or key players change. PMI white paper
The PMBOK Guide lists 14 types of power for project managers.Partly trueThe Sixth Edition (2017) listed 14 forms of power. The current Eighth Edition is built around six principles and seven performance domains. PMI
Stakeholders is a performance domain in PMBOK 8.TrueIt is one of seven domains, with governance, scope, schedule, finance, resources and risk. PMI
Communications has its own performance domain in PMBOK 8.FalseCommunications is not one of the seven domains. It runs across them, especially stakeholder work. PMI
The power-interest grid dates back to 1991.TrueThe earliest version is credited to Aubrey Mendelow, 1991. Nielsen Norman Group
Engaged executive sponsors are the top driver of project success.TruePMI’s 2017 Pulse of the Profession named actively engaged sponsors the top driver of projects meeting their goals. CIO, on PMI 2017
Poor sponsor support is a leading cause of failed projects.TrueIn PMI’s 2018 survey, 26% of organizations named inadequate sponsor support as the primary cause of failed projects. ITWeb, on PMI 2018
Most people affected by a change fully commit to it.FalseChangefirst research cited by PMI found only 25% of change recipients fully commit; the rest accept or resist. PMI white paper
Agile projects need less stakeholder management.FalseScrum involves key stakeholders every sprint at the sprint review, so engagement is more frequent, not less. Scrum Guide 2020
Project managers always have formal authority over their team.FalseIn weak matrix organizations, functional managers often define priorities, so project managers rely on influence. PMI

Checked November 2026.

Conclusion

Stakeholder management is not a document you complete during planning. It is a habit that runs through the whole project: find the people who matter, understand what they need, decide how much attention each one deserves, and keep adjusting as power and interest shift. The cases in this guide show the pattern. Projects that engage stakeholders early and keep their sponsors involved, like London 2012, hold their scope and their deadline. Projects that treat stakeholders as a list, like Healthcare.gov and BER, pay for it later.

Start small: map your current project in the Power-Interest Grid Builder above, pick the two or three stakeholders who need more attention this week, and put a meeting in the calendar. Your ability to manage stakeholders will shape your results, and your reputation as a project manager, more than any schedule.

Stakeholder Management FAQ

Stakeholder Management: Common Questions

What is the difference between stakeholder management and stakeholder engagement?

Stakeholder management is the overall approach: identifying stakeholders, analyzing their power and interest, and planning how to work with each one. Stakeholder engagement is the ongoing interaction that carries out that plan, such as meetings, updates, demos and feedback sessions. Management sets the strategy; engagement is the daily work.

How do you identify stakeholders on a new project?

Review the project charter, business case and org chart, then brainstorm with the core team: who decides, who pays, who uses the result, who builds it, who approves it and who could object? Include internal and external groups, and start with the people who will have to change the most.

What is a power-interest grid?

A power-interest grid plots stakeholders by their power over the project and their interest in it. The four quadrants give four strategies: manage closely (high power, high interest), keep satisfied (high power, low interest), keep informed (low power, high interest) and monitor (low power, low interest).

What should a stakeholder register include?

At minimum: the stakeholder’s name or group, role, power, interest, attitude, key needs or concerns, the engagement strategy, communication frequency, the owner of the relationship and a next review date. The free Excel template on this page includes all of these fields.

Can stakeholder management be applied in Agile projects?

Yes. Agile projects involve stakeholders more often, not less. In Scrum, key stakeholders attend the sprint review every sprint, and the product owner uses their feedback to prioritize the backlog. The project manager or Scrum Master still needs to know who those stakeholders are and keep them engaged.

What should a project manager do when stakeholder expectations are unrealistic?

Address it early and with facts. Show the constraints, the trade-offs between scope, time and cost, and the realistic options. Escalate to the sponsor if needed, and document the agreed expectations so they do not drift later.

How often should you update the stakeholder map?

Review it at every phase gate or every few sprints, and immediately after major changes such as a new sponsor, a reorganization, a scope change or public controversy. Power and interest shift as a project moves forward.

Suggested articles:

Scroll to Top