Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Goal: Identify all stakeholders in a product, map their interests and influence, and clarify communication and decision-making expectations.

​
Tools Required

This skill runs using CORE memory only. No integrations required.

​
Step 1: Define Scope and Context

Clarify what you’re mapping stakeholders for:
  • A specific product or feature decision?
  • An organizational initiative or strategy?
  • A project or launch?
Ask: “Who are all the people and teams that will be affected by or influence this?”

​
Step 2: Brainstorm All Stakeholders

Cast a wide net. List everyone with an interest or influence:
  • Direct users: People using the product daily
  • Product team: Product managers, designers, engineers
  • Leadership: CEO, executives, department heads
  • Support and operations: Customer support, DevOps, admin team
  • Related teams: Sales, marketing, finance, legal, security
  • External stakeholders: Customers, partners, regulators, board members
  • Influencers: Industry analysts, thought leaders, key advocates
Don’t filter yet. Capture everyone.

​
Step 3: Map Power and Interest

Create a 2×2 matrix: Axes:
  • Horizontal (Power/Influence): Low ↔ High (how much control do they have?)
  • Vertical (Interest/Impact): Low ↔ High (how much does this matter to them?)
Plot each stakeholder on the matrix.

​
Step 4: Assign Engagement Strategy

Based on quadrant, define how you’ll engage each stakeholder: High Power, High Interest (Manage Closely)
  • Regular updates and input opportunities
  • Include in key decisions
  • Address concerns proactively
High Power, Low Interest (Keep Satisfied)
  • Periodic updates (don’t overwhelm)
  • Alert if status changes or risks emerge
  • Focus on outcomes that matter to them
Low Power, High Interest (Keep Informed)
  • Share progress regularly
  • Gather input and feedback
  • Make them feel heard
Low Power, Low Interest (Monitor)
  • Minimal communication
  • Share decision outcomes if relevant
  • Escalate only if engagement level changes

​
Step 5: Identify Potential Conflicts

Ask:
  • Are there stakeholders with opposing goals?
  • Who might feel threatened by this decision or change?
  • Are there regulatory or compliance concerns?
  • What assumptions are each stakeholder making?
Note tensions explicitly. Plan how to address them.

​
Step 6: Create Communication Plan

For each stakeholder group:
  • Frequency: How often will you update them?
  • Format: Email, meetings, Slack, dashboards?
  • Content: What matters to them? (timeline, ROI, risk, user impact)
  • Feedback loop: How will you gather and respond to their input?

​
Output Format

Stakeholder Map — [Product/Initiative Name] 📊 Stakeholder Grid
Low InterestHigh Interest
High PowerKeep SatisfiedManage Closely
Low PowerMonitorKeep Informed
Manage Closely (High Power, High Interest) [Stakeholder Role/Name]
  • Interest: [What matters to them about this]
  • Concerns: [What are they worried about?]
  • Influence: [What can they approve/block?]
  • Engagement: [How often / format]
  • Key message: [What they need to hear]
[Repeat for each stakeholder]
Keep Satisfied (High Power, Low Interest) [Stakeholder Role/Name]
  • Interest: [Minimal — but what will trigger engagement?]
  • Power: [What can they approve/block?]
  • Engagement: [Monthly update? Escalation triggers?]
  • Key message: [What they care about]
[Repeat]
Keep Informed (Low Power, High Interest) [Stakeholder Role/Name]
  • Interest: [Why does this matter to them?]
  • Engagement: [How often will they hear from you?]
  • Feedback mechanism: [How will you gather their input?]
[Repeat]
Monitor (Low Power, Low Interest) [Stakeholder Role/Name] — [Reason on map]
⚡ Potential Conflicts & Tensions [Conflict 1]
  • Stakeholders: [Who has opposing goals?]
  • The tension: [What are they disagreeing on?]
  • Mitigation: [How will you resolve or manage it?]
[Conflict 2] [Same structure]
📋 Communication Plan [Stakeholder Group] (e.g., Leadership, Product Team, Customer Support)
StakeholderFrequencyFormatKey TopicsFeedback Loop
[Name/Role][Weekly/Bi-weekly/Monthly][Email/Meeting/Slack][What matters to them][How they provide input]
[Name/Role][Frequency][Format][Topics][Feedback method]

​
Edge Cases

  • Conflicting priorities between high-power stakeholders: Document both positions explicitly. Escalate to the decision-maker if you can’t find alignment. Ask: “What outcome matters more — A or B?”
  • Hidden stakeholder emerges later: Revisit the map. Add them to the appropriate quadrant. Adjust communication plan and timeline if they’re in “Manage Closely.”
  • Stakeholder role changes mid-project: Update their position on the grid. Adjust engagement level accordingly.
  • Too many stakeholders: Consolidate by role or team. You don’t need individual entries for every person if they share interests (e.g., “Engineering team”).
  • Stakeholder not being transparent about concerns: Watch for indirect signals (delays, pushback, absence). Ask directly: “I notice [behavior]. What concerns do you have?”
  • External stakeholder with veto power: Clarify the scope of their veto. What do they control? What’s negotiable? Map this explicitly.