All skills
deanpeters avatar

/stakeholder-mapping

@b68bf96

Prioritize stakeholders using two complementary grids. Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/stakeholder-mapping

This session only. Nothing lands on disk.

template.md

≈913 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Stakeholder Mapping Template

Two grids, then the comparison that makes running both worthwhile. Quality checks at the bottom.

Provenance

Adapted from prompts/ in the product-manager-prompts repo.


Grid 1: Power × Interest — how to engage

## Power × Interest: [Initiative]

| | **High Interest** | **Low Interest** |
|---|---|---|
| **High Power** | **Manage closely** — co-design, frequent touchpoints<br>· [who] | **Keep satisfied** — exec briefings, strategic framing<br>· [who] |
| **Low Power** | **Keep informed** — demos, newsletters, transparency<br>· [who] | **Monitor** — light touch<br>· [who] |

Grid 2: Impact × Power — whose voice to elevate

## Impact × Power: [Initiative]

| | **High Power** | **Low Power** |
|---|---|---|
| **High Impact** | **Q2** — impacted and empowered; manage closely<br>· [who] | **Q1** — impacted but marginalized; **elevate deliberately**<br>· [who] |
| **Low Impact** | **Q4** — gatekeepers; manage the relationship<br>· [who] | **Q3** — monitor, minimal investment<br>· [who] |

Impact is not power. A frontline support agent has high impact and low power. An executive two levels removed has high power and low impact. Collapsing them into one axis is what makes a single grid misleading.


The comparison — why you ran both

### Grid Comparison

| Stakeholder | Power×Interest | Impact×Power | Tension |
|---|---|---|---|
| [who] | Monitor | **Q1** | Low interest, high impact — they don't know this is coming |
| [who] | Manage closely | Q4 | High power, low impact — engaged but not affected |

**Q1 voices to elevate:** [who, and how you'll reach them]

**The mismatch that matters most:** [the one stakeholder whose two placements
disagree most, and what you'll do about it]

The most common and most costly mismatch: Monitor on Power×Interest and Q1 on Impact×Power. That's someone deeply affected who has no power and hasn't engaged — usually because nobody told them. The first grid alone says ignore them. The second says they'll bear the consequences.


Engagement plan

| Stakeholder | Quadrant | Engagement | Cadence | Owner |
|---|---|---|---|---|
| | | [co-design / brief / inform / consult] | | |

Quadrant migration (optional)

For stakeholders you intend to move rather than merely serve.

| Stakeholder | From | To | Why | How |
|---|---|---|---|---|
| [who] | Keep satisfied | Manage closely | Their sponsorship unlocks budget | Bring them into design review |

Migration is a deliberate strategy, not a hope. If you can't name the how, you're not migrating anyone.


Quality checks

Both grids

  • Both were actually built — a single grid hides the mismatch that matters
  • Nobody was placed by seniority as a proxy for power
  • Impact was judged by consequence borne, not by attention paid

The comparison

  • Every stakeholder appears on both grids
  • At least one genuine tension is named. If both grids agree everywhere, one was copied
  • Q1 (high impact, low power) is populated — an empty Q1 usually means you looked only at people with titles

Action

  • Q1 voices have a specific elevation method, not "gather feedback"
  • Every engagement has a named owner and a cadence
  • Any migration names a concrete mechanism

Honesty

  • Someone in Monitor who is genuinely high-impact has been reconsidered
  • The plan is executable by the people named, at the cadence named

Source: SKILL.md on GitHub

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The stakeholder-mapping skill is a purely instructional tool designed to help project managers prioritize stakeholders. It contains only documentation and templates, with no executable code, network operations, or security risks detected.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at b68bf96. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 2 months ago
argument-hint
[stakeholder list or initiative]
type
component
theme
stakeholder-comms
Other metadata
intent
Run two complementary 2x2 grids — Power × Interest (sets engagement strategy per stakeholder) and Impact × Power (surfaces who bears consequences but lacks voice) — then compare outputs to reveal blind spots and plan quadrant migration. The grids answer different questions and neither one alone is sufficient: Power × Interest tells you how to engage; Impact × Power tells you whose voice to elevate. Feed outputs into stakeholder-engagement-advisor for per-stakeholder action planning.
best_for
[
  "After stakeholder identification, when you need to decide who gets which level of engagement",
  "Preparing an engagement plan before a roadmap review where executives and impacted user groups have conflicting authority",
  "Surfacing high-impact, low-power user segments who deserve more voice in product decisions but lack org pull",
  "Re-baselining stakeholder strategy after a reorg has shifted who holds decision authority",
  "Planning a compliance or regulatory initiative where power to block sits separately from who bears the consequences"
]
scenarios
[
  "Who should I prioritize engaging on this initiative?",
  "How do I handle stakeholders with conflicting priorities?",
  "Help me figure out whose voice is missing from our roadmap decisions",
  "I need a stakeholder engagement strategy before our quarterly review"
]
sources
[
  "MITRE Innovation Toolkit — Stakeholder Map & Matrix: https://itk.mitre.org/toolkit-tools/stakeholder-map-and-matrix/",
  "MITRE Innovation Toolkit — Stakeholder Power Categories: https://itk.mitre.org/toolkit-tools/stakeholder-power-categories/"
]
estimated_time
25-40 min

README badge

README badge for deanpeters/product-manager-skills/stakeholder-mapping