discover-stakeholder-summary

Name: discover-stakeholder-summary
Author: product-on-purpose

486stars64forks

How to install discover-stakeholder-summary?

product-on-purpose/pm-skills/discover-stakeholder-summary

$npx -y skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary

Installs into the current project.

Summary

Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Use at project kickoff, when taking over from another PM, or when resistance signals misalignment. For the update you send to those stakeholders, use found

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Stakeholder Summary
3
4	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.
5
6	## When to Use
7
8	- At the start of a new project or initiative to map the landscape
9	- When taking over an existing project from another PM
10	- Before major decision points that require cross-functional buy-in
11	- When experiencing resistance or misalignment mid-project
12	- During organizational changes that shift stakeholder dynamics
13	- When preparing communication strategies for launches or changes
14
15	## When NOT to Use
16
17	- You need the async update you will SEND to stakeholders -> use `foundation-stakeholder-update`; this skill maps them, that one talks to them
18	- You are preparing for one specific high-stakes meeting -> use `foundation-meeting-brief`
19	- You need customer research synthesis rather than an influence map -> use `discover-interview-synthesis`
20	- You want a persona to design or market against -> use `foundation-persona`
21
22	## Instructions
23
24	When asked to create a stakeholder summary, follow these steps:
25
26	1. Identify All Stakeholders
27	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.
28
29	2. Assess Influence and Interest
30	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.
31
32	3. Understand Their Perspective
33	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.
34
35	4. Map Relationships
36	Identify key dependencies, alliances, and potential conflicts between stakeholders. Understanding who influences whom helps you navigate organizational dynamics.
37
38	5. Categorize by Engagement Level
39	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.
40
41	6. Plan Communication
42	For high-priority stakeholders, define communication cadence, preferred channels, and key messages. Good stakeholder management is proactive, not reactive.
43
44	7. Identify Risks and Mitigations
45	Note where stakeholder concerns could derail the project and plan how to address them. Early attention to resistant stakeholders prevents surprises.
46
47	## Output Format
48
49	Use the template in `references/TEMPLATE.md` to structure the output. A complete summary fills every template section: Overview; Stakeholder Map; Stakeholder Profiles; Detailed Stakeholder Analysis; Key Relationships; Communication Plan; Risk Mitigation; Action Items; and Document History.
50
51	## Quality Checklist
52
53	Before finalizing, verify:
54
55	- [ ] All significant stakeholders are identified (not just obvious ones)
56	- [ ] Influence and interest assessments are realistic, not wishful
57	- [ ] Concerns are documented from stakeholder's perspective, not dismissed
58	- [ ] Relationships and dependencies are mapped
59	- [ ] Communication plan is specific and actionable
60	- [ ] Resistant stakeholders have mitigation strategies
61
62	## Examples
63
64	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type

discover-stakeholder-summary

486stars64forks

View on GitHub

How to install discover-stakeholder-summary?

product-on-purpose/pm-skills/discover-stakeholder-summary

$npx -y skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Stakeholder Summary
3
4	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.
5
6	## When to Use
7
8	- At the start of a new project or initiative to map the landscape
9	- When taking over an existing project from another PM
10	- Before major decision points that require cross-functional buy-in
11	- When experiencing resistance or misalignment mid-project
12	- During organizational changes that shift stakeholder dynamics
13	- When preparing communication strategies for launches or changes
14
15	## When NOT to Use
16
17	- You need the async update you will SEND to stakeholders -> use `foundation-stakeholder-update`; this skill maps them, that one talks to them
18	- You are preparing for one specific high-stakes meeting -> use `foundation-meeting-brief`
19	- You need customer research synthesis rather than an influence map -> use `discover-interview-synthesis`
20	- You want a persona to design or market against -> use `foundation-persona`
21
22	## Instructions
23
24	When asked to create a stakeholder summary, follow these steps:
25
26	1. Identify All Stakeholders
27	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.
28
29	2. Assess Influence and Interest
30	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.
31
32	3. Understand Their Perspective
33	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.
34
35	4. Map Relationships
36	Identify key dependencies, alliances, and potential conflicts between stakeholders. Understanding who influences whom helps you navigate organizational dynamics.
37
38	5. Categorize by Engagement Level
39	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.
40
41	6. Plan Communication
42	For high-priority stakeholders, define communication cadence, preferred channels, and key messages. Good stakeholder management is proactive, not reactive.
43
44	7. Identify Risks and Mitigations
45	Note where stakeholder concerns could derail the project and plan how to address them. Early attention to resistant stakeholders prevents surprises.
46
47	## Output Format
48
49	Use the template in `references/TEMPLATE.md` to structure the output. A complete summary fills every template section: Overview; Stakeholder Map; Stakeholder Profiles; Detailed Stakeholder Analysis; Key Relationships; Communication Plan; Risk Mitigation; Action Items; and Document History.
50
51	## Quality Checklist
52
53	Before finalizing, verify:
54
55	- [ ] All significant stakeholders are identified (not just obvious ones)
56	- [ ] Influence and interest assessments are realistic, not wishful
57	- [ ] Concerns are documented from stakeholder's perspective, not dismissed
58	- [ ] Relationships and dependencies are mapped
59	- [ ] Communication plan is specific and actionable
60	- [ ] Resistant stakeholders have mitigation strategies
61
62	## Examples
63
64	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type