stakeholder-power-mapping

Apply stakeholder and power mapping whenever the user is navigating organizational decisions, driving change, launching a product, building alignment, or trying to understand why something keeps getting blocked. Triggers on phrases like "why won't people adopt this?", "who do I need to convince?", "this keeps getting blocked", "how do I get buy-in?", "who are the key players?", "there's political resistance", "how do I manage stakeholders?", "who has influence here?", "someone is sabotaging this", or any situation where human actors, organizational dynamics, or change management are involved. Also trigger when a technically sound plan is failing for non-technical reasons — the real constraint is often human, not systemic. Never skip this skill when organizational change or adoption is involved.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "stakeholder-power-mapping" with this command: npx skills add andurilcode/skills/andurilcode-skills-stakeholder-power-mapping

Stakeholder & Power Mapping

Core principle: Every system exists within a social and organizational context. The technically correct solution fails if the wrong people oppose it, if key influencers aren't engaged, or if incentives are misaligned. Mapping stakeholders and power dynamics before acting is as important as mapping the technical system.


The Core Process

Step 1: Identify All Stakeholders

Cast wide — include everyone who:

  • Decides: Has authority to approve, veto, or fund
  • Influences: Shapes the opinions of decision-makers without formal authority
  • Implements: Will execute or use the outcome
  • Is affected: Will experience the consequences (even without a voice)
  • Could block: Has the ability to slow, derail, or resist (formally or informally)

Don't limit to the obvious ones. Silent stakeholders are often the most dangerous.

Step 2: Assess Power & Interest

For each stakeholder, assess:

  • Power: How much influence do they have over this outcome? (Low / Medium / High)
  • Interest: How much do they care about this outcome? (Low / Medium / High)
  • Current stance: Actively supportive / Neutral / Resistant / Unknown

Step 3: Map Relationships

  • Who influences whom? (The real org chart is rarely the official one)
  • Who are the trusted advisors of key decision-makers?
  • Are there alliances or coalitions — groups who move together?
  • Are there existing tensions between stakeholders that will play out in this decision?

Step 4: Understand Motivations

For each key stakeholder:

  • What do they want from this situation? (stated goal)
  • What do they need (underlying interest, often unstated)?
  • What do they fear (the loss or risk they're avoiding)?
  • What do they value (the lens through which they evaluate options)?

People rarely oppose things because they're irrational. They have reasons. Find them.

Step 5: Design the Engagement Strategy

Based on the map, decide:

  • Who needs to be activated (turned from neutral to supportive)?
  • Who needs to be managed (their concerns addressed before they become blockers)?
  • Who needs to be informed (but not deeply involved)?
  • Who should be brought in first to create momentum?

Power/Interest Grid

Place each stakeholder in the appropriate quadrant:

High    │  KEEP SATISFIED     │  MANAGE CLOSELY     │
Power   │  (Engage carefully, │  (Key players —     │
        │   meet their needs) │   highest priority) │
        ├─────────────────────┼─────────────────────┤
Low     │  MONITOR            │  KEEP INFORMED      │
Power   │  (Low effort,       │  (Engage regularly, │
        │   watch for shifts) │   get their input)  │
        └─────────────────────┴─────────────────────┘
              Low Interest           High Interest

Output Format

👥 Stakeholder Map

StakeholderRolePowerInterestStanceKey motivation
[Name/Role][Their function]High/Med/LowHigh/Med/LowSupport/Neutral/Resist[What they care about]

🕸️ Influence Network

Key relationships to understand:

  • Decision-makers: Who has final say?
  • Key influencers: Who shapes the decision-makers' views?
  • Gatekeepers: Who controls access to the decision-makers?
  • Coalitions: Which stakeholders move together?
  • Tensions: Which stakeholder relationships are already strained?

⚠️ Risk Stakeholders

Stakeholders who could block or derail:

  • Who: [Name/role]
  • How they could block: [Specific mechanism]
  • Why they might resist: [Their underlying concern]
  • How to mitigate: [Engagement approach]

🎯 Engagement Strategy

Priority tier 1 — Manage closely (High power, High interest):

  • [Stakeholder]: [Specific engagement approach and message]

Priority tier 2 — Keep satisfied (High power, Low interest):

  • [Stakeholder]: [What they need, minimum viable engagement]

Priority tier 3 — Keep informed (Low power, High interest):

  • [Stakeholder]: [Communication cadence, how to use their energy positively]

Priority tier 4 — Monitor (Low power, Low interest):

  • [Stakeholder]: [Watch for shifts, low effort]

📣 Sequencing

The order in which you engage stakeholders matters:

  1. Who should be brought in first to build momentum?
  2. Who needs to see other supporters before they'll move?
  3. Who is a multiplier — their endorsement convinces others?
  4. Who should be engaged last (after critical mass is established)?

💬 Messaging by Stakeholder Type

Different stakeholders need different framings of the same initiative:

Stakeholder typeWhat they care aboutHow to frame the proposal
ExecutiveCost, risk, strategic alignment[Frame in their terms]
EngineeringTechnical quality, workload[Frame in their terms]
ProductUser impact, roadmap[Frame in their terms]
OperationsStability, process change[Frame in their terms]

Resistance Patterns

Understand why people resist — the response is different for each:

Type of resistanceRoot causeResponse
Rational disagreementThey see a real flawEngage with the argument, not the person
Fear of changeLoss of comfort/competenceReduce the change burden, involve them early
TerritorialPerceived threat to their domainGive them ownership of part of it
Incentive misalignmentTheir success metric opposes the changeChange the metric or show how it aligns
Information gapThey don't understand the full pictureBetter communication, earlier involvement
Trust deficitPast bad experiences with similar changesAcknowledge history, build incrementally
PoliticalOpposing someone associated with the initiativeNavigate through mutual allies

Thinking Triggers

  • "Who benefits from the current state and has a reason to resist this?"
  • "Who has informal influence that doesn't show up on the org chart?"
  • "Whose endorsement would move the most people?"
  • "What does each key stakeholder stand to lose if this succeeds?"
  • "Who should hear about this before the formal announcement?"
  • "What's the minimum viable coalition needed to move this forward?"

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

red-teaming

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

inversion-premortem

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

cognitive-bias-detection

No summary provided by upstream source.

Repository SourceNeeds Review