How to Create a Stakeholder Map Using the Power × Interest Grid

The pm-skills repository provides a /stakeholder-map slash command that automatically generates a Power × Interest grid and tailored communication plan through markdown-based prompting logic.

Creating a stakeholder map is essential for project success, and the pm-skills open-source toolkit streamlines this process with a ready-to-use command that implements the classic Power × Interest framework. This repository delivers a complete workflow for identifying stakeholders, classifying them by influence and engagement, and generating actionable communication strategies. The implementation relies entirely on markdown-based prompting without compiled binaries, making it compatible with Claude-style AI assistants.

Understanding the Power × Interest Grid

The Power × Interest grid is a project management framework that categorizes stakeholders based on two dimensions: Power (the ability to influence the project outcome) and Interest (the level of concern or investment in the project). This creates four distinct quadrants that dictate communication frequency and management approach. The pm-skills implementation automates this classification through structured prompting logic defined in the skill files.

Using the Stakeholder-Map Command

Command Syntax and Invocation

To initiate the mapping process, use the slash-command syntax with a brief project description. According to pm-execution/commands/stakeholder-map.md (lines 6-15), the command parses your input and forwards it to the underlying skill engine.

/stakeholder-map New analytics platform launch

You can also supply supporting documents such as org charts or project briefs to pre-populate the stakeholder list:

/stakeholder-map [upload org_chart.pdf]

The Step-by-Step Workflow

The skill execution follows a rigorous five-phase pipeline as defined in pm-execution/skills/stakeholder-map/SKILL.md:

1. Context Gathering – The system asks clarifying questions about the initiative phase, known stakeholders, and political sensitivities (lines 20-27 of the command file).

2. Stakeholder Identification – A predefined list of typical internal and external roles is presented (lines 30-34), expanded automatically with any uploaded documents.

3. Classification – Each stakeholder receives Power (high/low) and Interest (high/low) assignments (lines 20-22 of the skill file).

4. Grid Placement – A static 2 × 2 matrix maps stakeholders to four quadrants (lines 26-30):

   • Manage Closely – High Power, High Interest
   • Keep Satisfied – High Power, Low Interest
   • Keep Informed – Low Power, High Interest
   • Monitor – Low Power, Low Interest

5. Communication Plan Generation – For each quadrant, the tool suggests frequency, channel, key message, and owner (lines 31-35), then renders the final markdown document.

Inside the Implementation

Command Definition (pm-execution/commands/stakeholder-map.md)

This file defines the slash-command interface, argument parsing, and the markdown skeleton that gets populated during execution. It specifies the workflow steps (lines 20-27) and provides the template structure for the final output document. The command surface handles the transition from user input to skill invocation, ensuring consistent formatting across all generated stakeholder maps.

Skill Logic (pm-execution/skills/stakeholder-map/SKILL.md)

The core intelligence resides here, containing the prompting logic for stakeholder discovery and the classification algorithm. This file implements the grid mapping logic and determines communication tactics based on quadrant placement. The skill processes the document generation in sections: stakeholder tables (lines 62-65), quadrant-specific communication tables (lines 68-79), and optional conflict-resolution sections (lines 83-88).

Repository Documentation

The stakeholder-map command is listed among the top-level features in README.md (lines 236-255), with additional context provided in pm-execution/README.md (line 17) describing its role within the execution module.

Practical Code Examples

Basic Invocation and Output

Triggering the command produces a complete markdown document with structured tables:

/stakeholder-map New analytics platform launch

Result includes:

## Stakeholder Map: New analytics platform launch

### Stakeholder Grid

| Stakeholder | Role      | Power | Interest | Quadrant        | Stance |
|------------|-----------|-------|----------|-----------------|--------|
| CFO        | Executive | High  | Low      | Keep Satisfied  | Cautious |
| Tech Lead  | Engineering | Low | High     | Keep Informed   | Supportive |

Integrating with Downstream Automation

After generating the map, you can leverage the structured output for further automation. As noted in lines 98-100 of the command file, the generated markdown supports downstream workflows such as drafting updates or scheduling meetings:

Want me to **draft the first stakeholder update** for the 'Manage Closely' group?

Answering "yes" prompts the assistant to populate the Manage Closely communication table with a ready-to-send email template based on the predefined frequency and channel recommendations.

The Four Quadrants and Communication Strategy

The pm-skills implementation enforces a consistent communication strategy for each quadrant:

• Manage Closely: Weekly face-to-face meetings or dedicated Slack channels for high-power, high-interest stakeholders who require active collaboration.
• Keep Satisfied: Monthly executive summaries and quarterly business reviews for high-power, low-interest stakeholders who need periodic reassurance without detail overload.
• Keep Informed: Bi-weekly email newsletters and dashboard access for low-power, high-interest stakeholders who want transparency but lack decision authority.
• Monitor: Annual updates and passive observation for low-power, low-interest stakeholders who require minimal resource investment.

Summary

• The pm-skills repository provides a complete markdown-based stakeholder mapping solution through the /stakeholder-map command.
• The workflow is defined in pm-execution/commands/stakeholder-map.md and pm-execution/skills/stakeholder-map/SKILL.md, covering identification, classification, grid placement, and communication planning.
• The Power × Interest grid automatically categorizes stakeholders into four quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor.
• Generated output includes structured tables for stakeholders and quadrant-specific communication tactics, with optional conflict-resolution sections.
• The tool supports document uploads for automated stakeholder extraction and integrates with downstream automation for drafting updates and scheduling meetings.

Frequently Asked Questions

What is the Power × Interest grid in project management?

The Power × Interest grid is a stakeholder analysis framework that maps individuals based on their authority to influence project outcomes (Power) and their level of concern or investment (Interest). This creates four quadrants that determine appropriate communication strategies and management effort, ensuring high-power stakeholders receive adequate attention while limited resources are not wasted on low-impact monitors.

How do I invoke the stakeholder-map command in the pm-skills repository?

Use the slash-command syntax /stakeholder-map followed by a project description or initiative name. You can optionally upload supporting documents like org charts using bracket notation: /stakeholder-map [upload filename.pdf]. The command is processed by the markdown-based prompting system defined in pm-execution/commands/stakeholder-map.md and requires a Claude-style AI assistant to interpret the syntax.

Where is the stakeholder classification logic implemented?

The classification logic resides in pm-execution/skills/stakeholder-map/SKILL.md (lines 20-22), which defines the prompting strategy for assigning Power and Interest values. The grid placement algorithm (lines 26-30) maps these binary classifications into the four standard quadrants, while the communication recommendations (lines 31-35) provide specific frequency, channel, and messaging guidance for each quadrant.

Can I customize the communication plan templates generated by the tool?

Yes. Since the pm-skills implementation uses pure markdown-based prompting without compiled binaries, you can edit the generated output directly or modify the underlying templates in pm-execution/commands/stakeholder-map.md. The repository is designed for extensibility, allowing organizations to adapt the communication tables, conflict-resolution sections (lines 83-88), and escalation procedures to fit specific organizational tooling or methodologies.

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