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