Stakeholder Map: How to Build One in 4 Steps (With Template)

A stakeholder map sorts everyone with a stake in your project into a simple picture of who matters most and how to engage them. Done well, it prevents the two most common project failures: blindsiding an executive who should have been consulted, and over-communicating with people who only wanted a newsletter.

This guide covers the 4-step process to build one, the methods to choose from (Power-Interest Grid is the default), and the honest failure modes nobody else writes about. The builder below lets you plot a live Power-Interest Grid in under two minutes.

What Is a Stakeholder Map?

A stakeholder map is a visual that plots everyone connected to your project against two or three dimensions that drive how you engage them. The most common version is a 2x2 grid: Power on one axis, Interest on the other. Each person or group goes into one of four quadrants, and the quadrant tells you the engagement strategy. It sits alongside your project management framework as one of the foundational planning artifacts.

The foundation comes from academic work on stakeholder theory. R. Edward Freeman popularized the core definition in 1984.

"A stakeholder is any group or individual who can affect or is affected by the achievement of the organization's objectives." - R. Edward Freeman, Strategic Management: A Stakeholder Approach (1984)

Seven years later, Aubrey Mendelow published the Power-Interest Grid (sometimes called Mendelow's Matrix), which remains the default tool for classifying stakeholders. Other methods like the Salience Model and Onion Diagram exist for specific situations, but 80 percent of project teams only need the grid.

The 4-Step Stakeholder Mapping Process

Every stakeholder map goes through the same four steps. The first two are the heavy lifting. Steps three and four are where most teams rush and end up with a map that looks clean but misrepresents reality.

Step 1. Identify stakeholders. List every individual or group with a stake in the project outcome. Go wide. Include the obvious names (client, sponsor, core team) and the less obvious ones (legal, finance, end users, adjacent teams, vendors). A first pass should produce 15 to 25 names for a medium project.

Step 2. Assess power and interest. For each stakeholder, score Power (can they change the outcome, fund it, or kill it?) and Interest (do they care about the result and want to stay involved?). Use high or low for each. Resist the urge to invent medium scores to avoid hard conversations.

Step 3. Plot on the grid. Place each stakeholder in one of four quadrants: Manage Closely, Keep Satisfied, Keep Informed, or Monitor. Clusters are normal. If every name lands in Manage Closely, you have not scored honestly and the map is useless.

Step 4. Define engagement per quadrant. Write one sentence per quadrant covering frequency, channel, and owner. "Weekly one-on-ones with the client (Project Lead owns)" beats "high touch comms." Specificity is what turns the map from a poster into a plan.

Stakeholder Mapping Tools and Methods

The Power-Interest Grid is the default stakeholder mapping tool, but eight methods cover most projects. Pick based on the shape of your stakeholder set, not the method that looks most sophisticated.

If you are unsure, start with the Power-Interest Grid. Run it for 30 minutes with your team. If it feels like power and interest are not the right axes, switch to the Salience Model. Do not try to use all eight methods on the same project. The deeper guides below explain each method in turn so you can pick on shape, not on which method sounds most rigorous.

"Key stakeholders must be satisfied at least minimally, or public policies, organizations, communities, or even countries and civilizations will fail." - John M. Bryson, Professor, University of Minnesota Hubert H. Humphrey School of Public Affairs

Power-Interest Grid (Mendelow)

Aubrey Mendelow introduced the Power-Interest Grid at the 1991 International Conference on Information Systems. The framework plots stakeholders on a 2x2 by their power to influence the project and their interest in its outcome. Four quadrants follow: Manage Closely, Keep Satisfied, Keep Informed, and Monitor.

The grid is the default opening move for most teams because it is fast to run, easy to communicate, and produces clear engagement strategies per quadrant. Skip it when the shape of your stakeholder set is about urgency or legitimacy.

Salience Model (Mitchell, Agle, Wood)

Ronald Mitchell, Bradley Agle, and Donna Wood published the Salience Model in the Academy of Management Review in 1997. The model classifies stakeholders by three attributes (power, legitimacy, urgency), which intersect into seven types from Dormant to Definitive.

The strength is that it captures the politically complex case where a stakeholder has a valid claim but no formal authority. The cost is the three-attribute scoring, which adds time most projects do not need. Use the Salience Model when 2x2 placement feels wrong because the grid misses what makes a stakeholder salient.

Influence-Impact Grid

The Influence-Impact Grid appears in PMI's PMBOK Guide and is often used in change management. The two axes are influence (can shape the outcome) and impact (will be affected by the outcome). Same shape as the Power-Interest Grid, different question.

The model is most useful in change programs where some stakeholders shape the outcome but are not affected, and others are affected but cannot shape it. The fourth-quadrant trap is real: low-influence, high-impact stakeholders are often the ones whose resistance kills the rollout. Skip when influence and impact track together.

Onion Diagram (Alexander)

The Onion Diagram has roots in Suzanne and James Robertson's Mastering the Requirements Process (1999). Ian Alexander popularized it in product and requirements engineering in the early 2000s. Stakeholders sit in concentric rings around the project, from the product itself out to the wider environment (regulators, market, society).

The onion is best for early discovery, when you do not know enough to score stakeholders on power or interest yet. It tells you who might care, not what to do with them. Once the project starts, switch to a 2x2 method.

RACI Matrix

RACI has roots in 1970s consulting practice and is now codified in PMI's PMBOK Guide. It assigns each stakeholder one of four roles per task or decision: Responsible (does the work), Accountable (owns the outcome), Consulted (input invited), Informed (kept in the loop).

Strictly, RACI is not a stakeholder mapping tool. It assumes you already know the stakeholders and now want to clarify who decides what. In practice, teams run RACI right after the Power-Interest Grid: the grid tells you who matters, RACI tells you what role each one plays.

Stakeholder Circle (Bourne)

Lynda Bourne developed the Stakeholder Circle during her doctoral research at RMIT, then published it in Stakeholder Relationship Management (Gower, 2009). The model visualizes the top 15 stakeholders as concentric arcs scaled by power, proximity, and urgency.

The Stakeholder Circle is heavier than a 2x2 and is built for ongoing programs and portfolios where stakeholder relationships persist over months. For a one-off project, it is overkill. For a multi-year client engagement, the circle keeps the team disciplined about who moves the needle each quarter.

"Recognition that relationships with stakeholders are most important to success." - Dr. Lynda Bourne, CEO, Stakeholder Management Pty Ltd

Three-Dimensional Grid (Murray-Webster & Simon)

Ruth Murray-Webster and Peter Simon published the Three-Dimensional Grid in PM World Today (2006) as an extension of the Power-Interest Grid. The third axis is attitude, broken into supportive, neutral, and hostile.

The cube produces a richer map. A high-power, high-interest, hostile stakeholder is a different problem than a high-power, high-interest, supportive one, even though both sit in the Manage Closely quadrant of a flat 2x2. Use the third dimension when attitude flips outcomes (M&A, restructuring, leadership change). Skip when attitudes are uniform across the stakeholder set.

Force Field Analysis (Lewin)

Kurt Lewin introduced Force Field Analysis in Field Theory in Social Science (1951). The framework lists the driving forces pushing for a change on one side and the restraining forces pushing against it on the other.

Strictly, this is a change-management framework, not a stakeholder map. It earns its place in the toolkit because the forces are usually attached to specific stakeholder groups, which reframes the conversation away from authority and toward momentum. Use Force Field when the project is an adoption play. Skip when the question is "who has the authority to greenlight this."

Stakeholder Map Template

Our strategy template library includes planning frameworks, and the same principles apply to a stakeholder map. You need three artifacts: the list, the grid, and the engagement plan per quadrant. Here is the minimum structure any tool can produce.

Stakeholder list. A row per stakeholder with columns for name, role or title, power score (high or low), interest score (high or low), and assigned quadrant. This is the raw data the grid visualizes.

The grid itself. A 2x2 with Power on the vertical axis and Interest on the horizontal. Each quadrant holds the names that scored into it. The builder above produces this automatically from the list.

Engagement plan. One row per quadrant with columns for frequency, channel, owner, and key message. This is what turns the grid into actual behavior change.

Worked Example: Website Redesign

Here is a filled stakeholder map for a 6-week website redesign. Real reasoning per placement, not placeholder labels.

That is 5 roles across 4 quadrants. Real projects often have 10 to 20 stakeholders. The logic scales because the engagement strategy per quadrant is fixed. Only the names change.

When Mapping Is Useful (and When It Is Theater)

Stakeholder mapping works when the project meets three conditions: it involves 5 or more stakeholders, spans multiple weeks, and has at least one stakeholder whose engagement will make or break the outcome. If any of those is missing, mapping adds ceremony without clarity.

The cost of skipping the exercise is rarely visible at kickoff and almost always visible at month three. PMI's 2013 Pulse of the Profession found that 56% of every dollar at risk on a project comes down to ineffective communications. Most of that risk traces back to stakeholders who were never properly identified or engaged.

Skip mapping on solo or small-team projects. Under 5 stakeholders, everyone knows who cares about what. A formal grid is overhead.

Skip mapping on short projects (under 2 weeks). The time to build and maintain the map exceeds the value. A one-line "owner per deliverable" note is enough.

Skip mapping on projects with one dominant stakeholder. When one client or one executive drives everything, the map is a single quadrant with everyone else in Monitor. Do not dress that up as analysis.

The most common theater pattern: teams build the map in a kickoff workshop, post it to a wiki, and never reference it again. A stakeholder map is a living document. If you do not update it when someone leaves, joins, or shifts priority, the map is stale within a month.

How to Run a Stakeholder Mapping Workshop

A good stakeholder mapping workshop takes 60 minutes with 4 to 8 people from the project team. Inviting every stakeholder defeats the purpose. You are assessing them, not negotiating with them.

Teams that run this workshop at project kickoff and revisit it monthly have fewer last-minute stakeholder blow-ups than teams that skip it or do it once.

From Map to Execution

The hardest part of stakeholder mapping is not building the map. It is making the map influence daily behavior after the workshop ends. Most stakeholder maps become wiki artifacts that nobody consults when a decision needs their input. Pin the map plus an engagement plan next to the project work, not in a separate slide deck.

The fix is to keep the stakeholder map close to the tasks and conversations it governs. If the map lives in one tool, the project runs in another, and the client chat lives in a third, the map will rot. Teams that co-locate their stakeholder map with their stakeholder communication, RACI matrix, and project plan keep it alive because they see it daily.

What we see on Rock. Teams that use Rock to run client projects keep the stakeholder map as a pinned note in the project space. The quadrant assignments become follower lists on tasks.

Manage Closely stakeholders get added as followers on milestone tasks. Keep Informed stakeholders get added to the weekly status note. Monitor stakeholders only see the final launch announcement.

That way the map is not a separate document to maintain. It is the routing logic that decides who sees what.

Frequently Asked Questions

Is a stakeholder map the same as a stakeholder matrix? Mostly yes. Most teams use the terms interchangeably. "Map" tends to describe the output (the 2x2 with names placed), and "matrix" tends to describe the method (the framework with axes and quadrants). When someone asks for a stakeholder matrix, they almost always mean the Power-Interest Grid.

How often should I update a stakeholder map? Monthly for projects over 3 months. Biweekly for projects under 3 months. Every time someone joins or leaves the project, update the map the same day.

What if a stakeholder does not fit cleanly in one quadrant? Put them in the higher of the two. A borderline high-power stakeholder goes into Manage Closely or Keep Satisfied, not Keep Informed. The cost of under-engaging is higher than over-engaging.

Do I need special software to build a stakeholder map? No. A whiteboard or a shared doc is enough. The tool does not matter. What matters is that the map stays near the tasks and conversations it governs.

What are the 4 quadrants of stakeholder mapping? The four quadrants come from the Power-Interest Grid. They 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 quadrant maps to its own engagement strategy.

What is the difference between stakeholder analysis and stakeholder mapping? Stakeholder analysis is the broader practice of identifying stakeholders and understanding their interests, influence, and likely behavior. Stakeholder mapping is one technique within that practice, specifically the visual placement of stakeholders on a 2x2, onion diagram, or other framework. Mapping is the deliverable; analysis is the underlying work.

What are the 5 stakeholder analysis methods? The five most common are the Power-Interest Grid, the Salience Model, the Influence-Impact Grid, the Onion Diagram, and the Stakeholder Circle. Most strategic toolkits add RACI, the Three-Dimensional Grid, and Force Field Analysis as related techniques, which is why this guide covers eight.

Why is stakeholder mapping important? Stakeholder mapping prevents the most common project failure mode: discovering halfway through that a critical stakeholder was unmanaged. It forces the team to name everyone affected, score their power and interest, and assign engagement before the project encounters resistance. Skipping the exercise is cheap at kickoff and expensive at month three.

Stakeholder maps only work if they stay close to the work. Rock combines chat, tasks, and notes in one workspace so your stakeholder map, your project plan, and your client conversations live together. One flat price, unlimited users. Get started for free.