Isaiah / Guides / Stakeholder mapping

Stakeholder mapping: how to map a decision before you act

Updated 2 November 2026 · Huper.Technology

A stakeholder map shows who a decision touches, how much each group can do about it, and how the groups connect. Done well, it tells you where the pushback will come from before anything is public.

In short

  • Map one decision at a time. A map of "our stakeholders" in general is too vague to act on.
  • Use three views: a power-interest grid to sort, a salience check to prioritise, and a relationship map to see who will influence whom.
  • Record each group's likely position and what it would need to hear, with the evidence behind your view.
  • A map shows positions before you act. It does not show how groups will react to your move or to each other. Test that separately.

What stakeholder mapping is

Stakeholder mapping is the process of identifying everyone affected by a decision, judging how much each can influence the outcome, and laying the result out so the team can agree on priorities. The output is usually a grid, a network diagram, or a table. The page matters less than the thinking: who is in the field, what they care about, and what they can do.

It sits inside stakeholder analysis, which is the wider job of understanding interests and positions. Mapping is the part that turns that understanding into a picture the whole team, and later the board, can read in one go.

Three models worth knowing

The power-interest grid

The most common model. Plot each stakeholder on two axes: how much power it has over the outcome, and how much interest it takes in it. The four quadrants suggest a default treatment.

QuadrantTypical treatmentExample for a branch-closure decision
High power, high interestManage closely. Involve early, brief in person.Banking regulator, employee union
High power, low interestKeep satisfied. Brief before they hear it elsewhere.Major institutional shareholders
Low power, high interestKeep informed. Explain the decision and the support on offer.Older customers in affected towns
Low power, low interestMonitor.Customers who bank only online

The grid is fast and easy to explain. Its weakness is that it treats power as fixed. A low-power group with high interest can gain power quickly if a journalist or a politician picks up its cause. Our power interest grid guide covers scoring and a worked example of groups moving quadrant after an announcement.

The salience model

Ronald Mitchell, Bradley Agle and Donna Wood proposed that a stakeholder's claim gets attention according to three attributes: power (can it impose its will), legitimacy (is its claim seen as proper), and urgency (does its claim demand immediate attention). A group with all three is a "definitive" stakeholder and moves to the top of the list.

The model is useful when the grid gives you too many high-priority groups. It also explains why a small group with an urgent, legitimate grievance can dominate the news for a week despite having little formal power.

The relationship map

A network diagram: stakeholders are nodes, and lines show who influences, funds, reports on, or allies with whom. This is the view most teams skip, and it is the one that explains most surprises. Regulators read the press. Employees talk to journalists. Investors watch what politicians say. A decision rarely meets each group separately; the groups meet each other.

How to map stakeholders for one decision

  1. Write the decision in one sentence. "We will close 40 branches over 12 months and move those customers to digital and partner channels" maps very differently from "we are reviewing our branch network". Be specific about what changes, for whom, and when.
  2. List the groups, then the named actors. Start broad: investors, regulators, employees, customers, media, communities, government, partners, competitors. Then name the actors inside each group who carry weight: the union, the sector regulator, the two reporters who cover you, the local MP.
  3. Score power and interest. Agree a simple scale and score as a team. Where people disagree, write down why. The disagreement is often more useful than the score.
  4. Check salience. For each high-priority group, ask whether its claim is legitimate and whether it is urgent. That tells you the order in which to engage.
  5. Draw the relationships. Who listens to whom? Who has allied before? Who would gain from opposing you publicly?
  6. Record position and need. For each group: likely position on the decision (support, neutral, oppose), what would move it, and what it needs to hear first. Note the evidence for each judgement.
  7. Mark likely coalitions and flashpoints. Where could two opposed groups find common cause? Which group's reaction would trigger another's?

The figures in the example sentence above are illustrative. Use your own decision's specifics; vague decisions produce vague maps.

Worked example (hypothetical)

A regional lender plans to close a set of rural branches. On the grid, the regulator and the union sit in the top right, shareholders top left, and affected older customers bottom right.

The relationship map changes the picture. Older customers have little power alone, but local media cover branch closures, and local politicians read local media. Once the story runs, the regulator faces questions about access to cash. The bottom-right group becomes the route by which the top-right group's position hardens.

The line worth taking into the room: "If we brief the regulator after the customers, we lose the framing."

A stakeholder mapping template

Copy this table into a document or spreadsheet. One row per actor, not per group, once you get past the first pass. For a fuller version with position gaps, owners and confidence ratings, see the stakeholder analysis template.

ColumnWhat to write
StakeholderGroup and named actor, e.g. "Regulator: banking supervision team"
Power1–5. Can it stop, delay, fine, or change the decision?
Interest1–5. How much does the decision affect it, and does it know yet?
Legitimacy / urgencyYes / no for each, with one line of reasoning
Likely positionSupport, neutral, oppose, and how firmly
Linked toThe other stakeholders it influences or listens to
What moves itThe concern, commitment or evidence that would shift its position
First messageWhat it needs to hear, from whom, and in what order relative to others
EvidencePast statements, filings, coverage, or conversations behind the judgement

Where a static map falls short

A stakeholder map is a snapshot of positions as you understand them before you act. Three things it cannot show:

Teams cover this gap with war-gaming sessions, red teams playing the hardest stakeholders, or advisers who have seen similar decisions play out. These work, but they are limited to the people in the room and what they can imagine on the day.

Testing the map before you act

Isaiah takes the next step from the map. You bring the decision and the documents that frame it. Isaiah builds the stakeholder field from that material and fresh research, simulates those stakeholders responding to your move and to each other in simulated public discourse, and tests candidate counter-moves. You get a board-ready report covering the stakeholder landscape, the narratives that spread, the risks and the moves that backfire, with each finding traced to quotes from named simulated stakeholders. The simulation stays open so you can question any of them.

It is a stress-test, not a forecast. Simulated stakeholders are not survey respondents, and the output does not replace your advisers or your judgement. It shows you the reactions worth preparing for, while the decision is still private.

Frequently asked questions

What is the difference between stakeholder mapping and stakeholder analysis?

Stakeholder analysis is the wider work of understanding who is affected by a decision, what they want and how much they can do about it. Stakeholder mapping is the part of that work that puts the answers on one page, usually as a grid or a network, so the team can see priorities and relationships at a glance.

How often should a stakeholder map be updated?

Treat it as a working document for the life of the decision. Revisit it when the decision changes, when a new actor appears, and after any public moment such as an announcement, a leak or a regulator's comment. A map drawn once at the start of a project goes stale quickly.

Which stakeholder mapping model should I use?

Use the power-interest grid to sort a long list quickly, the salience model when you need to decide whose claims to act on first, and a relationship map when the risk is that groups will influence each other. Most decisions with public exposure need all three views.

Can stakeholder mapping predict how people will react?

Not on its own. A map records positions as you understand them before you act. Reactions depend on how stakeholders respond to your move and to each other. To explore that, teams use war-gaming sessions, red teams, or a simulation of the stakeholder field, and treat the output as scenarios to test rather than forecasts.

Have a decision coming up?

Tell us what it is. We will set up a private stress-test on it and show you how the stakeholder field reacts before anything goes public.

Request a demo

Related

Sources

  1. Mitchell, R. K., Agle, B. R., & Wood, D. J. (1997). Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts. Academy of Management Review, 22(4), 853–886. doi.org/10.2307/259247 (checked 2 November 2026)