stakeholder-map
phuryn/pm-skills
Build a power/interest grid to map stakeholders and create targeted communication strategies.
What is stakeholder-map?
This skill helps you identify and classify stakeholders on a power/interest matrix, then develop a tailored communication plan for each group. Use it when managing stakeholders across projects, preparing launches, aligning cross-functional teams, or planning engagement strategies.
- Identify all relevant stakeholders (executives, teams, partners, users) for a given initiative
- Classify stakeholders on power (influence) and interest (engagement) dimensions
- Place stakeholders in a 2×2 grid: Manage Closely, Keep Satisfied, Keep Informed, Monitor
- Recommend communication frequency, format, and key messages per quadrant
- Create a structured communication plan table with stakeholder details and strategies
- Flag potential conflicts and suggest alignment approaches
How to install stakeholder-map
npx skills add https://github.com/phuryn/pm-skills --skill stakeholder-mapHow to use stakeholder-map
- 1.Gather context: collect org charts, project briefs, or team rosters if available, or describe the initiative
- 2.List all stakeholders: identify executives, team leads, partners, and end users relevant to the project
- 3.Assess each stakeholder on power (ability to influence) and interest (how much they're affected)
- 4.Plot stakeholders on the power/interest grid and assign to one of four quadrants
- 5.For each quadrant, define communication frequency, format, and key messages
- 6.Create a communication plan table documenting stakeholder, role, strategy, and channel
- 7.Identify conflicting stakeholder interests and propose alignment strategies
- 8.Save the stakeholder map and plan as a markdown document for reference and sharing
Use cases
- Preparing for a product launch by identifying who needs what information and when
- Aligning cross-functional teams by clarifying stakeholder roles and communication needs
- Managing organizational change by ensuring executives and affected teams stay engaged
- Planning a new initiative by mapping internal and external stakeholders upfront
- Resolving stakeholder misalignment by identifying competing interests and communication gaps
- Product managers planning launches or major initiatives
- Project managers coordinating across teams and departments
- Leaders managing organizational change or cross-functional alignment
- Executives preparing for board or investor communications
- Teams onboarding new stakeholders or scaling projects
stakeholder-map FAQ
Start with your best estimate based on their role and involvement. You can refine the classification as you learn more about the project and their actual influence or engagement.
Review it at major project milestones or when team composition, scope, or priorities shift. Stakeholder positions may move as the project evolves.
Flag the conflict explicitly in your analysis. Propose alignment strategies such as shared goals, trade-offs, or escalation paths to a common decision-maker.
Yes. External stakeholders (partners, vendors, customers, regulators) can be mapped the same way. Adjust communication channels and frequency to suit external relationships.
Keep them informed with light-touch updates and make them available on request. They may become more engaged later, so maintain the relationship without heavy investment.
Full instructions (SKILL.md)
Source of truth, from phuryn/pm-skills.
name: stakeholder-map description: "Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement."
Stakeholder Mapping & Communication Plan
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
Context
You are helping build a stakeholder map for $ARGUMENTS.
If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.
Instructions
-
Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
-
Classify each stakeholder on two dimensions:
- Power (High/Low): Their ability to influence decisions, resources, or outcomes
- Interest (High/Low): How much the project directly affects them or how engaged they are
-
Place stakeholders in the Power × Interest grid:
High Interest Low Interest High Power Manage Closely — Regular 1:1s, involve in decisions, seek their input early Keep Satisfied — Periodic updates, escalate only critical issues Low Power Keep Informed — Regular status updates, invite to demos, gather feedback Monitor — Light-touch updates, available on request -
For each quadrant, recommend:
- Communication frequency (daily, weekly, bi-weekly, monthly)
- Communication format (1:1, email, Slack, meeting, dashboard)
- Key messages and framing
- Potential risks if this stakeholder is neglected
-
Create a communication plan table:
Stakeholder Role Power Interest Strategy Frequency Channel Key Message -
Flag potential conflicts: Identify stakeholders with competing interests and suggest alignment strategies.
Think step by step. Save the stakeholder map as a markdown document.
Further Reading
Related skills
More from phuryn/pm-skills and the wider catalog.
startup-canvas
Generate a comprehensive Startup Canvas combining 9-section Product Strategy with Business Model for new products.
summarize-interview
Transform interview transcripts into structured summaries with JTBD, satisfaction signals, and action items.
summarize-meeting
Transform meeting transcripts into structured notes with decisions, action items, and clear ownership.
swot-analysis
Identify strengths, weaknesses, opportunities, and threats with strategic recommendations for competitive positioning.
test-scenarios
Generate comprehensive test scenarios from user stories with objectives, conditions, steps, and expected outcomes.
user-personas
Generate 3 research-backed user personas with jobs-to-be-done, pain points, and behavioral insights.