Stakeholder Analysis: A Practical How-To Guide
Ask a project manager what caused a past project to struggle, and you will rarely hear "we ran out of spreadsheets." More often the answer involves a decision-maker who felt blindsided, a community group that mobilised opposition, or an internal team whose workload was quietly doubled without consultation. Stakeholder dynamics sit behind a striking share of project overruns, scope disputes, and outright failures. Yet stakeholder analysis is still treated as a checkbox exercise — a slide deck produced at kickoff and never reopened.
This guide offers a practical approach: who counts as a stakeholder, how to map them, what to do with that map, and how to avoid the mistakes that turn a good analysis into shelf-ware.
Who Counts as a Stakeholder?
The standard definition — anyone who affects or is affected by the project — sounds simple, but most teams apply it too narrowly. The obvious stakeholders (the sponsor, the client, the steering committee) get listed. The less obvious ones get missed.
A more useful framing is to scan four rings. The first ring is your project team and direct governance: the sponsor, PMO, core team, and any formal oversight bodies. The second ring is the organisation: departments whose processes will change, IT teams whose infrastructure will be touched, HR if roles are being redesigned. The third ring is external: suppliers, regulators, partner agencies, Indigenous rights holders, community associations. The fourth ring is the broader environment: media, advocacy groups, elected officials, the general public in cases with service-delivery implications.
Not every ring will be equally relevant on every project. But the discipline of scanning all four before finalising your list catches the stakeholders who surface later and cause the most disruption — precisely because nobody thought to engage them early.
Mapping with the Power-Interest Grid
Once you have a comprehensive list, you need a way to prioritise. The power-interest grid places each stakeholder on two axes: their power to influence the project outcome, and their interest in that outcome. The result is four quadrants, each calling for a different engagement approach.
Manage closely. High power, high interest. These stakeholders can make or break the project and are paying close attention. Invest the most here: regular briefings, early involvement in key decisions, and a direct line to the project manager.
Keep satisfied. High power, lower interest. These stakeholders can exert significant influence but are not focused on your project day-to-day. Keep them informed at a level that prevents surprises; do not overwhelm them with detail they do not need.
Keep informed. Lower power, high interest. These stakeholders care about the outcome but have limited ability to affect it. Regular, clear communication builds goodwill and often surfaces useful ground-level intelligence about project risks.
Monitor. Low power, low interest. Light-touch engagement is appropriate here, but revisit placement periodically — circumstances change, and a stakeholder who is disengaged today may become influential tomorrow.
A word of caution: the grid is a starting point, not a permanent classification. Power and interest shift as the project progresses. A regulator in the "monitor" quadrant at initiation may move firmly into "manage closely" when you reach the approvals phase.
From Map to Plan: Engagement That Holds Up
A stakeholder map that does not drive action is just a list of names. The next step is an engagement plan that answers two questions for each key stakeholder: what does this stakeholder need from the project, and what does the project need from this stakeholder?
What stakeholders need can include information, involvement in decisions, assurance that their concerns are heard, or simply the certainty that a change will not harm their interests. What the project needs from them can include funding decisions, technical input, approvals, or advocacy with other stakeholders. Writing both sides down forces the team to think about engagement as a two-way exchange, not just a communication broadcast.
From there, specify the engagement mechanism (briefing, workshop, consultation, written update), frequency, owner, and success indicator. Keep it proportional — a one-page matrix is more likely to be used than a forty-row spreadsheet.
Common Mistakes to Avoid
Treating the initial list as final. Add stakeholders as you learn more about the project environment.
Confusing communication with engagement. Sending a newsletter is not the same as understanding concerns and responding to them.
Letting the register go stale. Stakeholder positions shift. Review your map at each phase gate.
Assigning engagement to one person. The project manager owns the strategy, but relationship-building should be distributed across the project team.
Ignoring internal stakeholders. The departments and teams whose daily work will change are often the most powerful determinants of adoption success.
Stakeholder analysis is not a one-time deliverable. It is a living discipline — one that distinguishes projects that deliver lasting value from those that deliver outputs nobody uses.
XNM Consulting brings structured stakeholder engagement into every project delivery engagement. To learn how we support complex, multi-stakeholder projects, visit our Program and Project Delivery page.