Stakeholder Power Interest Map

Stakeholder map

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning…

---
name: stakeholder-map
description: "Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement."
---

## Stakeholder Mapping & Communication Plan

Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.

### Context

You are helping build a stakeholder map for **$ARGUMENTS**.

If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.

### Instructions

1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.

Overview

Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.

Manual install (npx, ZIP)

Claude Codenpx skills add phuryn/pm-skills --skill stakeholder-map -g -a claude-code

Claude Code (degit)npx degit phuryn/pm-skills/pm-execution/skills/stakeholder-map#main ~/.claude/skills/stakeholder-map

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.5 KB

Read SKILL.md here

phuryn/main1 file shown

SKILL.md2.5 KB

Browse every file on GitHub↗

SKILL.md

Show the full text52 lines

stakeholder-map/SKILL.md52 lines · 2.5 KB

PreviewCode

Outline

RawView on GitHub

Stakeholder Mapping & Communication Plan

Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.

Context

You are helping build a stakeholder map for $ARGUMENTS.

If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.

Instructions

Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
Classify each stakeholder on two dimensions:
- Power (High/Low): Their ability to influence decisions, resources, or outcomes
- Interest (High/Low): How much the project directly affects them or how engaged they are

Place stakeholders in the Power × Interest grid:

	High Interest	Low Interest
High Power	Manage Closely — Regular 1:1s, involve in decisions, seek their input early	Keep Satisfied — Periodic updates, escalate only critical issues
Low Power	Keep Informed — Regular status updates, invite to demos, gather feedback	Monitor — Light-touch updates, available on request

For each quadrant, recommend:
- Communication frequency (daily, weekly, bi-weekly, monthly)
- Communication format (1:1, email, Slack, meeting, dashboard)
- Key messages and framing
- Potential risks if this stakeholder is neglected
Create a communication plan table:

Stakeholder Role Power Interest Strategy Frequency Channel Key Message
Flag potential conflicts: Identify stakeholders with competing interests and suggest alignment strategies.

Think step by step. Save the stakeholder map as a markdown document.

1	---
2	name: stakeholder-map
3	description: "Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement."
4	---
5
6	## Stakeholder Mapping & Communication Plan
7
8	Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
9
10	### Context
11
12	You are helping build a stakeholder map for $ARGUMENTS.
13
14	If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.
15
16	### Instructions
17
18	1. Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
19
20	2. Classify each stakeholder on two dimensions:
21	- Power (High/Low): Their ability to influence decisions, resources, or outcomes
22	- Interest (High/Low): How much the project directly affects them or how engaged they are
23
24	3. Place stakeholders in the Power × Interest grid:
25
26	\| \| High Interest \| Low Interest \|
27	\|---\|---\|---\|
28	\| High Power \| Manage Closely — Regular 1:1s, involve in decisions, seek their input early \| Keep Satisfied — Periodic updates, escalate only critical issues \|
29	\| Low Power \| Keep Informed — Regular status updates, invite to demos, gather feedback \| Monitor — Light-touch updates, available on request \|
30
31	4. For each quadrant, recommend:
32	- Communication frequency (daily, weekly, bi-weekly, monthly)
33	- Communication format (1:1, email, Slack, meeting, dashboard)
34	- Key messages and framing
35	- Potential risks if this stakeholder is neglected
36
37	5. Create a communication plan table:
38
39	\| Stakeholder \| Role \| Power \| Interest \| Strategy \| Frequency \| Channel \| Key Message \|
40	\|---\|---\|---\|---\|---\|---\|---\|---\|
41
42	6. Flag potential conflicts: Identify stakeholders with competing interests and suggest alignment strategies.
43
44	Think step by step. Save the stakeholder map as a markdown document.
45
46	---
47
48	### Further Reading
49
50	- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
51	- [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)
52