Stakeholder Map

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

• The Product Management Frameworks Compendium + Templates
• Team Topologies: A Handbook to Set and Scale Product Teams