# Stakeholder Map

A stakeholder map identifies people and groups who affect or are affected by a decision, then makes relationships, power, interests, and engagement visible.

- Type: artifact
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/stakeholder-map/>)

## What it means

A stakeholder map is a visual representation of the people, groups, and institutions connected to a project or system. It may organize them by relationship, proximity, influence, interest, impact, or another relevant dimension. Its purpose is not merely to manage powerful sponsors, but to understand whose knowledge, rights, labor, risks, and outcomes must shape the work.

## Why it matters

Products fail when teams overlook a gatekeeper, frontline worker, downstream community, regulator, or person who bears harm without buying the product. Mapping expands the field of view, clarifies relationships and decision power, and supports a deliberate plan for research, participation, communication, consent, and accountability.

## When to use it

Use it at project kickoff, during discovery planning, before major policy or platform changes, when forming a governance group, or when conflict and hidden dependencies emerge. Revisit it after research, organizational changes, or decisions that alter who benefits or carries risk.

## How it works

1. Define the decision or system being mapped, then brainstorm internal, external, direct, indirect, present, and future stakeholders.
2. Include people affected by outcomes even if they lack purchasing power, formal authority, technical access, or an easy channel to the team.
3. Map relationships and relevant dimensions such as influence, interest, impact, expertise, trust, vulnerability, and decision rights.
4. Validate assumptions through conversations and records; avoid assigning motives or speaking for groups without evidence.
5. Create an engagement plan that matches the stakes—from informing to co-deciding—and update the map as the system changes.

## A practical example

A school district planning an attendance app maps students, guardians, teachers, office staff, social workers, transportation providers, privacy officers, courts, and families with unstable housing. The team learns that automated absence alerts could expose sensitive situations, so it adds human review, appeal routes, translated messages, and strict data minimization.

## Where it breaks

Influence-interest grids can privilege already powerful actors and reduce complex people to labels. A map cannot substitute for participation, and categorizing someone as low influence must never imply low importance. Sensitive maps may also create security or privacy risks, so access, detail, and retention should be proportionate.

## Common mistakes

- Equating stakeholders with executives and customers only.
- Guessing people’s interests, needs, or level of support without speaking to them.
- Using the map solely to win approval rather than distribute voice and decision rights responsibly.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/stakeholder-map/#visualization-stakeholder-map>)

## Sources

1. [Stakeholders Map](<https://servicedesigntools.org/tools/stakeholders-map>) — Service Design Tools · Method guide
2. [Stakeholder Mapping: The Complete Guide to Stakeholder Maps](<https://ixdf.org/literature/article/map-the-stakeholders>) — Interaction Design Foundation · Educational article
3. [Mapping Systems](<https://www.thisisservicedesigndoing.com/methods/mapping-systems>) — This is Service Design Doing · Method guide

## Related topics

- [Ecosystem Map](<https://wiki.soroush.uk/topic/ecosystem-map/>)
- [Service Blueprint](<https://wiki.soroush.uk/topic/service-blueprint/>)
- [Design Review](<https://wiki.soroush.uk/topic/design-review/>)
