"The plan is good. It is the people that are hard."
Every change program leader has said some version of this, usually around week 10 of a program that was supposed to take 12.
The plan is almost always solvable. The stakeholder layer is where change programs die, quietly, a dozen unaddressed frictions at a time.
Stakeholder mapping is the single cheapest intervention you can run, and most teams do a version of it that is not useful. Here is the version that is.
Why most stakeholder maps fail
Three common failures.
1. They list people, not positions. A list of names is not a map. It does not tell you what the person believes, what they stand to lose, or how they will move.
2. They use influence vs. interest as the only axis. Classic 2x2. Useful once. Not enough to actually plan a sequence of moves. Two dimensions cannot carry the weight of a complex change.
3. They are done once at kickoff. Stakeholder positions move. The map has to move with them, or you are navigating by a 4-month-old chart.
Fix all three.
The map that works
We use a four-dimension map. It is lightweight enough to maintain and rich enough to make real decisions from.
For every named stakeholder or stakeholder group:
1. Position: on a 5-point scale: Blocker, Sceptic, Neutral, Supporter, Champion 2. Influence: on the specific decision or change you are trying to land 3. What they stand to lose: named explicitly. Status, headcount, work, control, reputation. 4. What they need to move one step: the specific thing that would shift them from, for example, Sceptic to Neutral
The fourth column is the one most maps miss. Without it, you have a diagnosis without a prescription.
Build the map
Allow two weeks. You cannot do this well in a two-hour workshop with the PMO.
Week 1: Interview. Have 20 to 30 minute structured conversations with 10 to 20 named stakeholders across the affected system. Ask four questions:
- What do you think this program is trying to do?
- If it lands well, what is different for you and your team?
- What worries you about it?
- What would you need to see to back it with energy?
Take detailed notes. Do not try to persuade during the interview. Listen.
Week 2: Triangulate. Talk to people who know the stakeholders, peers, reports, sponsors. Their read is often sharper than the stakeholder's own.
Assemble the map. Be honest. If a sponsor is secretly a sceptic, the map has to say so, even if the conversation about the map is uncomfortable.
Design the sequence
Now the map starts earning its cost. For each stakeholder, ask:
- What position do we need them in for this to land?
- What is the minimum move required? (Often "Sceptic to Neutral" is enough. You do not need every stakeholder to be a Champion.)
- What is the smallest intervention that would move them one step?
Interventions are rarely communications. More often they are:
- A 1:1 with the sponsor, specifically to address the thing they stand to lose
- A role on the program that gives them visible ownership of a piece of it
- A small win they can point to with their own team
- Direct engagement on the design so the change is not happening "to" them
- Removing a specific constraint that is making their life harder (the simplest and most effective)
Sequence the interventions. Do the stakeholders whose influence is highest first, not the ones you most enjoy talking to.
The groups most change programs miss
Three groups are systematically under-mapped.
1. Middle managers. They are usually the biggest source of real risk. They are closest to the change, have the least power to shape it, and carry the most day-to-day responsibility for making it work. Map them individually, not as a population.
2. Informal opinion leaders. Every org has people who are not senior on the org chart but whose opinions shape others. They are often tenured ICs, a veteran project manager, a long-serving team lead. If they move, the cohort moves. If they do not, the cohort will not. Name them specifically.
3. Adjacent function leaders. The functions whose work your change affects indirectly, IT, finance, legal, risk. They often hold veto power and are treated as an afterthought. Map them as carefully as your direct stakeholders.
The review cadence
Revisit the map every two to four weeks while the program is live. Not once.
A simple review looks like this, 30 minutes:
- Walk through the named stakeholders in order of influence
- For each: did we make the move we planned? What happened? What is the current position?
- Any surprises? New entrants?
- What are the 3 to 5 stakeholder moves for the next two weeks?
This is not bureaucracy. It is the early-warning system for the program.
A small note on ethics
Stakeholder mapping is the opposite of manipulation when it is done well. You are not looking for leverage to push people where you want them. You are trying to understand what they need, what they stand to lose, and whether the program design actually accommodates those legitimate concerns.
Sometimes the result of a good map is that the plan changes. That is not a failure of the map. That is the map doing its job.
A deeper playbook
The method above comes from the longer Brand Foundations and Change playbook we use internally. It covers stakeholder mapping, brand foundations, and communications strategy together, because in practice, these three sit on top of each other.
Grab the Brand Foundations, Stakeholder Mapping & Comms Strategy playbook if you want the full version with templates and worked examples. It is the same document we pull out at the start of a new program internally.
Welcome to better.