stakeholder-map

Name: stakeholder-map
Author: phuryn

1.8kinstalls2.5kforks

How to install stakeholder-map?

phuryn/pm-skills/stakeholder-map

$npx -y skills add phuryn/pm-skills --skill stakeholder-map

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type

stakeholder-map

1.8kinstalls2.5kforks

View on GitHub

How to install stakeholder-map?

phuryn/pm-skills/stakeholder-map

$npx -y skills add phuryn/pm-skills --skill stakeholder-map

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type