Who to manage closely, who to keep informed, and a filled-in map you can copy.
A stakeholder map is a diagram that sorts everyone affected by a project by how much power they have over it and how interested they are in it, so you know who to involve closely and who only needs updates. To make one, list your stakeholders, score each on power and interest, place them on a two-by-two grid, then write down how you’ll engage each group.
Figure 1The power/interest grid. Each quadrant tells you how to engage the people in it. The highlighted quadrant, high power and high interest, is where most of your time goes.
Stakeholder mapping is the process of listing everyone who can affect or is affected by a project, then arranging them visually to decide how to involve each one. The result, a stakeholder map, turns a long list of names into a plan: who to meet every week, who to update every month, and who only needs to know the project exists.
The most common format is a two-by-two grid with power on one axis and interest on the other, often called the power-interest matrix or Mendelow’s matrix. Wikipedia’s article on stakeholder analysis calls the two-dimensional matrix “the most common presentation style” (Wikipedia).
Stakeholder mapping is important because projects often stall not on the work itself but when someone with a say hears about a decision too late. A stakeholder map makes those people visible at the start, while there’s still time to involve them. The UK Government Analysis Function puts it simply: “Effective stakeholder mapping helps you identify who needs to be involved, when, and why” (Analysis Function).
You need a stakeholder map whenever a piece of work touches people outside your own team: a new project, a product launch, a reorganization, a tool rollout, or a new role where you don’t yet know who decides what. For a two-week task inside one team, a list of names in the project doc is usually enough.
Stakeholders are usually split into internal stakeholders, who work inside the organization, and external stakeholders, who don’t. Both types can sit anywhere on the grid: a regulator is external but has a lot of power, while a new hire is internal but has little say.
Here’s how the two types compare:
Type | Who they are | Examples |
|---|---|---|
Internal | People inside your organization | Executives, managers, the teams that build or use the work |
External | People outside it | Customers, suppliers, partners, regulators, investors |
The four quadrants of a stakeholder map are manage closely, keep satisfied, keep informed and monitor, based on each stakeholder’s power and interest. Each quadrant comes with a different level of engagement, from regular working sessions down to an occasional check-in.
Here’s what each quadrant asks of you, with examples from the stakeholder map further down:
Quadrant | Power and interest | What to do | Example |
|---|---|---|---|
Manage closely | High power, high interest | Involve early, meet regularly, decide together | CFO, head of IT |
Keep satisfied | High power, low interest | Short updates, consult before big changes | CEO, legal and compliance |
Keep informed | Low power, high interest | Regular updates and a place to raise concerns | Department managers, employees |
Monitor | Low power, low interest | Occasional check-ins | Payroll provider |
Quadrant names vary between sources. The UK Government Analysis Function, for example, uses “consult with” for one of them. The idea is the same everywhere: match your effort to each stakeholder’s power and interest.
Stakeholder mapping is the visual step: placing people on a grid. Stakeholder analysis is the wider process around it, which also covers each stakeholder’s needs, concerns and likely reaction, and turns them into an engagement plan. In practice the two terms are often used interchangeably, and most teams do both in the same session.
Make a stakeholder map in four steps: list everyone the project affects, score each person on power and interest, place them on the grid, and write an engagement plan for each quadrant. Do it with two or three people who know the project, because one person’s view of who matters is always incomplete.
In Whimsical, each stakeholder can be a sticky note you drag between quadrants as the project moves, and you can mention the owner of each relationship in a comment so they get a notification.
Write the reason next to every placement. “CFO: signs off the budget” settles the next disagreement faster than a name on a grid, and it tells you when someone should move.
Here’s a stakeholder map for a realistic project: rolling out a new expense tool at a 200-person company, led by the operations manager. It has eleven stakeholders across the four quadrants, and the three to manage closely are highlighted.
Figure 2Stakeholder map example: expense tool rollout. Rolling out an expense tool at a 200-person company. The highlighted stakeholders are the three to manage closely.
A stakeholder map only becomes useful once it turns into an engagement plan. Here’s the plan for the same project, one line per stakeholder, starting with the three to manage closely and following the map’s quadrants:
Stakeholder | What they need | How often | Owner |
|---|---|---|---|
CFO (sponsor) | Budget and rollout decisions | Weekly 30-minute check-in | Operations manager |
Head of IT | Security review and single sign-on setup | Weekly, in the project channel | Operations manager |
Finance team lead | Approval rules and reporting | Twice a week during setup | Finance analyst |
CEO | Go-live date and risks | Monthly five-line update | CFO |
Legal and compliance | Data storage and retention terms | Before the contract is signed | Operations manager |
IT security | Vendor security questionnaire | Once, before vendor choice | Head of IT |
Department managers | What changes for their teams, and when | Every two weeks | Operations manager |
Employees who file expenses | How to submit expenses, and from when | Launch email and a one-page guide | Operations manager |
Accounts payable clerks | How approved expenses reach them | Training session before launch | Finance team lead |
Payroll provider | Notice if reimbursement files change | At launch | Finance analyst |
Office manager | Where receipts for office purchases go | At launch | Operations manager |
A good engagement plan says who gets what, how often, and through which channel. Most weak plans name a group and a vague intention instead. Here are four lines the way they usually get written, and the way they should read:
Keep the CFO in the loop.
Manage closely: the CFO reviews budget and rollout decisions in a weekly 30-minute check-in.
Tell IT about the project.
Manage closely: the head of IT signs off the security review before we choose a vendor.
Update the CEO.
Keep satisfied: the CEO gets a five-line update on the first Monday of each month.
Let everyone know when it launches.
Keep informed: employees get a launch email and a one-page guide a week before go-live.
Use the power/interest grid for most projects, because it answers the question teams ask most often: where to spend their time. Use a salience model when legitimacy and urgency matter as much as power, a relationship map when influence travels through people, and a RACI matrix when the real question is who does what. The salience model, described by Mitchell and colleagues in 1997, uses three dimensions: power, legitimacy and urgency (Wikipedia).
Figure 3Which stakeholder mapping method should you use? One question decides it. The highlighted answer, the power/interest grid, fits most projects.
What do you need to know?
Yes, an AI assistant can draft a first stakeholder map from a project brief in seconds, and it’s good at suggesting stakeholders you forgot. We’d still check every placement with the team: a model can’t know that the head of sales cares about this project because of last quarter’s numbers.
With the Whimsical connector for Claude, Claude can draw the map as a Whimsical board. This prompt asks for the same layout as the example above:
The four steps of stakeholder mapping are: identify every stakeholder, score each one on power and interest, place them on the power/interest grid, and plan how to engage each quadrant. Review the map at each milestone, because people move between quadrants as a project changes.
The purpose of a stakeholder map is to decide where your communication effort goes. It shows who needs close involvement, who needs regular updates and who only needs an occasional check-in, so the people who can shape or block the project hear about decisions before they’re made.
A stakeholder relationship map shows how stakeholders influence each other, as a network of people connected by lines, instead of placing them on a grid. Use one when decisions travel through informal influence, for example when a respected engineer shapes what the head of IT approves.
The best tool for stakeholder mapping is one your team can edit together while you discuss placements. A whiteboard with sticky notes works well, because you can drag stakeholders between quadrants as opinions change. A spreadsheet helps alongside it for long stakeholder lists and the engagement plan.
Update a stakeholder map at every major milestone, and whenever someone joins, leaves or changes role. For most projects a quick monthly review is enough. A stakeholder map is only useful while it matches reality, so an outdated map is worse than none.
Start your stakeholder map from ours
Make a free copy of the example map, then replace the stakeholders with your own.
Make a free copy of the map