| name | stakeholder-discovery |
| type | workflow |
| family | workflow |
| rigor | full |
| description | Use when projects involve multiple stakeholders, decision-makers, or affected parties—maps motivations and power dynamics. |
| keywords | stakeholders, audience-mapping, motivations, power-dynamics, discovery, decision-makers |
| compatibility | Claude Code and compatible agent products |
| requires | [] |
| enhances | ["buyer-persona","prd-writing","stakeholder-review","executive-briefing"] |
| sources_pdf | ["Scaling People (Johnson)","High Output Management (Grove)","Crucial Conversations (Grenny)","The Making of a Manager (Zhuo)","HBR Guide to Managing Up (HBR)"] |
| sources_web | ["SVPG: Stakeholder Management vs. Engagement","Silicon Valley Product Group: Stakeholder Identification"] |
Overview
Stakeholder-discovery is the process of mapping the "organizational ecosystem" to ensure you have the necessary alignment and safety to proceed. It distinguishes between those who have opinions and those who have "veto power," ensuring that critical relationships are cultivated early.
Iron Law
NO DELIVERABLE WITHOUT A VALIDATED STAKEHOLDER MAP
Late-stage "vetoes" are a failure of discovery. Mapping power and interests early is the difference between a smooth launch and an organizational roadblock.
State Machine
digraph stakeholder_discovery_flow {
"Start" [shape=doublecircle];
"Step 1: Identify & Categorize Stakeholders" [shape=box];
"Step 2: Power/Interest Analysis" [shape=box];
"Step 3: Motivation Audit (Mutual Purpose)" [shape=box];
"Gate: Map Validation" [shape=diamond];
"Step 4: Establish Engagement Cadence" [shape=box];
"Done: Stakeholder Context Established" [shape=doublecircle];
"Start" -> "Step 1: Identify & Categorize Stakeholders";
"Step 1: Identify & Categorize Stakeholders" -> "Step 2: Power/Interest Analysis";
"Step 2: Power/Interest Analysis" -> "Step 3: Motivation Audit (Mutual Purpose)";
"Step 3: Motivation Audit (Mutual Purpose)" -> "Gate: Map Validation";
"Gate: Map Validation" -> "Step 4: Establish Engagement Cadence" [label="valid"];
"Gate: Map Validation" -> "Step 1: Identify & Categorize Stakeholders" [label="invalid"];
"Step 4: Establish Engagement Cadence" -> "Done: Stakeholder Context Established";
}
When to Use This Skill
- At the start of any cross-functional project.
- When you are new to a role or organization (mapping the "two and two").
- When a project requires approval from multiple departments (Finance, Legal, HR, etc.).
- When you feel "sideways management" is lacking or obstacles are appearing unexpectedly.
When NOT to Use This Skill
- For independent tasks that have no impact on others and require no external approval.
- For small, routine tasks within a single, already-aligned team.
Core Process
Step 1: Identify & Categorize Stakeholders
- Identify "True" Stakeholders: Distinguish between those who offer opinions and those with veto power—the ability to prevent a product or project from launching. (Source: SVPG/Cagan)
- Map the "Two and Two": Identify the people and roles two levels below you and two levels above you. Understand what drives them. (Source: Johnson, Scaling People)
- Sideways Identification: Actively look for peers and other leaders who might create or prevent obstacles. (Source: Johnson, Scaling People)
