```markdown
# Stakeholder Management Skill

## Overview
Expertise in identifying, analyzing, engaging, and managing stakeholders throughout the vendor replacement program to ensure alignment, support, and successful outcomes.

## Stakeholder Analysis Framework

### Stakeholder Identification

**Key Stakeholder Categories:**

**Executive Leadership:**
- CEO/President
- CTO/VP Engineering
- CFO
- COO
- Business Unit Leaders

**Program Sponsors & Decision Makers:**
- Executive Sponsor (primary)
- R&D Leadership
- Finance Director
- Security/Compliance Leadership

**Program Team:**
- Program Manager
- Change Manager
- Technical Lead
- Tool Specialists

**Affected Teams:**
- Development teams
- QA teams
- DevOps teams
- Product managers
- Project managers

**External Stakeholders:**
- Current vendor (account manager, team)
- AI tool vendors
- Customers (if impacted)
- Partners/integrators

**Support Functions:**
- Legal/contracts
- Procurement
- IT/infrastructure
- HR/training
- Communications

### Power-Interest Matrix

**Mapping Framework:**
```markdown
## Power-Interest Grid

               High Power
                   |
     KEEP SATISFIED | MANAGE CLOSELY
    ┌──────────────┼──────────────┐
    │  CFO         │  CTO         │
    │  Legal       │  R&D VP      │
    │  Procurement │  Exec Sponsor│ High
    ├──────────────┼──────────────┤ Interest
    │  Other VPs   │  Dev Teams   │
    │  HR          │  Tool Vendors│
    │  Comms       │  Pilot Team  │
    └──────────────┴──────────────┘
      MONITOR      │ KEEP INFORMED
                   |
               Low Power

**Quadrant Strategies:**

**Manage Closely (High Power, High Interest):**
- Weekly 1:1 updates
- Include in key decisions
- Address concerns immediately
- Co-create solutions
- Example: CTO, R&D VP, Executive Sponsor

**Keep Satisfied (High Power, Low Interest):**
- Monthly executive summaries
- Escalate only major issues
- Focus on business outcomes
- Respect their time
- Example: CFO, other C-suite

**Keep Informed (Low Power, High Interest):**
- Regular team communications
- Involve in planning
- Quick response to questions
- Community building
- Example: Dev teams, pilot team members

**Monitor (Low Power, Low Interest):**
- General updates only
- Available if needed
- No active engagement
- Example: Adjacent teams, observers
```

### Stakeholder Register

**Template:**
```markdown
## Stakeholder Register

| Name | Role | Power | Interest | Position | Strategy | Owner |
|------|------|-------|----------|----------|----------|-------|
| Jane Smith | CTO | High | High | Champion | Manage closely | PM |
| John Doe | CFO | High | Medium | Skeptical | Keep satisfied | PM |
| Sarah Lee | R&D VP | High | High | Supportive | Manage closely | PM |
| Mike Chen | Security | Medium | High | Concerned | Partner & address | Tech Lead |
| Dev Team A | Users | Low | High | Curious | Keep informed | Change Mgr |
| Vendor PM | External | Medium | Medium | Resistant | Professional | Vendor Mgr |

**Position Definitions:**
- Champion: Active supporter, promoter
- Supportive: Positive, willing to help
- Neutral: No strong opinion
- Skeptical: Needs convincing
- Resistant: Opposed, potential blocker
- Concerned: Worried about specific aspects
```

## Engagement Strategies

### By Stakeholder Type

**Champions (Leverage for Support):**
```markdown
**Engagement Strategy:**
- Involve early and deeply
- Ask for advice and input
- Use as spokespersons
- Amplify their support
- Recognize publicly

**Communication:**
- Frequency: Weekly or more
- Method: 1:1 meetings, co-working sessions
- Content: Deep dives, strategic discussions
- Ask: "How can I support you in supporting this?"

**Example Actions:**
- Co-present to executives
- Quote in communications
- Invite to planning sessions
- Request testimonials
```

**Skeptics (Address Concerns):**
```markdown
**Engagement Strategy:**
- Listen to concerns
- Provide data and evidence
- Address risks proactively
- Offer pilot participation
- Build confidence gradually

**Communication:**
- Frequency: Biweekly
- Method: 1:1 meetings, data-driven updates
- Content: ROI data, risk mitigation, proof points
- Ask: "What would it take to gain your support?"

**Example Actions:**
- Private briefings with Q&A
- Share similar company successes
- Offer to pilot with their requirements
- Regular checkpoint meetings
```

**Resisters (Understand and Mitigate):**
```markdown
**Engagement Strategy:**
- Understand root cause of resistance
- Address legitimate concerns
- Find areas of agreement
- Isolate if necessary (escalate to sponsor)
- Document interactions

**Communication:**
- Frequency: Monthly or as needed
- Method: Formal meetings, documented
- Content: Requirements, constraints, tradeoffs
- Ask: "What are your non-negotiables?"

**Example Actions:**
- Executive sponsor involvement
- Formal requirements gathering
- Compromise where possible
- Escalation path clear
```

### Communication Planning

**Communication Matrix:**
```markdown
| Audience | Purpose | Frequency | Method | Owner | Content |
|----------|---------|-----------|--------|-------|---------|
| Executive Sponsor | Decisions, escalations | Weekly | 1:1 meeting | PM | Status, risks, decisions needed |
| Steering Committee | Governance, approval | Monthly | Meeting | PM | Strategic updates, phase gates |
| Program Team | Coordination | Daily | Standup | PM | Tasks, blockers, coordination |
| Pilot Team | Guidance, support | 2x/week | Office hours | Change Mgr | Training, Q&A, feedback |
| All R&D | Awareness | Weekly | Email/Slack | PM | Progress, wins, upcoming |
| Executives | Visibility | Monthly | Email | PM | Executive summary |
| Vendor | Coordination | Weekly | Meeting | Vendor Mgr | Transition planning |
```

**Message Development Framework:**

**SCQA Structure (Situation-Complication-Question-Answer):**
```markdown
**Situation:** Current state or context
"We're currently spending $400K/year on offshore development vendors"

**Complication:** Problem or opportunity
"Costs are rising 10%/year and we're losing IP and flexibility"

**Question:** What the audience is wondering
"How can we reduce costs while maintaining quality?"

**Answer:** Your recommendation or update
"We're piloting AI-augmented FTEs to reduce costs 60% in 90 days"

**Apply to each communication based on audience priorities**
```

## Resistance Management

### Sources of Resistance

**Job Security Fears:**
- Concern: "AI will replace me"
- Reality: AI augments, transforms roles
- Response: Career development, upskilling, role evolution

**Change Fatigue:**
- Concern: "Another transformation initiative"
- Reality: This one has clear ROI and timeline
- Response: Acknowledge past, show differences, quick wins

**Loss of Control:**
- Concern: "This is being forced on me"
- Reality: Need to adapt to market changes
- Response: Involve in decisions, allow input, phased adoption

**Competency Anxiety:**
- Concern: "I don't know how to use AI"
- Reality: New skill, but learnable
- Response: Training, support, mentoring, practice time

**Quality Concerns:**
- Concern: "AI output isn't good enough"
- Reality: AI + human = better than either alone
- Response: Data, validation processes, pilot proof

**Vendor Relationship:**
- Concern: "We have good relationship with vendor"
- Reality: Business decision, not personal
- Response: Professional transition, maintain relationships

### Resistance Response Playbook

**Step 1: Listen and Validate**
```markdown
**Bad:** "Your concern is unfounded"
**Good:** "I hear your concern about [X]. That's important. Tell me more about that."

**Goal:** Understand root cause, show respect, build trust
**Time:** 70% listening, 30% talking
```

**Step 2: Acknowledge and Empathize**
```markdown
**Bad:** "Get over it"
**Good:** "I understand why you'd feel that way. Change is hard, especially when..."

**Goal:** Show empathy, build connection
**Avoid:** Dismissing, minimizing, arguing
```

**Step 3: Provide Context and Data**
```markdown
**Bad:** "Just trust us"
**Good:** "Here's why we're doing this... [business case]. Here's what we've seen... [data]."

**Goal:** Build understanding, address information gaps
**Include:** ROI, market trends, competitor actions, success stories
```

**Step 4: Address Specific Concerns**
```markdown
**Bad:** Generic talking points
**Good:** Direct response to their specific concern with concrete actions

Example:
Concern: "I'll lose my job"
Response: "No layoffs planned. In fact, we're investing $19K in training to upskill the team. Your role will evolve to higher-value architecture work. Here's the career path..."
```

**Step 5: Offer Involvement**
```markdown
**Bad:** "This is happening whether you like it or not"
**Good:** "Would you like to be part of the pilot? Your feedback would be valuable. What would make this work better for you?"

**Goal:** Create ownership, allow input
**Result:** Resister → Skeptic → Neutral → Supporter
```

### Difficult Conversations

**Preparation:**
- Know your facts and data
- Anticipate objections
- Prepare responses
- Identify desired outcome
- Plan for escalation if needed
- Choose right time and place

**During Conversation:**
- Start with alignment (what we agree on)
- Listen more than talk (70/30 rule)
- Stay calm and professional
- Acknowledge emotions (theirs and yours)
- Focus on interests, not positions
- Look for win-win solutions
- Document key points

**Follow-up:**
- Summarize in writing
- Address commitments made
- Check in later (don't abandon)
- Involve others if needed (sponsor, HR)
- Track progress on concerns

## Stakeholder Influence Tactics

### Persuasion Strategies

**Rational Persuasion (For Analytical Stakeholders):**
- Data, metrics, ROI models
- Benchmarks and case studies
- Pilot results and proof points
- Risk assessments
- Example: CFO, Finance, Analytics teams

**Consultation (For Involved Stakeholders):**
- Ask for input early
- Incorporate feedback
- Co-create solutions
- Share credit
- Example: R&D leadership, technical leads

**Inspirational Appeal (For Visionary Stakeholders):**
- Future vision and possibilities
- Competitive advantage
- Innovation and leadership
- Strategic alignment
- Example: CEO, CTO, product leaders

**Collaboration (For Partner Stakeholders):**
- Work together on challenges
- Joint problem solving
- Shared goals and metrics
- Mutual support
- Example: Security, compliance, IT

**Coalition Building (For Skeptical Stakeholders):**
- Build supporter network
- Leverage champions
- Social proof
- Peer influence
- Example: Resistant managers, skeptical teams

## Stakeholder Meeting Best Practices

### Pre-Meeting
- Define clear objective
- Send agenda 24+ hours ahead
- Include relevant materials
- Identify decisions needed
- Confirm attendees

### During Meeting
- Start and end on time
- Review objective and agenda
- Listen actively
- Take notes (or assign note-taker)
- Manage time
- Confirm decisions and actions
- Summarize next steps

### Post-Meeting
- Send notes within 24 hours
- Clarify action items (owner, due date)
- Follow up on commitments
- Thank participants
- Update stakeholder register

### Meeting Types

**1:1 Updates (30 min):**
- Status overview (5 min)
- Deep dive on area of interest (15 min)
- Q&A and feedback (5 min)
- Actions and next steps (5 min)

**Steering Committee (60 min):**
- Executive summary (5 min)
- Key metrics and status (10 min)
- Deep dive on topic (20 min)
- Decisions needed (15 min)
- Actions and wrap (10 min)

**Phase Gate Review (90 min):**
- Gate criteria review (20 min)
- Evidence presentation (30 min)
- Q&A and discussion (20 min)
- Decision (15 min)
- Next steps (5 min)

## Stakeholder Satisfaction

### Measuring Satisfaction

**Pulse Survey (Monthly):**
```markdown
## Stakeholder Satisfaction Survey

1. How satisfied are you with program communication?
   1 (Very Dissatisfied) - 5 (Very Satisfied)

2. How well are your concerns being addressed?
   1 (Not at all) - 5 (Very well)

3. How confident are you in program success?
   1 (Not confident) - 5 (Very confident)

4. What's going well?
   [Open text]

5. What needs improvement?
   [Open text]

**Target: Average ≥4.0/5.0**
```

**Feedback Channels:**
- Regular surveys (monthly)
- Office hours (open door)
- Anonymous feedback (suggestion box)
- Retrospectives (team)
- 1:1 meetings (individual)

## Common Stakeholder Management Pitfalls

### Pitfall 1: Ignoring Low-Power Stakeholders
**Problem:** Focusing only on executives, ignoring team members
**Why it fails:** Team resistance sinks programs despite executive support
**Solution:** Engage all levels, especially those doing the work

### Pitfall 2: One-Way Communication
**Problem:** Talking at stakeholders, not listening
**Why it fails:** Miss concerns, lose support, create resistance
**Solution:** 70% listening, 30% talking. Ask questions.

### Pitfall 3: Surprising Stakeholders
**Problem:** Springing major changes or issues without warning
**Why it fails:** Erodes trust, creates defensive reactions
**Solution:** No surprises. Communicate early and often.

### Pitfall 4: Treating All Stakeholders the Same
**Problem:** Same message, same frequency for everyone
**Why it fails:** Doesn't match needs, wastes time or under-informs
**Solution:** Tailor approach based on power-interest analysis

### Pitfall 5: Avoiding Difficult Stakeholders
**Problem:** Not engaging with resisters or skeptics
**Why it fails:** Problems fester, resistance grows, sabotage risk
**Solution:** Engage early, often, and directly

## Tools and Templates

**Stakeholder Tools:**
- Power-Interest Matrix (Excel, PowerPoint)
- Stakeholder Register (Excel, Google Sheets)
- Communication Plan (Excel, project mgmt tool)
- Meeting Tracker (Calendar, project mgmt tool)
- Satisfaction Surveys (SurveyMonkey, Google Forms, Typeform)

**Communication Tools:**
- Email for formal, documented communication
- Slack/Teams for quick, informal updates
- Video calls for complex discussions
- In-person for sensitive topics
- Presentations for formal briefings

## Success Metrics

**Engagement Metrics:**
- Stakeholder response rate: ≥90% to communications
- Meeting attendance: ≥90% required attendees
- Feedback participation: ≥60% survey completion
- Satisfaction score: ≥4.0/5.0 average

**Support Metrics:**
- Champion count: ≥5 active champions
- Resistance level: <10% active resisters
- Escalations: <5 per month to executive sponsor
- Approval speed: <48 hours for decisions

**Outcome Metrics:**
- Phase gate approvals: 100% passed
- Budget approval: Obtained on time
- Resource allocation: 100% of requested
- Program continuation: Zero cancellations due to stakeholder issues

This skill ensures stakeholder support is maintained throughout the program, preventing political derailment.
```