Know what each stakeholder needs before you ask for support
List everyone a project affects, work out what each person cares about and who they listen to, and plan how you will approach each one.
See it in action
A stakeholder map for moving a company from its own servers to the cloud, with each group's influence and the plan for approaching it.
How it works
Describe the project and the change it asks people to accept. Each stakeholder or group gets its own branch, and what you learn about them sits underneath.
-
List the stakeholders. Ask who the project affects, grouped by role: sponsors, decision makers, contributors, affected teams and outside parties. Add a branch for each group.
-
Work out what each one cares about. Under each stakeholder, ask what they are likely to worry about. The CFO asks about cost, the engineering lead about disruption, the security team about compliance.
-
Find who influences whom. Influence does not always follow the org chart. Under a group, ask questions like “Who does the CEO listen to on infrastructure?” and add a note with what you know first-hand.
-
Plan each conversation. Under each stakeholder, ask what message, format and timing will work, and who should deliver it.
Why a map instead of a power-interest grid
A power-interest grid puts each person in one of four boxes. It does not say why someone is uninterested or what would change their mind. On the map, each person has a branch for their concerns, their relationships and your plan for them.
Example
Say you are leading an internal platform migration that touches 15 people across four departments. Under affected teams, you note that the QA lead also speaks for a group of senior engineers who doubt the migration. That changes the plan: you meet her one-on-one first, answer her team’s concerns, and ask for her help before the wider announcement.