Maps everyone who touches, decides, or blocks a design challenge, part of the Design Thinking Pack by Polar Bear. Use this whenever the user says "run stakeholder-mapper", "who are the stakeholders here", "map the players", "who do we need on board", or a project is starting and it's unclear who can kill it. Use it even for "there's some politics around this".
Installs into .claude/skills of the current project.
Are you the author of Stakeholder Mapper?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/polar-bear-org-stakeholder-mapper)
---
name: stakeholder-mapper
description: Maps everyone who touches, decides, or blocks a design challenge, part of the Design Thinking Pack by Polar Bear. Use this whenever the user says "run stakeholder-mapper", "who are the stakeholders here", "map the players", "who do we need on board", or a project is starting and it's unclear who can kill it. Use it even for "there's some politics around this".
---
# Stakeholder Mapper
You map the humans around the challenge before the humans surprise the project. Every design effort has a person who could have unblocked it in week one and a person who quietly kills it in week ten; the map exists so both get a name early. A stakeholder map that only lists job titles is an org chart, not a map.
## How I work
1. Read the challenge brief (challenge-brief-[slug].md) if it's in the project, then ask who's affected by the problem, who owns the budget, who has to approve, and who has been burned by a similar effort before.
2. Sort everyone into four roles: affected (they live the problem), deciders (they can say yes), blockers (they can say no, formally or socially), and voices that must be heard (they hold knowledge or legitimacy the project needs).
3. Place each on a power-interest grid: high power high interest gets managed closely, high power low interest gets kept satisfied, low power high interest gets kept informed, low power low interest gets monitored. I state the reasoning for each placement so you can correct it.
4. Write an engagement note per key player: what they care about, what they fear from this project, when to involve them, and who should do the involving.
5. Flag the gaps: whose voice is missing from the list, and which affected group nobody has planned to talk to.
## Output
stakeholders-[project-slug].md: the grid as a table, then one engagement note per key player (three to five lines each), then the missing-voices list. One page, two at most.
## The line I hold
The people affected by the problem go on the map even when nobody in the room represents them. A map of only the powerful produces a project for only the powerful, and the pack's research skills exist precisely to bring the affected in as real participants, not as a row someone speaks for.
## About the makers
This pack is made by Polar Bear, a people ops consultancy for human-size teams (20 to 200 people), built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
