# How to Create a Stakeholder Map Using PM Skills: A Complete Guide

> Learn to create a stakeholder map using PM skills with our complete guide. Discover how the stakeholder-map command builds a Power x Interest grid and generates a custom communication plan.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-07-10

---

**To create a stakeholder map using PM Skills, invoke the `/stakeholder-map` command, which executes a structured workflow defined in [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md) to build a Power × Interest grid and generate a tailored communication plan.**

The **phuryn/pm-skills** repository provides a dedicated **skill** for stakeholder mapping that automates the classic Power × Interest framework. This declarative skill guides the model through data collection, classification, and communication strategy generation, outputting a version-controlled Markdown document suitable for any product initiative.

## What Is the Stakeholder Map Skill?

The **stakeholder-map** skill is a declarative instruction set stored in [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md). It defines a six-step workflow that transforms raw project information into a structured stakeholder analysis and communication matrix. Unlike manual mapping exercises, this skill leverages the PM Skills framework to parse inputs, apply decision logic, and format outputs automatically.

The skill is exposed through the CLI command `/stakeholder-map`, documented in [`pm-execution/commands/stakeholder-map.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/stakeholder-map.md). When invoked, the command forwards your project brief to the skill engine, which then executes the classification and planning logic.

## Step-by-Step Workflow for Stakeholder Mapping

The skill follows a rigorous process to ensure comprehensive coverage and strategic alignment.

### Gather Stakeholder Data

The workflow begins by prompting you for project artifacts such as org charts, briefs, or team rosters. If no files are provided, the skill infers likely participants across standard functions: executives, engineers, designers, marketing, sales, support, legal, finance, partners, and end-users. You can also supply a CSV file containing existing stakeholder data for the model to parse and populate.

### Classify by Power and Interest

Each identified stakeholder is evaluated along two dimensions defined in the skill logic:

- **Power**: The ability to influence decisions or allocate resources (High/Low)
- **Interest**: The degree to which the project affects them or their engagement level (High/Low)

This binary classification creates the foundation for the prioritization matrix.

### Map to the Power × Interest Grid

The skill places stakeholders into four quadrants rendered as a Markdown grid:

- **Manage Closely** (High Power + High Interest): Requires frequent 1:1s and early involvement in decision-making
- **Keep Satisfied** (High Power + Low Interest): Needs periodic updates and escalation paths for critical issues only
- **Keep Informed** (Low Power + High Interest): Receives regular status updates and demo invitations
- **Monitor** (Low Power + Low Interest): Gets light-touch updates and on-request availability

### Generate the Communication Plan

For each quadrant, the skill constructs a concrete communication strategy specifying **frequency**, **channel**, **key messages**, and **risk mitigation** tactics. The final output is a Markdown table with the schema: Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message.

### Identify and Flag Conflicts

The skill actively scans for stakeholders with competing interests and suggests alignment strategies to preempt blockers before they impact the project timeline.

## Invoking the Stakeholder Map Command

To execute the skill, use the following syntax in your CLI:

```bash
/stakeholder-map New analytics platform launch

```

The command accepts an optional file upload (CSV or text) containing pre-existing stakeholder data. When provided, the skill parses these files to auto-populate the classification table rather than inferring participants from scratch.

## Practical Example

The following invocation demonstrates a typical workflow for a product launch:

```bash
/stakeholder-map New analytics platform launch

```

**Resulting Output:**

```markdown

## Stakeholder Mapping & Communication Plan

**Project:** New analytics platform launch  

| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |
|-------------|------|-------|----------|----------|-----------|---------|-------------|
| VP of Engineering | Exec | High | High | Manage Closely | Weekly | 1:1 | Align roadmap with technical constraints |
| Marketing Lead | Team | Low | High | Keep Informed | Bi-weekly | Email | Share feature benefits for go-to-market |
| Finance Director | Exec | High | Low | Keep Satisfied | Monthly | Dashboard | Highlight budget impact |
| Support Team | Team | Low | Low | Monitor | As-needed | Chat | Notify of release notes |

```

This Markdown output can be committed to version control, shared with leadership, or integrated into project documentation.

## Key Files and Architecture

Understanding the repository structure helps when customizing or extending the skill:

| File | Purpose |
|------|---------|
| [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md) | Defines the step-by-step workflow, classification logic, and output formatting |
| [`pm-execution/commands/stakeholder-map.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/stakeholder-map.md) | CLI wrapper that triggers the skill execution |
| [`pm-execution/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/README.md) | Lists the skill among other execution-focused capabilities (PRDs, OKRs) |
| [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) | High-level repository overview mentioning the `stakeholder-map` shortcut |

## Summary

- **PM Skills** provides a dedicated `stakeholder-map` skill for automated stakeholder analysis
- The workflow is defined in [`pm-execution/skills/stakeholder-map/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/stakeholder-map/SKILL.md) and executed via the `/stakeholder-map` command
- Stakeholders are classified by **Power** and **Interest**, then mapped to four strategic quadrants
- Output includes a **communication plan** with specific frequencies, channels, and key messages
- The skill detects **conflicts** between stakeholders and suggests mitigation strategies
- Results are emitted as **Markdown** for easy version control and team sharing

## Frequently Asked Questions

### What is the Power × Interest grid in PM Skills?

The Power × Interest grid is a two-by-two matrix used by the stakeholder-map skill to prioritize stakeholders based on their influence (Power) and engagement (Interest). This framework ensures that communication efforts are allocated efficiently, focusing intensive management on high-power, high-interest stakeholders while minimizing overhead for low-priority groups.

### Can I import existing stakeholder data into the PM Skills stakeholder map?

Yes. The skill accepts uploaded files such as CSVs or organizational charts. When you provide these artifacts during the `/stakeholder-map` invocation, the model parses the data to auto-populate the stakeholder table rather than inferring participants from generic project categories.

### How does the stakeholder-map skill handle conflicting interests?

The skill includes a conflict detection step that scans the classified stakeholder list for competing interests or opposing goals. When conflicts are identified, the output includes suggested alignment strategies to help product managers negotiate priorities and maintain project momentum.

### Where is the stakeholder map saved after generation?

The final stakeholder map is emitted as a Markdown document directly in the conversation output. You can copy this Markdown into your project repository, documentation wiki, or version control system. The skill does not automatically persist files to disk; it produces portable text output for manual or scripted storage.