Discover Stakeholder Summary
Scannednpx machina-cli add skill product-on-purpose/pm-skills/discover-stakeholder-summary --openclawname: discover-stakeholder-summary description: Documents stakeholder needs, concerns, and influence for a project or initiative. Use when starting projects, managing complex stakeholder relationships, or ensuring alignment across organizational boundaries. phase: discover version: "2.0.0" updated: 2026-01-26 license: Apache-2.0 metadata: category: research frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose
Stakeholder Summary
A stakeholder summary documents the people and groups who have interest in or influence over a project, capturing their needs, concerns, and relationships. Effective stakeholder management often determines project success more than technical execution, making this document essential for navigating organizational complexity.
When to Use
- At the start of a new project or initiative to map the landscape
- When taking over an existing project from another PM
- Before major decision points that require cross-functional buy-in
- When experiencing resistance or misalignment mid-project
- During organizational changes that shift stakeholder dynamics
- When preparing communication strategies for launches or changes
Instructions
When asked to create a stakeholder summary, follow these steps:
-
Identify All Stakeholders List everyone with a stake in the project: sponsors, approvers, contributors, consumers of the output, and those affected by changes. Cast a wide net initially—you can prioritize later. Include both individuals and groups.
-
Assess Influence and Interest For each stakeholder, evaluate their influence (power to affect the project) and interest (how much they care about outcomes). This determines how much attention each requires.
-
Understand Their Perspective Document what each stakeholder needs from the project, what concerns or risks they perceive, and what a successful outcome looks like to them. When possible, validate these directly through conversation.
-
Map Relationships Identify key dependencies, alliances, and potential conflicts between stakeholders. Understanding who influences whom helps you navigate organizational dynamics.
-
Categorize by Engagement Level Based on influence and interest, determine the appropriate engagement approach: actively manage, keep satisfied, keep informed, or monitor. Different stakeholders need different levels of attention.
-
Plan Communication For high-priority stakeholders, define communication cadence, preferred channels, and key messages. Good stakeholder management is proactive, not reactive.
-
Identify Risks and Mitigations Note where stakeholder concerns could derail the project and plan how to address them. Early attention to resistant stakeholders prevents surprises.
Output Format
Use the template in references/TEMPLATE.md to structure the output.
Quality Checklist
Before finalizing, verify:
- All significant stakeholders are identified (not just obvious ones)
- Influence and interest assessments are realistic, not wishful
- Concerns are documented from stakeholder's perspective, not dismissed
- Relationships and dependencies are mapped
- Communication plan is specific and actionable
- Resistant stakeholders have mitigation strategies
Examples
See references/EXAMPLE.md for a completed example.
Source
git clone https://github.com/product-on-purpose/pm-skills/blob/main/skills/discover-stakeholder-summary/SKILL.mdView on GitHub Overview
Stakeholder Summary documents people and groups with interest or influence, capturing their needs, concerns, and relationships. It helps navigate organizational complexity and secure cross-functional alignment during project initiation and organizational change.
How This Skill Works
Identify all stakeholders and assess their influence and interest. Document each stakeholder's needs, concerns, and success criteria, then map relationships and categorize engagement. Plan communications and risk mitigations using the standard output template.
When to Use It
- At the start of a new project to map stakeholders and expectations.
- When taking over an existing project to understand new dynamics.
- Before major decisions requiring cross-functional buy-in.
- During mid-project resistance or misalignment to re-align efforts.
- During organizational changes that shift stakeholder dynamics and priorities.
Quick Start
- Step 1: Identify all stakeholders.
- Step 2: Assess influence and interest.
- Step 3: Document perspectives and plan engagement.
Best Practices
- Identify all stakeholders, including sponsors, approvers, contributors, consumers, and affected groups.
- Assess influence and interest with a realistic, validated matrix.
- Document needs, concerns, and success criteria from each stakeholder’s perspective.
- Map dependencies and relationships to spot conflicts and influence flows.
- Create a concrete engagement plan with cadence, channels, and key messages.
Example Use Cases
- Launching a new product across product, marketing, sales, and support.
- Migrating a platform where governance and compliance stakeholders must align.
- Redesigning internal processes with cross-department input.
- Regulatory or governance initiatives requiring oversight stakeholder buy-in.
- Turnaround projects where the PM inherits stakeholder relationships and alignment issues.