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
1---2name: stakeholder-map3description: Stakeholder Mapping & Communication Plan4---5## Stakeholder Mapping & Communication Plan67Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.89### Context1011You are helping build a stakeholder map for **$ARGUMENTS**.1213If 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.1415### Instructions16171. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.18192. **Classify each stakeholder** on two dimensions:20 - **Power** (High/Low): Their ability to influence decisions, resources, or outcomes21 - **Interest** (High/Low): How much the project directly affects them or how engaged they are22233. **Place stakeholders in the Power × Interest grid**:2425 | | High Interest | Low Interest |26 |---|---|---|27 | **High Power** | **Manage Closely** — Regular 1:1s, involve in decisions, seek their input early | **Keep Satisfied** — Periodic updates, escalate only critical issues |28 | **Low Power** | **Keep Informed** — Regular status updates, invite to demos, gather feedback | **Monitor** — Light-touch updates, available on request |29304. **For each quadrant**, recommend:31 - Communication frequency (daily, weekly, bi-weekly, monthly)32 - Communication format (1:1, email, Slack, meeting, dashboard)33 - Key messages and framing34 - Potential risks if this stakeholder is neglected35365. **Create a communication plan table**:3738 | Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |39 |---|---|---|---|---|---|---|---|40416. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies.4243Think step by step. Save the stakeholder map as a markdown document.4445---4647### Further Reading4849- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)50- [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)
ComeOnOliver