stakeholder-identification

Generate a comprehensive, equity-aware stakeholder list for a product initiative.

6.8k|818|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill stakeholder-identification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-identification
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill stakeholder-identification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stakeholder lists written from memory reliably capture executives and vocal users while missing gatekeepers, permission-holders, and marginalized groups who bear the product's consequences. This Skill runs a structured six-step process that surfaces the stakeholders teams systematically overlook before any engagement begins.

Core Features & Use Cases

  • Structured Brainstorm and Categorization: Sorts stakeholders into Allies, Audiences, and Influencers, then tags each with Resources, Permission, or Decision authority to expose who can fund, block, or approve the work.
  • Equity Lens and Bias Check: Explicitly surfaces high-impact, low-power stakeholders and forces the team to name who they defaulted to and who is absent.
  • Priority Narrowing: Reduces the full list to 2-3 priority stakeholders, each with a specific learning question that feeds downstream mapping and engagement planning.
  • Use Case: When scoping a new intake portal, the Skill reveals that customer support agents, IT security, and compliance were missing from the initial list, changing the PRD requirements and rollout plan.

Quick Start

Ask the agent to identify all stakeholders for your initiative, for example: identify stakeholders for migrating all customers to the new billing system by Q4.

Frequently Asked Questions about stakeholder-identification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify stakeholders for a new product initiative?

Run an unfiltered brainstorm of everyone connected to the initiative, then categorize each as Ally, Audience, or Influencer and tag who holds Resources, Permission, or Decision authority. Finish with an equity check and narrow to 2-3 priority stakeholders.

What is the difference between stakeholder identification and stakeholder mapping?

Identification produces a complete list of who exists; mapping prioritizes them using Power versus Interest or Impact versus Power grids. Identification must come first because you cannot prioritize people you have not named.

How do I find missing stakeholders in my stakeholder map?

Apply the R/P/D gap test to find Permission or Decision holders absent from your list, then use the equity lens to surface people who bear the product's costs without power to shape it. A bias check names who you defaulted to and why.

Can I run stakeholder identification as a solo exercise?

Yes, it works solo or as a kickoff workshop. When working alone, use the bias and assumptions step to identify who is absent from your mental model, then validate the list with a cross-functional colleague before proceeding.

When should I not prioritize stakeholders during identification?

Do not cut stakeholders during the brainstorm phase, before understanding their actual influence or impact. Premature filtering is how high-impact, low-power voices get silently dropped; prioritization belongs in the separate mapping step.