shield_lock
金大哥
← 返回 Skill 列表
extension
分类: 营销与增长无需 API Key

stakeholder-power-mapping

在用户处理组织决策、推动变革、推出产品、建立共识或试图理解为什么某些事情总是被阻挠时，应用利益相关者和权力映射。当出现诸如“为什么人们不接受这个？”、“我需要说服谁？”、“这总是被阻拦”、“我如何获得支持？”、“关键人物是谁？”、“存在政治阻力”、“我如何管理利益相关者？”、“这里谁有影响力？”、“有人在破坏这件事”等短语，或者任何涉及人员行为、组织动态或变更管理的情况时触发。此外，在一个技术上合理的计划因非技术原因失败时也应触发——真正的限制往往在于人，而非系统本身。在涉及组织变革或采纳时，永远不要跳过这项技能。

person作者: jakexiaohubgithub
open_in_new仓库download下载资源包

Stakeholder & Power Mapping

Core principle: The technically correct solution fails if the wrong people oppose it, key influencers aren't engaged, or incentives are misaligned. Map the social and organizational context as carefully as the technical system.

The Core Process

Step 1: Identify All Stakeholders

Cast wide — include everyone who:

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

Silent stakeholders are often the most dangerous.

Step 2: Assess Power & Interest

For each stakeholder:

  • Power: Influence over outcome (Low / Medium / High)
  • Interest: How much they care (Low / Medium / High)
  • Current stance: Supportive / Neutral / Resistant / Unknown

Step 3: Map Relationships

  • Who influences whom? (Real org chart ≠ official one)
  • Trusted advisors of key decision-makers?
  • Alliances or coalitions — who moves together?
  • Existing tensions that will play out in this decision?

Step 4: Understand Motivations

For each key stakeholder:

  • Want (stated goal)
  • Need (underlying interest, often unstated)
  • Fear (the loss they're avoiding)
  • Value (the lens they evaluate options through)

People rarely oppose things irrationally. Find the reason.

Step 5: Design the Engagement Strategy

  • Who needs activating (neutral → supportive)?
  • Who needs managing (concerns addressed before they block)?
  • Who needs informing (not deeply involved)?
  • Who comes in first to create momentum?

Power/Interest Grid

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

| Stakeholder | Role | Power | Interest | Stance | Key motivation | |------------|------|-------|----------|--------|---------------| | [Name/Role] | [function] | H/M/L | H/M/L | Support/Neutral/Resist | [what they care about] |

🕸️ Influence Network

  • Decision-makers: Final say
  • Key influencers: Shape decision-makers' views
  • Gatekeepers: Control access
  • Coalitions: Move together
  • Tensions: Already strained relationships

⚠️ Risk Stakeholders

For each who could block or derail:

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

🎯 Engagement Strategy

Tier 1 — Manage closely (High power, High interest):

  • [Stakeholder]: [approach + message]

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

  • [Stakeholder]: [minimum viable engagement]

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

  • [Stakeholder]: [cadence, how to channel their energy]

Tier 4 — Monitor (Low power, Low interest):

  • [Stakeholder]: [watch for shifts]

📣 Sequencing

  1. Who comes first to build momentum?
  2. Who needs to see other supporters before moving?
  3. Who is a multiplier — their endorsement convinces others?
  4. Who comes last (after critical mass)?

💬 Messaging by Stakeholder Type

| Stakeholder type | What they care about | How to frame | |-----------------|---------------------|--------------| | Executive | Cost, risk, strategic alignment | [their terms] | | Engineering | Technical quality, workload | [their terms] | | Product | User impact, roadmap | [their terms] | | Operations | Stability, process change | [their terms] |

Resistance Patterns

| Type | Root cause | Response | |------|-----------|----------| | Rational disagreement | They see a real flaw | Engage the argument | | Fear of change | Loss of comfort/competence | Reduce burden, involve early | | Territorial | Threat to their domain | Give them ownership of part | | Incentive misalignment | Their metric opposes the change | Change metric or show alignment | | Information gap | Don't see the full picture | Better comms, earlier involvement | | Trust deficit | Past bad experiences | Acknowledge history, build incrementally | | Political | Opposing someone tied to the initiative | Navigate through mutual allies |

Thinking Triggers

  • "Who benefits from the current state and has reason to resist?"
  • "Who has informal influence not 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?"