All skills
deanpeters avatar

/stakeholder-identification

@b68bf96

Map every stakeholder before engaging anyone. Use when launching an initiative, scoping discovery, or building an engagement plan from scratch.

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

This session only. Nothing lands on disk.

template.md

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

Stakeholder Identification Template

Six steps, one worksheet each. Quality checks at the bottom.

Provenance

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


Step 1: Brainstorm without filtering

Four to six minutes, silent if in a group. Do not evaluate yet — evaluating during generation is what produces a list of the same eight people every time.

## Stakeholder Brainstorm: [Initiative]

Individuals, teams, organizations, and groups:
- [name or role]
- [name or role]

Step 2: Categorize

A stakeholder can appear in more than one column. The overlaps are the interesting part — an ally who is also a gatekeeper is a different relationship than either alone.

| Stakeholder | Ally | Audience | Influencer |
|---|---|---|---|
| [who] | ✓ | | ✓ |
  • Allies — actively support this, or benefit from its success
  • Audiences — impacted by the outcome, directly or indirectly
  • Influencers — shape decisions, opinion, or adoption without participating directly

Step 3: R/P/D marking

| Stakeholder | R (Resources) | P (Permission) | D (Decision) | Notes |
|---|---|---|---|---|
| [who] | budget/data/access | approval/sign-off | final say | |

The gap test: anyone holding P or D who wasn't in your Step 1 list is a gap that will surface later as a blocked launch. Add them now and note that you missed them — the pattern of who you forget is itself information.


Step 4: Equity lens

### Equity Lens

- Who experiences a significant consequence — financially, professionally, or personally?
- Who bears the product's costs or risks **without power to shape its design**?
- Whose perspective is missing because we assumed someone else represents them?
- Primary users? Secondary users? Affected in the third degree?

**Added by this lens:**
- [who, and what consequence they bear]

Stakeholders surfaced here usually land in Q1 of a stakeholder map — high impact, low power — and are the ones most likely to be discovered late.


Step 5: Bias and assumptions

### Bias Check

- Who did we default to naming first? [answer]
- Who is absent, and why? [answer]
- What did we assume about who counts as a stakeholder? [answer]

Record the answers. They shape the research plan and recruitment strategy, not just this list.


Step 6: Narrow to priority targets

Two or three. More than that isn't prioritization.

### Priority Stakeholders

| Name | Category | R/P/D | What we need to learn |
|---|---|---|---|
| | | | |

Choose from:

  • Highest-power decision-makers whose buy-in is required
  • Highest-impact users whose needs are least understood
  • Most likely blockers or skeptics

Quality checks

Generation

  • Step 1 ran without filtering — no one was excluded during brainstorm
  • The list includes people outside your organization where relevant

Coverage

  • Every P and D holder appears; any late additions are noted as gaps
  • Overlaps between categories are marked rather than forced into one column
  • The equity lens actually added someone. If it added nobody, it wasn't run honestly

Honesty

  • The bias check names a real default, not "we were thorough"
  • Someone who bears cost without power is on the list

Prioritization

  • Two or three priority targets, not eight
  • Each has a specific "what we need to learn," not "understand their needs"
  • At least one is a likely skeptic or blocker

Source: SKILL.md on GitHub

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill is a purely instructional framework for project management and stakeholder identification. It does not execute code, access sensitive files, or perform network operations. All external references are informational links to the author's own repository or established innovation toolkits.

  • 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
[initiative]
type
component
theme
stakeholder-comms
Other metadata
intent
Produce a comprehensive, equity-aware stakeholder set before any engagement begins. Combines broad brainstorm with structured categorization (Allies / Audiences / Influencers, R/P/D marking), an explicit equity and bias check, and a disciplined narrowing to the 2-3 stakeholders to understand deeply first. Designed to run as a solo exercise or a kickoff workshop. Feed outputs directly into stakeholder-mapping for prioritization.
best_for
[
  "Launching a new initiative where the stakeholder landscape is unmapped and influence networks are unknown",
  "Scoping a discovery sprint to define who to research, interview, and recruit",
  "Preparing a PRD stakeholder section with a validated, comprehensive list before writing requirements",
  "Onboarding to a new product domain and needing to map allies, gatekeepers, and decision-makers quickly",
  "Pressure-testing an existing stakeholder list for blind spots, bias, and missing edge-case populations"
]
scenarios
[
  "Who are all the stakeholders for this initiative?",
  "Are we missing anyone important in our stakeholder map?",
  "Help me prepare the stakeholder section of my PRD",
  "Who should we recruit for discovery research?"
]
sources
[
  "MITRE Innovation Toolkit — Stakeholder Identification Canvas: https://itk.mitre.org/toolkit-tools/stakeholder-identification-canvas/",
  "MITRE Innovation Toolkit — Community Map: https://itk.mitre.org/toolkit-tools/community-map/"
]
estimated_time
20-30 min

README badge

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