Stakeholder Mapping
Identifying everyone who has a stake in a problem, and characterising each by their power, interest, and attitude — so you research the right range of people and engage each one well.
The team that only researches the obvious stakeholders will always be surprised by the non-obvious ones — usually at the moment they matter most.
What it is
Not a list of who to consult. A cast of everyone whose behaviour, needs, or opposition shapes what a solution must do.
Stakeholder Mapping is the process of identifying every person or group with a stake in the problem a team is trying to solve — and characterising each by their power over the outcome, their interest in it, their current attitude toward it, and their influence over others. The result is a structured cast of actors that the team uses to guide who to research, who to engage, and who needs to be managed or addressed before a solution can actually reach the people it was designed for.
It is easy to mistake for a reporting or communication exercise — a list of who will be told about the work. That misreads it entirely. Its purpose is research and strategy: to ensure the team understands the full range of people and organisations who will shape the problem, use the solution, resist the change, or feel its effects downstream. A stakeholder map that only names the obvious actors — the direct users, the decision makers, the budget holders — is incomplete. The most important stakeholder in a project is frequently the one no one in the initial team thought to list.
The four attributes — power, interest, attitude, and influence — are not fixed. They are a snapshot that must be updated as the work progresses and as the team learns more. A stakeholder who appears neutral at the start of a project can become a blocker when their informal authority is threatened. A downstream-affected group who seemed irrelevant can turn out to be the most powerful signal of whether the solution is right. The map is a living research tool, not a project management diagram.
Sort the cast. Change the priority order.
The same eight stakeholders reveal completely different research priorities when sorted by different attributes.
Sort by power × interest to see who needs the most active management. Sort by attitude to see who to mobilise and who to plan around. Sort by influence to see whose opinion others will follow. Click any card to see what makes this stakeholder matter.
END USER
Primary user
DECISION MAKER
Authority holder
BUDGET HOLDER
Resource gatekeeper
REGULATOR
Rule-setter
FRONTLINE STAFF
Daily implementer
DOWNSTREAM
Indirect recipient
SILENT BLOCKER
Hidden obstacle
ADVOCATE
Community voice
SELECT A CARD TO SEE FULL ATTRIBUTES — THEN SORT THE CAST BY POWER, ATTITUDE, OR INFLUENCE
When to deploy it
For defining who to research. For planning who to engage. For surfacing hidden resistance before it surfaces itself.
Use it when
- →You are beginning a research phase and need to decide who the team must understand before designing anything.
- →You need to plan engagement: who to involve closely, who to keep informed, who to satisfy, and who to monitor.
- →A previous initiative failed or stalled late in implementation and you suspect a stakeholder who was never adequately engaged.
- →The solution requires behaviour change from people who did not choose the change — and you need to understand who will resist and why.
- →You are entering an unfamiliar domain and need to build a picture of whose knowledge, approval, and cooperation the work depends on.
Do not lean on it when
- ×You would use it only as a project communication plan — listing who to send updates to. That is stakeholder management, not stakeholder mapping. The method's value is in research coverage, not comms logistics.
- ×You treat it as fixed. Stakeholder maps decay; as the work progresses and relationships become clearer, the map must be updated. A map that was correct at week one may be badly wrong by week six.
- ×You use it to confirm the cast you already had in mind. The value is in the non-obvious stakeholders the facilitated session surfaces — not in documenting the obvious ones.
The honest limit: a stakeholder map is only as good as the session that produces it. A map built by one person at a desk will reflect one person’s field of view. A map built by a cross-functional team in a facilitated session, where each person is asked to challenge and extend the list, reliably surfaces people that no individual team member would have named alone. The session design matters as much as the framework.
How it works
Seven moves, from an initial list to a living research and engagement plan.
Start with who is already in the room — then push past them.
Begin by listing the stakeholders the team already knows: the direct users, the decision makers, the budget holders. This is the minimum viable cast. The method's real work starts next: systematically push the list past the obvious. Who is affected downstream? Who has informal influence that doesn't appear on an org chart? Who has historically opposed similar initiatives and is likely to do so again? Who has context no one on the team currently has?
Characterise each stakeholder by four attributes.
Assign each stakeholder a reading on power (their ability to advance or block the outcome), interest (how much they care about the problem or solution), attitude (supporter, neutral, or blocker), and influence (their ability to shape others' opinions). These are working hypotheses, not facts — they should be revised as the team learns more. They exist to structure the prioritisation, not to categorise people permanently.
Sort the cast to reveal priority and risk.
Map the cast onto a power-interest grid: high-power, high-interest stakeholders need the most active engagement; high-power, low-interest stakeholders need to be kept satisfied; low-power, high-interest stakeholders need to be kept informed. Separately, surface the blockers and plan around them. Surface the high-influence stakeholders and understand who listens to them.
Design a research plan from the map.
Use the map to decide who the team needs to understand deeply, not just consult. The most valuable research subjects are often the stakeholders who are non-obvious, who have high interest but low formal power, or who are downstream recipients whose experience reveals systemic failure. Do not only research the most powerful or most available stakeholders — that produces a map of what the loudest voices think, not what the problem actually is.
Design an engagement plan from the map.
Plan specifically: how to involve high-priority stakeholders, how to keep others informed without consuming their attention unnecessarily, and how to surface and address blockers before they can act. The plan should name real next steps — who talks to whom, by when — not describe a communication philosophy.
Revisit the map as the work progresses.
Stakeholder relationships shift. A neutral middle manager can become an active blocker when they understand what the project actually implies for their team. A downstream-affected community can become an active advocate when they are meaningfully involved. The map should be reviewed at each major phase gate, not archived after the first session.
Treat non-obvious stakeholders as primary, not secondary.
The most common and most consequential error in stakeholder mapping is relegating the non-obvious actors to a "secondary considerations" footnote. The stakeholders who are not obviously relevant are often the ones who reveal the most important constraint, the most important unmet need, or the most important implementation risk. Treat them as research priorities, not as edge cases.
Best practices
What separates a map that changes the research plan from one that documents the obvious.
When it goes well
- ✓The session is cross-functional: different team members see different stakeholders, and the combination consistently surfaces actors no individual would have named alone.
- ✓The facilitation actively pushes past the obvious — asking "who else?" at every step until the cast genuinely surprises the room.
- ✓Non-obvious stakeholders are treated as research priorities, not secondary considerations. They are in the research plan, not the footnote.
- ✓The map is treated as a hypothesis, not a fact. Each stakeholder's attributes are provisional and revisited as the team learns more.
- ✓The engagement plan that follows is specific: who speaks to which stakeholder, by what method, and by when.
The mistakes, and how to avoid them
Stopping at the obvious cast.
Listing only the well-known direct users, decision makers, and budget holders produces a map of the people the team was already aware of. The method's value is in discovering who else matters. A session that does not surprise the room has not been pushed far enough.
Building the map in isolation.
A map built by one person reflects one person's field of view. The cross-functional facilitated session is not optional — it is the mechanism for aggregating knowledge that no single team member has. Different functions see different actors, and the combination reliably surfaces what any individual would miss.
Treating blockers as people to avoid.
A stakeholder with a blocking attitude is an early warning, not a threat to be ignored. The goal is to understand why they are opposed — what fear, incentive, or genuine concern drives the resistance — and address it before implementation begins. Blockers who are not engaged become the reason good solutions fail.
Confusing stakeholder mapping with stakeholder management.
Comms planning — who to send the update to and how often — is a downstream activity. Stakeholder mapping is about research coverage and strategy: who the team needs to understand, and how to engage each person in a way that reflects their actual role and motivation.
Filing the map after the first session.
Stakeholder relationships change throughout a project. A map that was accurate in week one is often wrong by week eight. Revisit it at each phase gate: update attitudes, add newly discovered actors, remove those who are no longer relevant. The map is a living tool.
Logistics
Running a session that surfaces the whole cast, not just the cast the team already had.
Stakeholder mapping typically takes one to two hours for an initial session, with a small cross-functional team of two to six people. The output is a living document — the initial map is a first draft, not a final answer. Plan for at least two or three revisit sessions as the work progresses and the team learns more about who actually matters.
Facilitate, do not just document
The session's value is in the conversation, not in writing names on a 2x2. The facilitator's job is to keep pushing past the obvious — asking "who else?" after each category of stakeholder until the room has genuinely exhausted the cast. A session where no one in the room is surprised by the final map has not been facilitated well.
Use triggering questions to surface non-obvious actors
Reliable questions for extending the cast: Who feels the effects of the solution but has no direct relationship with the team? Who has historically resisted changes like this, and why? Whose informal opinion does this organisation tend to follow? Who delivers or implements the adjacent systems that this solution depends on? Who is typically forgotten in projects like this, and what happens when they are?
Score attributes as a team, not in advance
Power, interest, attitude, and influence should be assigned in the session, not prepared beforehand. The disagreements that arise — "I think she's a supporter but you think she's neutral" — are the valuable conversation. They surface differences in perception that need to be resolved before the team commits to an engagement strategy.
Plan the follow-on research in the same session
While the map is fresh and the team is aligned, commit to a research plan: which stakeholders need deep qualitative research, which need a shorter conversation, and which can be monitored rather than engaged directly. Move from map to plan in the same session so that the cast produces a concrete next step.
Schedule the revisit before the session ends
Book the first map review into the project calendar before the session closes. Without a specific scheduled date, revisit sessions do not happen. The map becomes a historical document rather than a living tool, and the team is surprised by the stakeholders who changed.
AI and this method
AI generates the obvious cast in seconds. The non-obvious cast requires the people in the room who have lived in the domain.
Toggle between modes to see who AI surfaces reliably, and where the most important stakeholders — the non-obvious ones who change the brief — tend to appear only in a facilitated human session.
FULL CAST
A well-facilitated session surfaces all eight stakeholder types — including indirect recipients, hidden blockers, and community advocates who fall outside the team's usual field of view.
NON-OBVIOUS FIRST
The most valuable research subjects are often the least obvious: the downstream recipient who first reveals downstream harm, the silent blocker who will stall implementation if not addressed early.
LIVE ATTRIBUTES
Power, interest, attitude, and influence are nuanced judgements that require conversation, contextual knowledge, and domain expertise — not pattern-matching from public data.
In-depth example
The Swiffer: the stakeholder that changed the design brief.
A product team mapping stakeholders for a floor-cleaning product pushes past the obvious users and discovers that the non-obvious group — elderly and limited-mobility users — reveals the job was never about cleaning power. Toggle between the human-led session and a hypothetical AI-first approach to see what each produces.
Step 1: Map the obvious cast
The team began where any product team would. The obvious stakeholders were documented first: the primary user (the person who cleans the floors), the retail buyer (the category manager who decides whether the product reaches the shelf), and the safety regulator (the body governing chemical and product standards).
Mapped by power and interest, the retail buyer and regulator required proactive management. The primary user — the person whose behaviour the product had to change — was where the team needed to focus research. Standard. Expected. And not yet revealing anything that would change the product.
Step 2: Push past the obvious — who else has a stake?
The facilitator kept pushing: who else interacts with floor cleaning, even indirectly? The cast expanded.
ELDERLY & LIMITED-MOBILITY USERS
This group was not the target demographic in any brief. But when the team ran research with them, a specific physical pattern emerged: the hardest part of cleaning a floor was not the cleaning itself — it was the wringing. Bending to a bucket, wringing a heavy mop, carrying the water. The mop was the problem.
PROFESSIONAL CLEANERS
Extreme-frequency users nobody had thought to study. Their insight: at high frequency, the time to wring, refill, and replace the mop head dominated the session. Disposable was not a luxury concept — it was a time-saving one.
HOUSEHOLDS WITH YOUNG CHILDREN
More frequent cleaning cycles than any other household type. The barrier was the friction of setup and cleanup — not motivation. A faster, lower-friction method would increase frequency of use.
Step 3: The stakeholder that changed the brief
The elderly and limited-mobility users provided the pivotal insight. When the team studied this group, the job-to-be-done shifted: it was not “clean the floor more effectively.” It was “maintain a clean home without physical strain.” The bucket, the wring, the weight, the bending — these were the barriers. Not cleaning power.
A better mop would not have solved this. The insight pushed the brief toward a completely different product archetype: lightweight, no-bucket, disposable. The constraints and the opportunity were both revealed by a stakeholder group nobody had planned to research.
From stakeholder to product category
The Swiffer was not invented by improving the mop. It was invented by discovering that the non-obvious stakeholder group — users nobody had briefed the team to study — redefined what the product needed to do entirely. The stakeholder map changed the design brief. The design brief changed the product. The product opened a new category.
Frameworks
Where Stakeholder Mapping shows up.
A discovery and research-planning method, it appears at the start of any phase where the team needs to know whose input and cooperation the work depends on. It is intentionally blank at later execution phases — by then, the map should already have been built and the engagement plan already be running.
Related methods
What to pair with Stakeholder Mapping.
Sources & further reading
The work behind this method.
Universal Methods of Design
Bella Martin and Bruce Hanington (2012)
A comprehensive reference for design research methods, including stakeholder mapping as a foundational practice. Martin and Hanington's treatment situates stakeholder mapping within the broader research toolkit and makes explicit its relationship to other methods: the map tells you who to study, and the other methods tell you how. Their emphasis on the facilitated session as the mechanism for surfacing non-obvious actors is the insight that separates a stakeholder map from a stakeholder list.
This Is Service Design Doing
Marc Stickdorn, Markus Edgar Hormess, Adam Lawrence, and Jakob Schneider (2018)
The most thorough practical guide to service design methods, including a rigorous treatment of stakeholder mapping in the context of service development. The book's coverage of multi-actor systems — where a service involves many different types of people whose experiences and roles intersect — makes the case that a thorough stakeholder map is a prerequisite for any service design work. Its framing of "backstage" actors (those whose work enables a service but who are invisible to the user) is the foundation for understanding why non-obvious stakeholders are so often the decisive ones.
Systems Thinking for Social Change
David Peter Stroh (2015)
On the systemic nature of stakeholder relationships and the way that solutions designed for obvious actors often produce unintended consequences for the non-obvious ones. Stroh's framework for understanding how actors in a system interact — and how an intervention aimed at one actor sends ripples through the whole system — makes the case for the comprehensive stakeholder map on systemic grounds: missing a stakeholder is not just a research gap; it is a design failure that tends to surface at implementation time.