name: stakeholder-map
description: Map stakeholders on a Power x Interest grid and create tailored communication plans. Use when managing complex stakeholder environments, launching cross-functional initiatives, or joining a new organization.
Stakeholder Map
A Power x Interest grid for identifying, categorizing, and managing stakeholders — with tailored communication strategies for each quadrant.
Purpose
Product initiatives fail more often from stakeholder misalignment than from bad engineering. This skill maps who cares, who has power, and what each person needs from you — preventing surprises, building support, and managing resistance proactively.
When to Use
- Starting a new initiative that touches multiple teams
- Joining a new organization or product area
- Preparing for a high-stakes launch or migration
- When a project is stalled due to organizational friction
- Before presenting a PRD or strategy for approval
When NOT to Use
- Solo projects with no organizational dependencies
- When all stakeholders are already aligned (verify this assumption first)
Required Context (Ask If Missing)
- Initiative description — what you're trying to accomplish
- Organization structure — teams, reporting lines, key roles
- Known stakeholders — people you already know are involved or affected
- Decision-making process — how decisions get made (RACI, consensus, executive decree?)
The Process
Step 1: Identify All Stakeholders
List everyone who is:
- Impacted by the initiative (their work, metrics, or team changes)
- Has influence over the initiative (can approve, block, or fund)
- Has expertise needed for the initiative (technical, domain, market)
- Has interest in the outcome (even if not directly impacted)
Don't forget:
- Adjacent team leads
- Support and operations teams
- Finance / legal / compliance
- External partners or customers
- Executive sponsors
Step 2: Map on Power x Interest Grid
For each stakeholder, rate:
- Power (High/Low): Can they approve, block, fund, or influence the outcome?
- Interest (High/Low): Do they care about this initiative's outcome?
HIGH INTEREST
│
┌────────────────────┼────────────────────┐
│ │ │
│ Keep Satisfied │ Manage Closely │
│ │ │
│ Periodic updates │ Regular 1:1s │
│ Escalate critical │ Involve in │
│ issues only │ decisions │
│ │ │
HIGH├────────────────────┼────────────────────┤
POWER │
│ │ │
│ Monitor │ Keep Informed │
│ │ │
│ Light-touch │ Status updates │
│ Watch for │ Demo invitations │
│ changes │ Feedback channel │
│ │ │
└────────────────────┼────────────────────┘
LOW INTEREST
Step 3: Define Communication Strategy Per Quadrant
Manage Closely (High Power, High Interest)
These are your most important stakeholders. Mismanaging them kills projects.
- Frequency: Weekly or bi-weekly 1:1s
- Format: In-person or video meetings, personalized updates
- Content: Progress, decisions needed, risks, trade-offs
- Action: Involve in key decisions before they're finalized
- Risk if neglected: They feel blindsided, withdraw support, or actively block
Keep Satisfied (High Power, Low Interest)
They can make or break your project but don't want to be in the details.
- Frequency: Monthly or milestone-based updates
- Format: Brief email or Slack summary, executive briefing
- Content: High-level status, escalations only, outcomes not activities
- Action: Only escalate critical issues or decisions that need their authority
- Risk if neglected: They hear about problems from others and lose confidence
Keep Informed (Low Power, High Interest)
They care deeply but can't directly block you. Often your best advocates.
- Frequency: Regular status updates (weekly or sprint-based)
- Format: Team meetings, Slack channels, demo sessions
- Content: Progress updates, feature previews, opportunities for input
- Action: Give them a feedback channel, leverage as evangelists
- Risk if neglected: They feel ignored, become detractors, or spread misinformation
Monitor (Low Power, Low Interest)
Minimal investment needed — but watch for changes.
- Frequency: Quarterly or as-needed
- Format: Broad communications (newsletters, all-hands)
- Content: Major milestones only
- Action: Watch for shifts — interest or power can change
- Risk if neglected: Low, but can become noisy if surprised by changes that affect them
Step 4: Identify Risks and Conflicts
Flag stakeholders who:
- Have conflicting interests with each other
- Are resistant to the initiative (and why)
- Have recently changed roles (power/interest may shift)
- Are underrepresented in current communications
Output Format
# Stakeholder Map — [Initiative Name]
**Date:** [date]
**PM:** [name]
---
## Stakeholder Grid
### Manage Closely (High Power, High Interest)
| Stakeholder | Role | Interest Area | Communication Plan | Potential Risk |
| --- | --- | --- | --- | --- |
| [name] | [role] | [what they care about] | Weekly 1:1, involve in [decisions] | [risk if mismanaged] |
### Keep Satisfied (High Power, Low Interest)
| Stakeholder | Role | Interest Area | Communication Plan | Escalation Trigger |
| --- | --- | --- | --- | --- |
| [name] | [role] | [what they care about] | Monthly summary | [when to escalate] |
### Keep Informed (Low Power, High Interest)
| Stakeholder | Role | Interest Area | Communication Plan | Leverage |
| --- | --- | --- | --- | --- |
| [name] | [role] | [what they care about] | Sprint updates, demos | [how they can help] |
### Monitor (Low Power, Low Interest)
| Stakeholder | Role | Watch For |
| --- | --- | --- |
| [name] | [role] | [condition that would increase their interest/power] |
---
## Conflicts and Risks
| Conflict | Stakeholders Involved | Mitigation |
| --- | --- | --- |
| [conflict description] | [names] | [how to handle] |
---
## Communication Calendar
| Cadence | Audience | Format | Owner |
| --- | --- | --- | --- |
| Weekly | Manage Closely group | 1:1 meetings | PM |
| Bi-weekly | Keep Informed group | Sprint demo | PM + Eng Lead |
| Monthly | Keep Satisfied group | Email summary | PM |
| Quarterly | All stakeholders | Roadmap review | PM + Leadership |
Anti-Patterns
| Avoid |
Why |
Instead |
| Treating all stakeholders equally |
Wastes time on low-impact people, under-invests in critical ones |
Use the grid to prioritize |
| Only mapping supporters |
Resistors cause the most damage if ignored |
Map everyone, especially skeptics |
| Static map |
People change roles, priorities shift |
Review monthly |
| Communicating the same way to everyone |
Execs want summaries, ICs want details |
Tailor format and depth |
| Skipping the conflict analysis |
Unaddressed conflicts escalate |
Name conflicts, plan mitigation |
References
1---2name: stakeholder-map-33description: <!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->4---5<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->6---7name: stakeholder-map8description: Map stakeholders on a Power x Interest grid and create tailored communication plans. Use when managing complex stakeholder environments, launching cross-functional initiatives, or joining a new organization.9---1011# Stakeholder Map1213A Power x Interest grid for identifying, categorizing, and managing stakeholders — with tailored communication strategies for each quadrant.1415---1617## Purpose1819Product initiatives fail more often from stakeholder misalignment than from bad engineering. This skill maps who cares, who has power, and what each person needs from you — preventing surprises, building support, and managing resistance proactively.2021---2223## When to Use2425- Starting a new initiative that touches multiple teams26- Joining a new organization or product area27- Preparing for a high-stakes launch or migration28- When a project is stalled due to organizational friction29- Before presenting a PRD or strategy for approval3031## When NOT to Use3233- Solo projects with no organizational dependencies34- When all stakeholders are already aligned (verify this assumption first)3536---3738## Required Context (Ask If Missing)3940- **Initiative description** — what you're trying to accomplish41- **Organization structure** — teams, reporting lines, key roles42- **Known stakeholders** — people you already know are involved or affected43- **Decision-making process** — how decisions get made (RACI, consensus, executive decree?)4445---4647## The Process4849### Step 1: Identify All Stakeholders5051List everyone who is:52- **Impacted by** the initiative (their work, metrics, or team changes)53- **Has influence over** the initiative (can approve, block, or fund)54- **Has expertise** needed for the initiative (technical, domain, market)55- **Has interest** in the outcome (even if not directly impacted)5657**Don't forget:**58- Adjacent team leads59- Support and operations teams60- Finance / legal / compliance61- External partners or customers62- Executive sponsors6364### Step 2: Map on Power x Interest Grid6566For each stakeholder, rate:67- **Power** (High/Low): Can they approve, block, fund, or influence the outcome?68- **Interest** (High/Low): Do they care about this initiative's outcome?6970```text71 HIGH INTEREST72 │73 ┌────────────────────┼────────────────────┐74 │ │ │75 │ Keep Satisfied │ Manage Closely │76 │ │ │77 │ Periodic updates │ Regular 1:1s │78 │ Escalate critical │ Involve in │79 │ issues only │ decisions │80 │ │ │81HIGH├────────────────────┼────────────────────┤82POWER │83 │ │ │84 │ Monitor │ Keep Informed │85 │ │ │86 │ Light-touch │ Status updates │87 │ Watch for │ Demo invitations │88 │ changes │ Feedback channel │89 │ │ │90 └────────────────────┼────────────────────┘91 LOW INTEREST92```9394### Step 3: Define Communication Strategy Per Quadrant9596#### Manage Closely (High Power, High Interest)9798These are your most important stakeholders. Mismanaging them kills projects.99100- **Frequency:** Weekly or bi-weekly 1:1s101- **Format:** In-person or video meetings, personalized updates102- **Content:** Progress, decisions needed, risks, trade-offs103- **Action:** Involve in key decisions before they're finalized104- **Risk if neglected:** They feel blindsided, withdraw support, or actively block105106#### Keep Satisfied (High Power, Low Interest)107108They can make or break your project but don't want to be in the details.109110- **Frequency:** Monthly or milestone-based updates111- **Format:** Brief email or Slack summary, executive briefing112- **Content:** High-level status, escalations only, outcomes not activities113- **Action:** Only escalate critical issues or decisions that need their authority114- **Risk if neglected:** They hear about problems from others and lose confidence115116#### Keep Informed (Low Power, High Interest)117118They care deeply but can't directly block you. Often your best advocates.119120- **Frequency:** Regular status updates (weekly or sprint-based)121- **Format:** Team meetings, Slack channels, demo sessions122- **Content:** Progress updates, feature previews, opportunities for input123- **Action:** Give them a feedback channel, leverage as evangelists124- **Risk if neglected:** They feel ignored, become detractors, or spread misinformation125126#### Monitor (Low Power, Low Interest)127128Minimal investment needed — but watch for changes.129130- **Frequency:** Quarterly or as-needed131- **Format:** Broad communications (newsletters, all-hands)132- **Content:** Major milestones only133- **Action:** Watch for shifts — interest or power can change134- **Risk if neglected:** Low, but can become noisy if surprised by changes that affect them135136### Step 4: Identify Risks and Conflicts137138Flag stakeholders who:139- Have **conflicting interests** with each other140- Are **resistant** to the initiative (and why)141- Have **recently changed roles** (power/interest may shift)142- Are **underrepresented** in current communications143144---145146## Output Format147148```markdown149# Stakeholder Map — [Initiative Name]150151**Date:** [date]152**PM:** [name]153154---155156## Stakeholder Grid157158### Manage Closely (High Power, High Interest)159160| Stakeholder | Role | Interest Area | Communication Plan | Potential Risk |161| --- | --- | --- | --- | --- |162| [name] | [role] | [what they care about] | Weekly 1:1, involve in [decisions] | [risk if mismanaged] |163164### Keep Satisfied (High Power, Low Interest)165166| Stakeholder | Role | Interest Area | Communication Plan | Escalation Trigger |167| --- | --- | --- | --- | --- |168| [name] | [role] | [what they care about] | Monthly summary | [when to escalate] |169170### Keep Informed (Low Power, High Interest)171172| Stakeholder | Role | Interest Area | Communication Plan | Leverage |173| --- | --- | --- | --- | --- |174| [name] | [role] | [what they care about] | Sprint updates, demos | [how they can help] |175176### Monitor (Low Power, Low Interest)177178| Stakeholder | Role | Watch For |179| --- | --- | --- |180| [name] | [role] | [condition that would increase their interest/power] |181182---183184## Conflicts and Risks185186| Conflict | Stakeholders Involved | Mitigation |187| --- | --- | --- |188| [conflict description] | [names] | [how to handle] |189190---191192## Communication Calendar193194| Cadence | Audience | Format | Owner |195| --- | --- | --- | --- |196| Weekly | Manage Closely group | 1:1 meetings | PM |197| Bi-weekly | Keep Informed group | Sprint demo | PM + Eng Lead |198| Monthly | Keep Satisfied group | Email summary | PM |199| Quarterly | All stakeholders | Roadmap review | PM + Leadership |200```201202---203204## Anti-Patterns205206| Avoid | Why | Instead |207| --- | --- | --- |208| Treating all stakeholders equally | Wastes time on low-impact people, under-invests in critical ones | Use the grid to prioritize |209| Only mapping supporters | Resistors cause the most damage if ignored | Map everyone, especially skeptics |210| Static map | People change roles, priorities shift | Review monthly |211| Communicating the same way to everyone | Execs want summaries, ICs want details | Tailor format and depth |212| Skipping the conflict analysis | Unaddressed conflicts escalate | Name conflicts, plan mitigation |213214---215216## References217218- Mendelow, Aubrey. "Stakeholder Mapping" (1991)219- [Mind the Product: Stakeholder Management](https://www.mindtheproduct.com/stakeholder-management/)220221<!-- Source: .faos/custom/skills/business/stakeholder-map/SKILL.md -->