# Stakeholder Mapping

Prioritize stakeholders using two complementary grids.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Media
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-mapping -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Prioritize stakeholders using two complementary grids. Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Stakeholder Mapping

## Purpose

Prioritize stakeholders and set engagement strategy. This skill runs two complementary grids on your identified stakeholder set and deliberately compares what they reveal, because each grid shows you something the other cannot.

**Power × Interest** answers: how much does each stakeholder care about this initiative, and how much can they influence it? It produces engagement strategies, who to involve deeply, who to keep informed, who to monitor. This is the grid most PMs know.

**Impact × Power** answers: who bears the consequences of this product's outcomes, and how much organizational power do they actually hold? It surfaces the stakeholders who matter most to get right but are most likely to be underrepresented, high impact, low power.

Running only the first grid optimizes for managing relationships with the powerful. Running only the second produces an equity analysis without an engagement plan. The insight lives in comparing them: a stakeholder who appears in "keep informed" on the first grid and "high impact, low power" on the second is someone you've been under-engaging with consequences that fall entirely on them. That's a product risk.

Use this after stakeholder-identification (which builds the full list) and before stakeholder-engagement-advisor (which plans per-stakeholder outreach).

## Input

**Works best with:** Your identified stakeholder list (ideally from `stakeholder-identification`).
**Also useful:** What you know about each person's power, interest, and current stance, plus the engagement decisions the map must drive.

Anything supplied with the invocation itself, text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line, counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The skill asks for the stakeholder set first, mapping unidentified stakeholders just formalizes your blind spots.

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/stakeholder-mapping/SKILL.md