Back to prompts
Decision MakingPremiumintermediate
4.7

Map Stakeholders by Influence and Interest

Identify every stakeholder, understand their motivations, and build a targeted engagement strategy for any initiative

Copy & Paste this prompt
I need to map stakeholders for [PROJECT/INITIATIVE/CHANGE].

Context:
- What this is about: [DESCRIBE THE INITIATIVE]
- Organization: [COMPANY / TEAM / COMMUNITY]
- My role: [YOUR POSITION]
- Key challenge: [WHAT MAKES STAKEHOLDER MANAGEMENT TRICKY HERE]

Create a comprehensive stakeholder map:

1. STAKEHOLDER IDENTIFICATION
   List ALL stakeholders (people tend to miss indirect ones):
   - Decision makers (who says yes/no)
   - Influencers (who shapes opinions)
   - End users (who lives with the result)
   - Gatekeepers (who controls access/resources)
   - Affected parties (who is impacted without having a say)
   - Hidden stakeholders (who will care but hasn't been consulted)

2. POWER-INTEREST GRID
   Classify each stakeholder:
   - High Power + High Interest → Manage Closely (key players)
   - High Power + Low Interest → Keep Satisfied (sleeping giants)
   - Low Power + High Interest → Keep Informed (allies and critics)
   - Low Power + Low Interest → Monitor (minimal effort)

3. MOTIVATION ANALYSIS
   For each key stakeholder:
   - What do they want from this? (stated goals)
   - What do they REALLY want? (underlying motivation)
   - What are they afraid of? (hidden concerns)
   - What would make them a champion?
   - What would make them a blocker?

4. ENGAGEMENT STRATEGY
   For each quadrant, define:
   - Communication frequency and format
   - Key messages tailored to their concerns
   - Who should communicate with them (you or someone else?)
   - Specific actions to gain their support

5. RISK ASSESSMENT
   - Which stakeholders are most likely to resist? Why?
   - Which unlikely allies could you recruit?
   - What coalition of support do you need to succeed?
   - Map the "critical path" of approvals needed

6. ONE-PAGE STAKEHOLDER BRIEF
   - Summary table I can reference before every meeting
   - Top 3 stakeholders to focus on this week
#decision-making#strategy#stakeholders#influence#interest

Works with

chatgptclaudegemini

💡 Pro Tips

  • •The stakeholders you forget about are the ones who derail your project — spend 10 minutes listing 'who else could care?'
  • •Understand what stakeholders are afraid of, not just what they want — fear drives resistance more than logic
  • •Map stakeholders BEFORE you need something from them — building relationships under pressure never works

✨ Example Output

Initiative: Migrating the company from Slack to Microsoft Teams

STAKEHOLDER MAP:

MANAGE CLOSELY (High Power, High Interest):
• CTO — Decision maker. Wants cost savings + security. Fears disruption to engineering workflows.
  → Strategy: Weekly 1:1 updates, frame as security + compliance win
• VP Engineering — Key influencer. Her team uses Slack integrations heavily.
  → Strategy: Map every Slack integration to Teams equivalent BEFORE talking to her. Present migration plan, not just the idea.

KEEP SATISFIED (High Power, Low Interest):
• CEO — Will approve budget but doesn't care about the tool. Wants it done quietly.
  → Strategy: Monthly one-slide update. Lead with cost savings number.

KEEP INFORMED (Low Power, High Interest):
• Developer team leads — Will be vocal critics. Love Slack, see Teams as "corporate."
  → Strategy: Involve 2-3 as "migration champions." Let them shape the channel structure.
• Customer support team — Heavy Slack users, worried about downtime.
  → Strategy: Guarantee parallel run period. Give them early access.

HIDDEN STAKEHOLDERS:
• IT Security — Will want to audit Teams permissions. Loop in NOW, not at launch.
• External contractors — Currently in Slack as guests. Need a guest access plan for Teams.

CRITICAL PATH: CTO approval → VP Eng buy-in → Developer champion recruitment → Pilot with one team → Company-wide rollout