phuryn/pm-skills

stakeholder-map

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan.

소스 보기
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

  1. Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
  1. 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
  1. Place stakeholders in the Power × Interest grid:
High InterestLow Interest
High PowerManage Closely — Regular 1:1s, involve in decisions, seek their input earlyKeep Satisfied — Periodic updates, escalate only critical issues
Low PowerKeep Informed — Regular status updates, invite to demos, gather feedbackMonitor — Light-touch updates, available on request
  1. 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
  1. Create a communication plan table:
StakeholderRolePowerInterestStrategyFrequencyChannelKey Message
  1. 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

같은 저장소의 Skills

더 많은 Skills

모든 Skills
phuryn
커뮤니티

create-prd

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

설치 수
3
GitHub Stars
2.6만
업데이트
7월 3일
phuryn
커뮤니티

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

설치 수
2
GitHub Stars
2.6만
업데이트
7월 3일
phuryn
커뮤니티

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

설치 수
2
GitHub Stars
2.6만
업데이트
7월 3일
phuryn
커뮤니티

beachhead-segment

Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.

설치 수
2
GitHub Stars
2.6만
업데이트
7월 3일