Stakeholder Mapping: How to Build a Stakeholder Map in 3 Weeks
9 min read ยท 2026-10-12
Stakeholder mapping means listing everyone who can affect your project or is affected by it. You then place each person on a grid by how much power they have and how much they care. The map tells you who to involve closely, who to keep satisfied, who to keep informed and who to simply watch. Then you plan how and how often you talk to each group.
The grid is only half the job. A map helps when it turns into actions: an owner for each key person, a message, a set rhythm for updates, and a review date. The roadmap below takes you from a blank page to a working map and a first round of updates in 3 weeks, alongside your normal work.
The roadmap at a glance
Goal: Build a stakeholder map and a communication plan your team uses from week 3 onward. Duration: 3 weeks
Define the Scope and List Every Stakeholder (Days 1-3)
Agree on what the map covers, then list everyone it touches.
- Write one sentence that describes the project, the decision or the change you are mapping.
- List stakeholders with your core team in a 45 minute session. Cover sponsors, users, teams that do the work, approvers, support, legal, finance, partners and customers.
- Ask four prompts: who pays, who approves, who uses it, who has to change how they work.
- Write names, not just departments. "Finance" is a group, but the person who signs off on the budget has a name.
Milestone: A list of named stakeholders, each with a role and a one-line description of how the project affects them.
Research What Each Stakeholder Needs (Days 4-8)
Find out what each key person wants, fears and expects.
- Hold short conversations with the 5 to 8 people who look most important. Aim for 20 to 30 minutes each.
- Ask the same three questions: what does success look like for you, what worries you, and how do you want to hear about progress.
- Read related documents too: past project reviews, team goals, emails about the project.
- Write one line per person: what they want, what they fear, how they like to get updates.
Milestone: Notes on needs and concerns for every stakeholder you might mark high power or high interest.
Plot the Power and Interest Grid (Days 9-10)
Place each stakeholder on the grid and agree on the result as a team.
- Score each person from 1 to 5 on power (can they approve, block or redirect the work?) and on interest (how much does the outcome change their day?).
- Put each name in one of the four quadrants.
- Add a mark for attitude: supporter, neutral or resistant.
- Review the grid with one or two teammates and talk through every name you placed differently.
Milestone: A grid with every stakeholder placed and an attitude marked, agreed by at least two people.
Turn the Map Into a Communication Plan (Days 11-13)
Decide who talks to whom, about what, and how often.
- Give each high power stakeholder one owner from the team.
- Set a channel and a rhythm for each quadrant, for example a weekly one-to-one, a fortnightly email, or a monthly summary.
- Write a key message for each resistant or neutral person with high power, tied to what they told you they care about.
- Add the first update dates to your project roadmap so they sit next to the work milestones.
Milestone: A communication plan listing each stakeholder's owner, channel, frequency and next contact date.
Run the First Cycle and Adjust (Days 14-21)
Use the plan for one week, then fix what did not work.
- Send the first round of updates and hold the planned one-to-ones.
- Track who replied, who raised concerns and whose attitude changed.
- Move people on the grid if you learn something new.
- Set a review date for the whole map, monthly or at each phase change.
Milestone: The first update round is done, the grid is updated, and the next map review is on the calendar.
What a Stakeholder Map Is
A stakeholder map is a picture of the people around a project, sorted by influence and involvement. The most common version is the power and interest grid, sometimes called the Mendelow matrix. It has two axes and four quadrants. Each quadrant comes with its own way of working with people.
A stakeholder map is not a list of everyone in the company. If a person cannot affect the project and is not affected by it, leave them off. A short, precise map helps more than a long, vague list.
- High power, high interest: manage closely. Sponsors, key approvers, the head of the team that has to change. Involve them in decisions, not just updates.
- High power, low interest: keep satisfied. Senior leaders and budget holders who are busy elsewhere. Short, regular summaries. Escalate only what needs their decision.
- Low power, high interest: keep informed. End users, support teams, frontline staff. Regular updates and a clear way to give feedback.
- Low power, low interest: monitor. People on the edges. Check in now and then in case their position changes.
How to Score Power and Interest Without Guessing
Placing people by gut feeling leads to arguments and mistakes. Use simple questions so two teammates reach the same score.
For power, ask: can this person approve or block the budget? Can they stop the launch? Do they control people or systems the project needs? Can they change the scope? As a practical rule, the more yes answers, the higher you place them on power. For interest, ask: will their daily work change? Will they be judged on the result? Have they asked about the project already? Do they lose something if it goes ahead?
Watch for formal power and real power. A manager may sign off on paper while a senior engineer or a long-serving team lead shapes what actually happens. If people regularly check with someone before they decide, that someone has power, whatever their title says.
Add Attitude: Supporters, Neutrals and Resistors
Power and interest tell you how much attention someone needs. Attitude tells you what kind. Mark each person as a supporter, neutral or resistant, based on what they said and did, not on what you hope.
The most important group is high power stakeholders who are resistant or neutral. They can slow everything down. For each of them, write down why they resist in their own words. Often the reason is concrete: they lose headcount, a deadline clashes with theirs, or they were not asked early enough. Answer that reason directly, in person, before it shows up in a meeting.
Supporters with high power are your allies. Ask them to speak for the project in rooms you are not in, and keep them informed so they never get caught off guard.
If the resistance comes from doubts about whether the project will work at all, test those doubts openly. Assumption mapping is a simple way to list and check them.
A Worked Example: An Internal Tool Rollout
Imagine a team replacing an old expense tool with a new one across the company. After day 3 the list has names from finance, IT, the leadership team, team managers, employees who submit expenses, and the vendor.
On the grid, the finance director lands in manage closely: high power, high interest, neutral. The chief operating officer lands in keep satisfied. Employees and the support desk land in keep informed. The vendor's account manager sits in monitor. The interviews show the finance director is worried about month-end closing during the switch.
The communication plan follows from that. The project lead meets the finance director weekly, and the go-live date moves away from month-end. The chief operating officer gets a five-line monthly summary. Employees get an email two weeks before the switch and a short guide on launch day. Each of these dates goes on the project roadmap, so updates are planned work, not afterthoughts.
How to Keep the Map Current
A stakeholder map goes stale fast. People change roles, priorities move, and a neutral approver can become a blocker after a budget cut. Review the map at fixed points: monthly on long projects, and every time the project enters a new phase.
Update it straight away after key events too: a new sponsor, a reorg, a missed milestone, or a heated meeting. Ask the owner of each key stakeholder one question in your weekly sync: has anything changed with this person? It takes two minutes and helps you catch shifts early.
Be careful where you store attitude notes. Writing "resistant, protects their team's budget" next to a name is useful for the core team, but it can hurt trust if it is shared widely. Keep two versions: a shared one with names, roles and update rhythm, and a private one with attitude and notes.
Common mistakes to avoid
- Mapping departments instead of people makes it unclear who to call, so write a named person for every key stakeholder.
- Building the map alone gives you blind spots, so plot the grid with at least one teammate who knows the organization differently.
- Treating the grid as the final product leaves it in a folder, so turn every high power name into an owner, a channel and a date.
- Sending the same update to everyone tires busy leaders and leaves users without enough detail, so match the depth and rhythm to each quadrant.
- Ignoring quiet resistors lets objections show up late, so ask neutral people with high power directly what worries them.
- Never revisiting the map leaves you working from old assumptions, so set a fixed review date and update after every major change.
Frequently asked questions
What is stakeholder mapping in project management?
Stakeholder mapping is the process of identifying the people who can affect or are affected by a project, then sorting them by power and interest. The result shows how closely to involve each person. Project managers use it to plan communication and to spot risks from people before they become problems.
What are the four quadrants of a stakeholder map?
The four quadrants are manage closely (high power, high interest), keep satisfied (high power, low interest), keep informed (low power, high interest) and monitor (low power, low interest). Each one has its own level of contact. Most of your time goes to the manage closely quadrant.
How often should you update a stakeholder map?
Review it at least monthly on long projects and at every phase change. Also update it after events that shift power or attitude, such as a new sponsor, a reorganization or a missed milestone. A quick weekly check by stakeholder owners keeps it accurate.
What tool can I use to make a stakeholder map?
A whiteboard, sticky notes, a spreadsheet or a slide in PowerPoint all work for the grid. What matters more is linking the map to your plan: put stakeholder updates and reviews on the same roadmap as your project milestones so they happen on time.
Who should be involved in stakeholder mapping?
Involve the project lead and two or three core team members who know different parts of the organization. Add the sponsor for a quick review of the high power names. Keep attitude notes within this small group.