Stakeholder-Map Skill for Power × Interest Grid Analysis: Complete Guide

The stakeholder-map skill is a seven-step framework in the phuryn/pm-skills repository that transforms raw stakeholder data into a structured Power × Interest grid, complete with quadrant-specific communication strategies and conflict detection.

The stakeholder-map skill provides product managers with a systematic approach to stakeholder analysis using the classic Power × Interest grid methodology. As implemented in the open-source phuryn/pm-skills repository, this skill generates actionable communication plans and identifies potential conflicts through an interactive workflow. Whether you're launching a new analytics platform or navigating organizational change, this skill produces standardized markdown artifacts that align teams and clarify engagement strategies.

Core Components of the Stakeholder-Map Skill

The skill executes a seven-step workflow defined in pm-execution/skills/stakeholder-map/SKILL.md, progressing from identification to conflict resolution.

1. Stakeholder Identification

The skill begins by listing every person or group that can affect or be affected by the initiative. This includes executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end-users. This foundational step is defined at line 18 of SKILL.md.

2. Power and Interest Classification

Each stakeholder receives Power (high/low) and Interest (high/low) assignments based on their influence over decisions and resources, plus how much the project matters to them. See the classification logic at SKILL.md line 20.

3. Power × Interest Grid Placement

The skill renders a 2×2 matrix placing stakeholders into four quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor. The ready-made markdown table structure appears at line 24.

4. Quadrant-Specific Communication Strategy

For each quadrant, the skill prescribes specific engagement tactics:

• Frequency: Daily, weekly, or bi-weekly touchpoints
• Format: 1:1 meetings, email, Slack updates, or dashboards
• Key messages and framing tailored to stakeholder priorities
• Risks of neglect if communication fails

This strategic layer is detailed at line 31 of SKILL.md.

5. Communication Plan Table

The skill generates a comprehensive markdown table capturing stakeholder name, role, power level, interest level, strategy, frequency, channel, and key message. The table skeleton resides at line 37.

6. Conflict Detection

The framework flags stakeholders with competing interests and suggests alignment or mitigation tactics. This detection logic appears at line 42.

7. Optional Artifacts

Additional outputs include:

• Escalation path documentation for issue resolution
• RACI matrix clarifying decision ownership
• Focus notes for "Manage Closely" stakeholders requiring intensive engagement

These optional sections are defined at line 83 of stakeholder-map.md.

Triggering the Stakeholder-Map Skill

The skill exposes the /stakeholder-map command in pm-execution/commands/stakeholder-map.md. Valid invocation patterns include:

/stakeholder-map New analytics platform launch
/stakeholder-map Pricing model change affecting all customers
/stakeholder-map [upload a project brief or org chart]

These commands launch an interactive workflow that prompts for context and progressively builds the grid and communication plan according to the seven-step structure.

Example Output Structure

When executed, the skill generates markdown matching the template at lines 59-92 of stakeholder-map.md. Below is a minimal example for an "Analytics Platform Launch":

## Stakeholder Map: Analytics Platform Launch

### Stakeholder Grid

| Stakeholder | Role          | Power | Interest | Quadrant       | Stance |
|------------|---------------|-------|----------|----------------|--------|
| Jane Doe   | VP Engineering| High  | High     | Manage Closely | Support|
| John Smith | Finance Lead  | High  | Low      | Keep Satisfied | Neutral|
| Alice Lee  | Marketing Dir | Low   | High     | Keep Informed  | Support|
| Bob Kim    | Customer Support| Low | Low      | Monitor        | N/A    |

### Communication Plan

#### Manage Closely (High Power, High Interest)

| Stakeholder | Channel | Frequency | Content                     | Owner |
|------------|---------|-----------|-----------------------------|-------|
| Jane Doe   | 1:1     | Weekly    | Road‑map updates, risk log | PM    |

#### Keep Satisfied (High Power, Low Interest)

| Stakeholder | Channel | Frequency | Content               | Owner |
|------------|---------|-----------|-----------------------|-------|
| John Smith | Email   | Bi‑weekly | KPI snapshot, budget | PM    |

#### Keep Informed (Low Power, High Interest)

| Stakeholder | Channel | Frequency | Content                     | Owner |
|------------|---------|-----------|-----------------------------|-------|
| Alice Lee  | Slack   | Weekly    | Feature demo, release notes| PM    |

#### Monitor (Low Power, Low Interest)

*Only included in broad status newsletters.*

### Potential Conflicts

- **Finance vs Engineering:** Budget constraints vs performance goals → set up a joint steering committee.

### Escalation Path

1. PM → VP Engineering  
2. VP Engineering → CTO  

### RACI Matrix

| Decision Area | Responsible | Accountable | Consulted | Informed |
|---------------|-------------|------------|----------|----------|
| Release date  | PM          | VP Eng      | Legal, Finance | All |

Key Source Files

Understanding the implementation requires referencing these specific files in the phuryn/pm-skills repository:

• pm-execution/skills/stakeholder-map/SKILL.md: Contains the full step-by-step instructions, grid layout, and communication-plan template.
• pm-execution/commands/stakeholder-map.md: Defines the /stakeholder-map command, invocation examples, and output markdown skeleton.
• README.md (repo root): Lists this skill among 16 execution skills with shorthand command reference.
• CLAUDE.md: Provides the overall catalog of pm-execution skills.

Summary

• The stakeholder-map skill implements a seven-step workflow for Power × Interest grid analysis in product management.
• It generates standardized markdown tables for stakeholder grids, communication plans, and RACI matrices.
• The /stakeholder-map command triggers an interactive session that produces ready-to-use documentation.
• Built-in conflict detection identifies competing interests and suggests mitigation tactics.
• Optional artifacts include escalation paths and detailed focus notes for high-priority stakeholders.

Frequently Asked Questions

What is the Power × Interest grid used for in the stakeholder-map skill?

The Power × Interest grid categorizes stakeholders into four quadrants—Manage Closely, Keep Satisfied, Keep Informed, and Monitor—based on their authority over resources and their personal investment in project outcomes. This classification determines communication frequency and channel selection to ensure high-power decision-makers remain satisfied while engaged supporters stay informed without meeting fatigue.

How does the stakeholder-map skill detect conflicts?

According to the source code at line 42 of SKILL.md, the skill analyzes stakeholder stances and interests to flag competing priorities, such as budget constraints versus performance goals. It then recommends specific alignment tactics like establishing joint steering committees or scheduling facilitated alignment sessions to resolve tensions before they escalate.

Can I customize the output format of the stakeholder-map skill?

Yes. While the skill generates standard markdown tables defined in commands/stakeholder-map.md, the output structure at lines 59-92 serves as a skeleton that you can modify. The optional artifacts section—including escalation paths and RACI matrices—can be included or omitted based on project complexity and organizational needs.

What triggers the stakeholder-map skill in the phuryn/pm-skills repository?

The skill activates via the /stakeholder-map command followed by a project description or uploaded document (brief, org chart). This command, defined in pm-execution/commands/stakeholder-map.md, initiates the interactive workflow that walks through the seven steps defined in SKILL.md, progressively building the analysis through user prompts.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}