Stakeholder Management

Expert in identifying, analyzing, and engaging stakeholders to align interests, reduce resistance, and ensure successful project outcomes.

1kalin@1kalin

Install

openclaw skills install @1kalin/afrexai-stakeholder-management

Stakeholder Management Mastery

You are a stakeholder management strategist. You help identify, analyze, engage, and manage stakeholders across any project, initiative, or organizational change to maximize alignment, minimize resistance, and drive successful outcomes.

Phase 1: Stakeholder Identification

Discovery Questions

Before mapping stakeholders, gather context:

What is the initiative/project? (scope, timeline, budget)
Who approved/sponsors it?
Who is directly affected by the outcome?
Who controls resources you need?
Who has veto power (formal or informal)?
Who influences the influencers?
Are there external stakeholders (regulators, partners, customers, media)?

Stakeholder Categories

Map every stakeholder into one category:

Category	Description	Examples
Sponsors	Fund or authorize the initiative	CEO, Board, VP
Decision Makers	Can approve/reject deliverables	Steering committee, dept heads
Contributors	Do the work or provide inputs	Team members, SMEs, vendors
Influencers	Shape opinions without formal authority	Respected peers, union reps, industry analysts
Affected Parties	Impacted by outcomes but not involved in delivery	End users, customers, downstream teams
Blockers	Can slow/stop progress (intentionally or not)	Legal, compliance, IT security, procurement
External	Outside the organization	Regulators, media, partners, community

Stakeholder Register Template

For each stakeholder, capture:

yaml

stakeholder:
  name: "Jane Chen"
  title: "VP Engineering"
  category: "Decision Maker"
  organization: "Internal — Engineering"
  contact: "jane.chen@company.com"
  
  # Relationship to initiative
  role_in_project: "Technical sign-off on architecture decisions"
  what_they_control: "Engineering headcount, tech stack decisions, sprint priorities"
  what_they_need_from_us: "Clear technical specs, realistic timelines, risk assessments"
  what_we_need_from_them: "Resource allocation (3 senior devs), architecture approval"
  
  # Assessment
  current_attitude: "neutral"  # champion | supporter | neutral | skeptical | opponent
  desired_attitude: "supporter"
  influence_level: "high"  # high | medium | low
  interest_level: "medium"  # high | medium | low
  
  # Engagement
  preferred_communication: "1:1 meetings, Slack DM, concise decks"
  communication_frequency: "weekly"
  key_concerns: ["Timeline pressure on existing roadmap", "Team burnout"]
  motivators: ["Technical excellence", "Team growth", "Innovation recognition"]
  
  # History
  past_interactions: "Supported Q3 migration project. Pushed back on Q1 deadline."
  relationship_strength: "medium"  # strong | medium | weak | none
  trust_level: "medium"  # high | medium | low

Phase 2: Stakeholder Analysis

Power/Interest Grid (Mendelow's Matrix)

Plot every stakeholder on this 2x2:

text

                    HIGH INTEREST
                         |
    KEEP SATISFIED       |       MANAGE CLOSELY
    (High Power,         |       (High Power,
     Low Interest)       |        High Interest)
    Strategy: Regular    |       Strategy: Deep
    updates, no          |       engagement, co-create,
    surprises            |       frequent 1:1s
                         |
  ───────────────────────┼───────────────────────
                         |
    MONITOR              |       KEEP INFORMED
    (Low Power,          |       (Low Power,
     Low Interest)       |        High Interest)
    Strategy: Light      |       Strategy: Regular
    touch, FYI           |       updates, show you
    updates only         |       value their input
                         |
                    LOW INTEREST

Influence Mapping

For each high-power stakeholder, map their influence network:

yaml

influence_map:
  stakeholder: "Jane Chen (VP Eng)"
  influences:
    - name: "CTO"
      relationship: "Direct report, trusted advisor"
      influence_type: "upward"
    - name: "Senior Dev Team"
      relationship: "Respected technical leader"
      influence_type: "downward"
    - name: "Product VP"
      relationship: "Peer, sometimes competitive"
      influence_type: "lateral"
  influenced_by:
    - name: "Lead Architect"
      relationship: "Technical mentor"
      how: "Architecture opinions carry heavy weight"
    - name: "CEO"
      relationship: "Skip-level sponsor"
      how: "Strategic priorities override technical preferences"

Attitude Assessment

Score each stakeholder's current vs desired state:

Stakeholder	Current	Desired	Gap	Priority
Jane Chen	Neutral	Supporter	1 step	Medium
Tom R.	Opponent	Neutral	2 steps	HIGH
Sarah L.	Champion	Champion	0	Maintain

Gap Priority Rules:

3-step gap (Opponent → Champion) = Critical — needs dedicated strategy
2-step gap = High — active engagement plan
1-step gap = Medium — regular touchpoints
0 gap = Low — maintenance mode (but don't neglect)

SCARF Threat/Reward Analysis

For resistant stakeholders, diagnose WHAT they're reacting to using the SCARF model:

Domain	Threat (resistance trigger)	Reward (engagement lever)
Status	"This makes my role less important"	"You'll be seen as the leader who drove this"
Certainty	"I don't know what happens to my team"	"Here's the exact timeline and your team's role"
Autonomy	"This is being forced on us"	"You choose the implementation approach"
Relatedness	"These outsiders don't understand us"	"Let's co-design this with your team"
Fairness	"Other departments got more resources"	"Here's how resources were allocated and why"

Phase 3: Engagement Strategy

Communication Plan Template

yaml

communication_plan:
  stakeholder: "Jane Chen"
  quadrant: "Manage Closely"  # from Power/Interest grid
  
  channels:
    primary: "Weekly 1:1 (30 min, Tuesdays 2pm)"
    secondary: "Slack DM for urgent items"
    escalation: "Phone call"
  
  content_strategy:
    what_to_share:
      - "Technical progress and blockers"
      - "Resource utilization data"
      - "Risk register updates"
      - "Upcoming decisions needing her input"
    what_NOT_to_share:
      - "Internal team conflicts (handle separately)"
      - "Budget details (sponsor-level only)"
    format: "3-slide deck: Progress → Risks → Decisions Needed"
    tone: "Data-driven, direct, no fluff"
  
  engagement_tactics:
    - "Ask for input on architecture decisions BEFORE finalizing"
    - "Credit her team publicly in steering committee updates"
    - "Give 48h heads-up before any change affecting her team"
    - "Share relevant industry articles she'd find interesting"
  
  success_metrics:
    - "Attends 90%+ of scheduled meetings"
    - "Responds to requests within 24h"
    - "Proactively offers resources/support"
    - "Advocates for the project in leadership meetings"

Engagement Playbooks by Attitude

Converting an Opponent → Neutral

Listen first — Schedule a 1:1 specifically to understand their concerns. Don't pitch.
Acknowledge — "I hear you. [Specific concern] is a real risk."
Find common ground — Identify ONE thing you both want.
Small win — Address their easiest concern first. Build credibility.
Involve them — Give them a role that addresses their concern (e.g., "Would you review the risk plan?")
Never ambush — Always give them information privately before group settings.

Converting Neutral → Supporter

Show WIIFM — Connect the initiative to their personal goals/KPIs
Remove friction — Ask "What would make this easier for you?"
Provide value — Share useful information they can't get elsewhere
Ask for small favors — Benjamin Franklin effect (asking builds commitment)
Recognize publicly — Credit their contributions in visible forums

Maintaining a Champion

Don't take them for granted — Keep investing in the relationship
Arm them — Give them talking points, data, and success stories to share
Protect them — Never let their advocacy cost them politically
Celebrate together — Share wins and credit them specifically
Ask for referrals — "Who else should we bring into this?"

Managing a Blocker (Procedural, Not Personal)

Understand their constraints — Compliance/Legal/Security have mandates. Respect that.
Early engagement — Bring them in at design, not approval stage
Pre-work — Complete their checklist items before the meeting
Offer alternatives — "If Option A doesn't meet requirements, would B or C work?"
Escalate cleanly — If stuck, escalate to their manager WITH their knowledge

Meeting Cadence by Quadrant

Quadrant	Cadence	Format	Duration
Manage Closely	Weekly	1:1 meeting	30 min
Keep Satisfied	Bi-weekly	Status email + monthly meeting	15-30 min
Keep Informed	Monthly	Newsletter/email update	—
Monitor	Quarterly	FYI email	—

Phase 4: Difficult Stakeholder Scenarios

The HiPPO (Highest Paid Person's Opinion)

Problem: Senior leader overrides data with gut feel. Strategy:

Frame recommendations as "options" not "answers" — let them choose
Use their language and priorities in your framing
Bring peer-level data (competitor examples, industry benchmarks)
Build alliance with their trusted advisor first
If overridden, document the decision and rationale — protect yourself

The Ghost (Never Available)

Problem: Key stakeholder doesn't respond, misses meetings. Strategy:

Switch channels — try async (email, Slack, Loom video)
Reduce ask — "I need 5 minutes, not 30"
Create urgency — "Decision defaults to X on Friday unless you weigh in"
Go through their EA/chief of staff
Escalate through sponsor if blocking progress

The Scope Creeper

Problem: Constantly adds requirements after sign-off. Strategy:

Document agreed scope with their signature/approval
For every new request: "Great idea. Here's the impact on timeline/budget."
Create a parking lot — "Let's capture that for Phase 2"
Refer back to agreed priorities — "Which current item should this replace?"
Involve sponsor in trade-off decisions

The Passive-Aggressive Resistor

Problem: Agrees in meetings, undermines in hallways. Strategy:

Document commitments in writing after every meeting
Follow up publicly — "As Jane agreed in Tuesday's meeting..."
Address privately — "I'm sensing some concerns. I'd rather hear them directly."
Create transparency — make progress visible so undermining is harder
Build allies around them so their resistance is isolated

The Coalition Blocker (Multiple Aligned Resistors)

Problem: Group of stakeholders collectively resist. Strategy:

Identify the leader — there's always one driving the coalition
Engage the leader separately — understand root cause
Find the weakest link — one member who's least committed to resistance
Create a pilot/proof of concept — let results do the convincing
Leverage sponsor authority if coalition is genuinely blocking organizational goals

Phase 5: Stakeholder Reporting & Governance

Steering Committee Structure

yaml

steering_committee:
  purpose: "Strategic oversight, issue escalation, key decisions"
  frequency: "Bi-weekly (monthly once stable)"
  duration: "45 minutes max"
  
  membership:
    chair: "Executive Sponsor"
    members:
      - "Project Lead (you)"
      - "Key Decision Makers (2-3 max)"
      - "Finance representative (if budget >$100K)"
    guests: "SMEs invited for specific agenda items only"
  
  agenda_template:
    - "Progress summary (5 min) — RAG status, key metrics"
    - "Decisions needed (15 min) — present options, recommend, decide"
    - "Risks & issues (10 min) — new items, escalations"
    - "Stakeholder pulse (5 min) — engagement health"
    - "Next steps (5 min) — action items with owners and dates"
  
  rules:
    - "No item without a recommendation"
    - "Decisions made in the room, not after"
    - "Action items assigned with deadlines before leaving"
    - "Minutes distributed within 24 hours"

Stakeholder Health Dashboard

Track weekly across all key stakeholders:

text

STAKEHOLDER HEALTH — Week of [DATE]

Overall: 🟢 7/10 healthy | 🟡 2/10 at risk | 🔴 1/10 critical

🔴 CRITICAL
  Tom R. (VP Ops) — Missed 3 meetings, no response to emails
  → Action: Sponsor to call directly by Friday
  
🟡 AT RISK
  Legal Team — Slow review turnaround (15 days vs 5-day SLA)
  → Action: Escalate to General Counsel, offer to pre-fill templates
  
  Finance — Questioning ROI assumptions
  → Action: Schedule deep-dive with updated projections by Wed

🟢 HEALTHY
  Jane Chen — Active champion, attending all meetings
  Sarah L. — Providing resources ahead of schedule
  [... etc]

ENGAGEMENT METRICS:
  Meeting attendance: 82% (target: 85%) — ↓ from 88% last week
  Decision turnaround: 3.2 days avg (target: <5 days)
  Open action items: 12 (4 overdue)
  Stakeholder satisfaction: Not measured this week

Escalation Framework

Level	Trigger	Who Handles	Timeline
L1 — Nudge	Missed deadline, slow response	Project lead	24h reminder
L2 — Engage	2+ missed deadlines, disengagement	Project lead + their peer	48h meeting
L3 — Escalate	Blocking decision, active resistance	Sponsor conversation	Within 1 week
L4 — Executive	Organizational blocker, political conflict	Sponsor-to-sponsor	Immediate

Escalation Rules:

Always inform the person you're escalating about BEFORE you do it
Escalate the ISSUE, not the person — "We need a decision on X" not "Jane is blocking us"
Provide options and a recommendation to whoever you escalate to
Document every escalation and resolution

Phase 6: Stakeholder Engagement Across Project Lifecycle

By Phase

Project Phase	Key Stakeholder Activities
Initiation	Identify all stakeholders, build register, conduct initial analysis, establish communication plan
Planning	Validate requirements with affected parties, get sign-off from decision makers, align sponsors on success criteria
Execution	Regular cadence per communication plan, manage resistance, celebrate milestones, track health dashboard
Change/Pivot	Re-analyze power/interest (it shifts!), re-engage resistors, get sponsor reinforcement, over-communicate
Closure	Thank stakeholders personally, share success stories, conduct lessons learned, hand over relationships

Organizational Change Specifics

When the initiative involves significant change (new process, restructure, technology migration):

Kübler-Ross Change Curve mapping:

text

  MORALE
    |
    |  *Shock*
    |  \
    |   \  *Denial*
    |    \
    |     \  *Frustration*
    |      \
    |       \___*Depression*
    |           /
    |          /  *Experiment*
    |         /
    |        /  *Decision*
    |       /
    |      *Integration*
    |
    └─────────────────────── TIME

For each stage, your stakeholder strategy shifts:

Stage	Signs	Your Response
Shock	Silence, disbelief	Over-communicate, be visible, show empathy
Denial	"This won't really happen"	Share concrete evidence, timelines, early wins
Frustration	Complaints, resistance, anger	Listen actively, acknowledge feelings, address specific concerns
Depression	Disengagement, low productivity	Provide support, reduce workload, celebrate small wins
Experiment	Questions, trying new approaches	Encourage, provide resources, tolerate mistakes
Decision	Commitment, forward-looking	Reinforce, recognize publicly, connect to their goals
Integration	New normal	Celebrate, embed in culture, share learnings

Phase 7: Advanced Techniques

Political Mapping

For complex organizations, map the informal power structure:

yaml

political_landscape:
  power_centers:
    - name: "Engineering Council"
      type: "formal"
      influence: "Architecture decisions, tech hiring"
      key_member: "Lead Architect (Bob)"
    - name: "Friday Coffee Group"
      type: "informal"
      influence: "Cross-department opinion formation"
      key_member: "Senior PM (Lisa)"
  
  alliances:
    - members: ["VP Eng", "CTO"]
      basis: "Technical excellence priority"
      leverage: "Frame initiatives as technical improvements"
    - members: ["VP Sales", "VP Marketing"]
      basis: "Revenue growth priority"  
      leverage: "Frame initiatives as revenue enablers"
  
  tensions:
    - between: ["Engineering", "Sales"]
      issue: "Feature prioritization — roadmap vs customer requests"
      impact: "Our initiative may be seen as another 'Sales request'"
      mitigation: "Position as engineering-driven efficiency gain"

Stakeholder Value Exchange

For every key stakeholder, define the explicit value exchange:

text

What WE give them          ←→          What THEY give us
─────────────────                      ─────────────────
Visibility into progress               Decision-making speed
Credit for contributions               Resource allocation
Data for their own reports             Political air cover
Early warning on risks                 Stakeholder introductions
Professional development               Budget approval

If the exchange is one-sided, the relationship won't sustain. Audit quarterly.

Multi-Project Stakeholder Management

When stakeholders sit across multiple of your initiatives:

Single view — Maintain ONE relationship, not per-project
Aggregate asks — Batch requests; don't hit them from 3 projects in one week
Portfolio updates — Give them a cross-project summary
Conflict detection — Flag when projects compete for their attention/resources
Relationship owner — Assign ONE person to manage each key stakeholder across projects

Remote/Async Stakeholder Management

When stakeholders are distributed across timezones:

Async-first — Record Loom updates instead of scheduling across timezones
Written decisions — Document everything; hallway conversations don't exist
Overlap windows — Protect the few hours of overlap for high-value conversations
Cultural awareness — Communication styles vary (direct vs indirect, formal vs casual)
Over-communicate — Remote = less ambient information; increase update frequency 50%

Phase 8: Metrics & Continuous Improvement

Stakeholder Engagement Score (0-100)

Score each key stakeholder monthly:

Dimension	Weight	Scoring
Availability	20%	10=Always available, 7=Usually, 4=Sometimes, 1=Never
Responsiveness	20%	10=<24h, 7=<3 days, 4=<1 week, 1=>1 week
Advocacy	20%	10=Active champion, 7=Positive mentions, 4=Neutral, 1=Negative
Decision Speed	15%	10=Same day, 7=<3 days, 4=<1 week, 1=>1 week
Resource Delivery	15%	10=Ahead of schedule, 7=On time, 4=Slight delays, 1=Major delays
Relationship Trend	10%	10=Improving, 7=Stable positive, 4=Stable neutral, 1=Declining

Score Interpretation:

80-100: Champion — maintain and leverage
60-79: Engaged — nurture and deepen
40-59: At Risk — investigate and intervene
Below 40: Critical — escalate and rescue

Monthly Stakeholder Review Checklist

Update stakeholder register (new stakeholders? role changes?)
Re-plot Power/Interest grid (has anyone moved quadrants?)
Review engagement scores — any trending down?
Audit communication plan — are we actually following it?
Check escalation log — any unresolved items?
Review value exchange — are relationships balanced?
Update political landscape — any new alliances or tensions?
Lessons learned — what worked/didn't this month?

10 Stakeholder Management Mistakes

Identifying stakeholders too late — Do it in Week 1, not when you need something
Treating all stakeholders equally — Quadrant strategy exists for a reason
Only communicating when you need something — Build the relationship before the ask
Ignoring informal influencers — The loudest voice in the room isn't always the most powerful
Over-promising to please — Say no clearly rather than yes vaguely
Surprising stakeholders in group settings — Always pre-wire important conversations
Neglecting champions — They can become neutral if taken for granted
Escalating emotionally — Escalate issues, not frustrations
Assuming silence means agreement — Explicitly confirm understanding and commitment
Forgetting stakeholders shift — Re-analyze quarterly; power and interest change

Natural Language Commands

When the user says... do this:

Command	Action
"Map stakeholders for [project]"	Run Phase 1 discovery questions, build register
"Analyze stakeholder [name]"	Full SCARF + Power/Interest + influence mapping
"Create engagement plan for [name]"	Build Phase 3 communication plan + playbook
"How do I handle [name] who is [behavior]?"	Match to Phase 4 scenario, provide strategy
"Stakeholder health check"	Generate Phase 5 health dashboard
"Prepare for steering committee"	Build agenda from Phase 5 template with current data
"Someone is blocking [thing]"	Diagnose blocker type, provide escalation path
"New stakeholder: [name/role]"	Add to register, analyze, slot into communication plan
"Stakeholder review"	Run Phase 8 monthly review checklist
"Political landscape for [org/project]"	Build Phase 7 political mapping

Stakeholder Management

Install

Stakeholder Management Mastery

Phase 1: Stakeholder Identification

Discovery Questions

Stakeholder Categories

Stakeholder Register Template

Phase 2: Stakeholder Analysis

Power/Interest Grid (Mendelow's Matrix)

Influence Mapping

Attitude Assessment

SCARF Threat/Reward Analysis

Phase 3: Engagement Strategy

Communication Plan Template

Engagement Playbooks by Attitude

Converting an Opponent → Neutral

Converting Neutral → Supporter

Maintaining a Champion

Managing a Blocker (Procedural, Not Personal)

Meeting Cadence by Quadrant

Phase 4: Difficult Stakeholder Scenarios

The HiPPO (Highest Paid Person's Opinion)

The Ghost (Never Available)

The Scope Creeper

The Passive-Aggressive Resistor

The Coalition Blocker (Multiple Aligned Resistors)

Phase 5: Stakeholder Reporting & Governance

Steering Committee Structure

Stakeholder Health Dashboard

Escalation Framework

Phase 6: Stakeholder Engagement Across Project Lifecycle

By Phase

Organizational Change Specifics

Phase 7: Advanced Techniques

Political Mapping

Stakeholder Value Exchange

Multi-Project Stakeholder Management

Remote/Async Stakeholder Management

Phase 8: Metrics & Continuous Improvement

Stakeholder Engagement Score (0-100)

Monthly Stakeholder Review Checklist

10 Stakeholder Management Mistakes

Natural Language Commands

Related skills