Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Stakeholder Power Interest Grid Mapper

general user planning skill risk: low

Stakeholder Power Interest Grid Mapper

The prompt instructs the model to identify stakeholders for a given project, classify them by power and interest, place them in a 2x2 grid with quadrant-specific strategies, build…

SKILL 1 file

SKILL.md
---
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.

2. **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

3. **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 |

4. **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

5. **Create a communication plan table**:

   | Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |
   |---|---|---|---|---|---|---|---|

6. **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](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)

INPUTS

$ARGUMENTS REQUIRED

project or initiative name/description

REQUIRED CONTEXT

  • project or initiative description ($ARGUMENTS)

OPTIONAL CONTEXT

  • files such as org charts, project briefs, team rosters

ROLES & RULES

Role assignments

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

EXPECTED OUTPUT

Format
markdown
Schema
markdown_tables · Stakeholder, Role, Power, Interest, Strategy, Frequency, Channel, Key Message
Constraints
  • include power/interest grid
  • include communication plan table
  • flag potential conflicts
  • save as markdown document

SUCCESS CRITERIA

  • Identify stakeholders
  • Classify each stakeholder on Power and Interest
  • Place stakeholders in the Power × Interest grid
  • Recommend communication frequency, format, key messages and risks per quadrant
  • Create a communication plan table
  • Flag potential conflicts and suggest alignment strategies
  • Save the stakeholder map as a markdown document

CAVEATS

Dependencies
  • User-provided files (org charts, project briefs, team rosters) or description of the product/initiative

QUALITY

OVERALL
0.82
CLARITY
0.90
SPECIFICITY
0.85
REUSABILITY
0.80
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Add explicit guidance on output length or depth (e.g., "limit to 8-12 stakeholders unless more are provided").

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR GENERAL USER