A stakeholder is anyone who can affect a project's outcome, or who is affected by it. That's a deliberately wide net — it includes the people doing the work, the people paying for it, the people who'll use what it produces, and sometimes people who never touch the project directly but whose support (or opposition) determines whether it succeeds. Not every stakeholder matters equally, which is exactly why project managers spend time mapping them rather than just listing them.
Splitting stakeholders into "internal" and "external" is common, but it's not that useful on its own — a junior internal team member and the CEO are both "internal," and they need completely different handling. What actually determines how a project manager should engage a stakeholder is two independent things: how much power they have to affect the project's direction or funding, and how much interest they have in its outcome. Plotting stakeholders on those two axes — a simple 2x2 grid, sometimes called Mendelow's matrix — gives a project manager a practical playbook instead of a flat list:
— High power, high interest — manage closely. These are your sponsors and key decision-makers; they need regular, substantive engagement and should never be surprised by project news.
— High power, low interest — keep satisfied. Executives who could shut the project down if unhappy, but who don't want day-to-day detail. Brief, infrequent updates; don't overload them.
— Low power, high interest — keep informed. End users, affected teams — people who care a lot but can't unilaterally change direction. Regular updates keep them supportive rather than blindsided.
— Low power, low interest — monitor with minimal effort. Worth tracking in case their position shifts, but not worth much active management time.
This is the practical reason stakeholder identification matters at all: it's not about creating a complete list for its own sake, it's about deciding, deliberately, how much of a limited communication budget each person actually deserves.
Every stakeholder has some stake in the outcome, but only some have real influence over whether the project succeeds — the sponsor funding it, the executive who can reprioritize it out of existence, the customer whose adoption determines whether it was worth doing. Key stakeholders sit in the high-power quadrants of the grid above, more or less by definition. Everyone else still matters, and ignoring low-power stakeholders entirely is a common mistake — a quiet department that feels steamrolled by a project can create resistance later that a little early engagement would have prevented — but they don't need the same weekly attention.
Once stakeholders are identified, most project teams map them onto a RACI chart to clarify exactly what role each one plays on specific decisions or deliverables: who's Responsible for doing the work, who's Accountable for the outcome (usually just one person per item), who needs to be Consulted before a decision is made, and who simply needs to be Informed after the fact. Stakeholder mapping tells you who matters and how much attention they need overall; RACI tells you, item by item, exactly what role they play. The two are complementary, not competing — a high-power, high-interest stakeholder from the power/interest grid is very often the "Accountable" party on a RACI chart for the decisions that matter most to them.
Start with the obvious roles — sponsor, project manager, core team, direct customer or end user — then work outward by asking, for each one: who approves their work, who's affected downstream by what they produce, and who could block or delay this if unhappy. That third question catches the people most teams miss: the compliance reviewer, the team whose system you're integrating with, the department that inherits support once the project ships. Revisit the list at each major phase, not just once at kickoff — stakeholders change as a project moves from planning into delivery and then into rollout.
What is a stakeholder in project management? Anyone who can affect a project's outcome or who is affected by it — including the project team, the sponsor, end users, and sometimes outside parties like regulators or partners.
What's the difference between a stakeholder and a key stakeholder? Every stakeholder has some stake in the outcome, but a key stakeholder has real influence — usually the power to fund, block, or redirect the project. Everyone else needs to be considered, but not managed as closely.
What is the power/interest grid used for? It's a simple framework for deciding how much engagement each stakeholder actually needs, based on how much influence they have over the project and how much they personally care about the outcome.
How is a stakeholder different from a RACI role? Stakeholder mapping identifies who matters and how much attention they need overall. RACI assigns a specific role (Responsible, Accountable, Consulted, or Informed) to each stakeholder for individual decisions or deliverables — the two work together.
Can a stakeholder be outside the organization? Yes. Customers, regulators, vendors, and partners are all common external stakeholders, and depending on the project, they can carry as much influence as anyone internal.
.svg){kind=small}
