
Stakeholder Management
- 1 installs
- Updated April 27, 2026
- fabioc-aloha/alex-cognitive-architecture
Provides influence mapping, communication strategies, and expectation management patterns for driving outcomes across complex organizations without direct authority.
About
Covers stakeholder influence mapping, communication strategy, and expectation management for leaders working across complex organizations. Used when planning how to align executives, peers, and teams to move a direction without direct authority.
- Frames stakeholders as levers, not obstacles
- Targets directors influencing execs and peers
Stakeholder Management by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 8, 2026 (Skillselion catalog sync)
npx skills add https://github.com/fabioc-aloha/alex-cognitive-architecture --skill stakeholder-managementAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | April 27, 2026 |
| Repository | fabioc-aloha/alex-cognitive-architecture ↗ |
What it does
Provides influence mapping, communication strategies, and expectation management patterns for driving outcomes across complex organizations without direct authority.
Files
Skill: Stakeholder Management
Influence mapping, communication strategies, and expectation management for complex organizations.
Metadata
| Field | Value |
|---|---|
| Skill ID | stakeholder-management |
| Version | 1.0.0 |
| Category | Leadership |
| Difficulty | Advanced |
| Prerequisites | None |
| Related Skills | executive-storytelling, coaching-techniques, frustration-recognition |
---
Overview
Stakeholder management is the art of achieving outcomes through others—especially when you lack direct authority. For directors, this means influencing executives, aligning peers, and enabling teams.
Core Principle
Stakeholders aren't obstacles—they're levers. The question is: what do they need to move your direction?
---
Module 1: Stakeholder Mapping
The Power-Interest Grid
| Low Interest | High Interest | |
|---|---|---|
| High Power | Keep Satisfied | Manage Closely |
| Low Power | Monitor | Keep Informed |
Mapping Process
1. List all stakeholders affected by or affecting your initiative 2. Assess power (decision authority, resource control, influence) 3. Assess interest (how much they care about outcomes) 4. Plot on grid 5. Develop strategy per quadrant
Stakeholder Profiles
For each key stakeholder, document:
| Field | Purpose |
|---|---|
| Name/Role | Who they are |
| Power Level | Decision authority |
| Interest Level | Engagement level |
| Current Position | Support, oppose, neutral |
| Desired Position | Where you need them |
| Key Concerns | What they worry about |
| Motivators | What they care about |
| Communication Preference | How to reach them |
Example Profile
## Stakeholder: VP of Engineering
- **Power**: High (controls development resources)
- **Interest**: Medium (not primary sponsor)
- **Current**: Neutral-skeptical
- **Desired**: Active supporter
- **Concerns**: Timeline risk, team bandwidth
- **Motivators**: Technical excellence, team morale
- **Preference**: Data-driven, short meetings
- **Strategy**: Show technical feasibility, minimize scope creep---
Module 2: Influence Strategies
Influence Without Authority
| Strategy | When to Use | Tactics |
|---|---|---|
| Reciprocity | Building long-term allies | Do favors first, bank goodwill |
| Coalition | Facing resistance | Build supporter network |
| Evidence | Skeptical stakeholders | Data, pilots, proof points |
| Authority | Borrowed credibility | Executive sponsor, expert endorsement |
| Scarcity | Creating urgency | Limited window, competitive pressure |
| Social proof | Risk-averse stakeholders | Industry examples, peer adoption |
The Stakeholder Ladder
Move stakeholders progressively:
Opponent → Skeptic → Neutral → Supporter → ChampionSmall wins at each stage build momentum.
Resistance Patterns
| Resistance Type | Root Cause | Counter |
|---|---|---|
| Fear of unknown | Uncertainty | Education, pilots |
| Loss of power | Territory threat | Involvement, shared credit |
| Resource concern | Budget/time | Clear scope, trade-offs |
| Past failure | Burned before | Different approach, risk mitigation |
| Not invented here | Pride | Co-creation, acknowledgment |
---
Module 3: Communication Strategies
Communication Frequency
| Stakeholder Type | Frequency | Medium |
|---|---|---|
| Executive sponsor | Weekly | 1:1, brief updates |
| Manage closely | 2x/week | Meetings, direct calls |
| Keep satisfied | Bi-weekly | Email summaries |
| Keep informed | Monthly | Newsletters, dashboards |
| Monitor | As needed | Include in broadcasts |
Message Tailoring
| Audience | Focus On | Avoid |
|---|---|---|
| Executives | Outcomes, ROI, decisions | Technical details |
| Technical leads | Feasibility, architecture | Business jargon |
| Finance | Costs, savings, ROI | Feature details |
| Legal | Risks, compliance | Jargon, assumptions |
| End users | Benefits, ease, timeline | Complexity |
The SPIN Framework for Stakeholder Conversations
| Stage | Purpose | Example Questions |
|---|---|---|
| Situation | Understand context | "What's your current process?" |
| Problem | Surface pain points | "What challenges do you face?" |
| Implication | Deepen urgency | "What happens if this continues?" |
| Need-payoff | Co-create solution | "How would X help you?" |
---
Module 4: Expectation Management
Setting Expectations
| Principle | Implementation |
|---|---|
| Under-promise, over-deliver | Commit to achievable, stretch for more |
| Early warning | Surface problems before they escalate |
| No surprises | Executives hate learning bad news publicly |
| Clear trade-offs | "We can do X or Y, not both" |
The Expectations Triangle
[Scope]
/ \
/ \
[Time]---[Resources]Rule: You can only fix two. If scope increases, either time extends or resources grow.
Difficult Conversations
Framework: SBI-I (Situation-Behavior-Impact-Intent)
1. Situation: "In yesterday's meeting..." 2. Behavior: "When you questioned the timeline publicly..." 3. Impact: "The team felt undermined, and sponsors lost confidence" 4. Intent: "I'd like to understand your concerns so we can address them offline"
Managing Up
| Challenge | Approach |
|---|---|
| Unclear priorities | Ask for explicit ranking |
| Micromanagement | Proactive updates, build trust |
| Unavailable sponsor | Brief async updates, clear asks |
| Changing requirements | Document trade-offs, get sign-off |
| Unrealistic timelines | Data-driven pushback, alternatives |
---
Module 5: Conflict Resolution
Conflict Modes (Thomas-Kilmann)
| Mode | When Appropriate |
|---|---|
| Competing | Urgent, right matters |
| Collaborating | Time available, relationship matters |
| Compromising | Moderate importance, both must move |
| Avoiding | Trivial issue, cooling off needed |
| Accommodating | Relationship > issue |
De-escalation Tactics
1. Slow down - Pause before responding 2. Listen fully - Don't interrupt, summarize back 3. Find common ground - "We both want X..." 4. Separate people from problem - Attack issue, not person 5. Propose next step - Move from emotion to action
Stakeholder Conflicts
When stakeholders disagree with each other:
1. Clarify positions - Ensure each understands the other 2. Find shared interests - Usually exist beneath positions 3. Propose options - Multiple paths forward 4. Escalate if needed - To appropriate decision-maker 5. Document decision - Prevent re-litigation
---
Module 6: RACI and Governance
RACI Matrix
| Role | Definition |
|---|---|
| Responsible | Does the work |
| Accountable | Owns the decision (one per task) |
| Consulted | Input before decision |
| Informed | Told after decision |
Governance Cadence
| Forum | Frequency | Purpose | Attendees |
|---|---|---|---|
| Steering Committee | Monthly | Decisions, escalations | Sponsors, leads |
| Working Group | Weekly | Progress, blockers | Doers, SMEs |
| Stakeholder Update | Bi-weekly | Status, alignment | All interested |
| 1:1 with Sponsor | Weekly | Issues, guidance | You + sponsor |
---
Quick Reference
Stakeholder Checklist
- [ ] Stakeholder map created
- [ ] Power-interest grid plotted
- [ ] Key profiles documented
- [ ] Communication plan defined
- [ ] Influence strategy per stakeholder
- [ ] RACI clarified
- [ ] Governance cadence established
- [ ] Expectations set and documented
Communication Cheat Sheet
| Stakeholder Says | They Mean | Your Move |
|---|---|---|
| "Keep me informed" | Don't surprise me | Regular brief updates |
| "I need to think about it" | Not convinced | Address concerns |
| "Sounds good" | Neutral, not committed | Get explicit commitment |
| "Let's discuss offline" | Issue is sensitive | Private meeting |
| "I have concerns" | Resistance building | Dig deeper immediately |
Red Flags
| Signal | Meaning | Action |
|---|---|---|
| Sponsor stops attending | Losing interest | Re-engage urgently |
| New stakeholder appears | Power shift | Quick mapping, engagement |
| Silence from key player | Brewing resistance | Reach out proactively |
| Scope creep from exec | Expectations mismatch | Clarify trade-offs |
---
Activation Patterns
| Trigger | Response |
|---|---|
| "stakeholder", "influence", "politics" | Full skill activation |
| "resistance", "pushback", "blocking" | Module 2 + 5 |
| "RACI", "governance", "who decides" | Module 6 |
| "manage expectations", "scope creep" | Module 4 |
| "stakeholder map", "power interest" | Module 1 |