# Change Management

> When to activate: change management, organizational change, ADKAR, Kotter 8-step, resistance to change, change communication, adoption, transformation

- Skill: `mattakushi432/change-management` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mattakushi432/change-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mattakushi432/change-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Mattakushi432 (https://skillmd.com/u/mattakushi432)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mattakushi432/change-management

---


# Change Management

## Kotter 8-Step Model

| Step | Action | Common failure |
|------|--------|----------------|
| 1. Create urgency | Show why change is essential now | "We'll be fine" complacency |
| 2. Form coalition | Build cross-functional leadership team | One person driving alone |
| 3. Create vision | Clear, inspiring picture of the future | Too vague or too complex |
| 4. Communicate vision | Repeat via every channel, consistently | One announcement then silence |
| 5. Remove obstacles | Clear structural and procedural barriers | Ignoring systemic blockers |
| 6. Create quick wins | Visible early wins to build momentum | Waiting too long for results |
| 7. Build on change | Accelerate after early wins | Declaring victory too soon |
| 8. Anchor in culture | Embed change in systems, processes, norms | Change fades when leader moves on |

## ADKAR Model (Prosci)

Use ADKAR to diagnose where individuals are in the change journey:

| Stage | Question to ask | If stuck here... |
|-------|----------------|-----------------|
| **A**wareness | "Do they know why this change is happening?" | More communication on the why |
| **D**esire | "Do they want to support this change?" | Address WIIFM (what's in it for me), involve them |
| **K**nowledge | "Do they know how to change?" | Training, documentation, coaching |
| **A**bility | "Can they actually perform the new behavior?" | Practice, feedback loops, remove barriers |
| **R**einforcement | "Will the change stick?" | Recognition, accountability, measurement |

**Diagnosis exercise:** Survey each impacted group (1-5 scale) on each ADKAR stage. Lowest stage = the constraint to fix first.

## Stakeholder Resistance Mapping

### Resistance Quadrants
```
        Impact on them
        Low             High
High  | Educate        | Engage deeply   |
      | (inform)       | (co-create)     |
Low   | Monitor        | Manage          |
      | (light touch)  | (address fears) |
Power
```

### Resistance Root Causes and Responses
| Root cause | Signs | Response |
|------------|-------|----------|
| Loss of control | "No one asked us" | Involve earlier, give choices |
| Uncertainty | "What does this mean for my role?" | Clarity, specifics, timeline |
| Past failures | "We tried this before" | Acknowledge history, explain what's different |
| Workload concern | "We don't have capacity" | Show the plan, phase-in, support |
| Values conflict | "This isn't who we are" | Connect change to values they hold |
| Lack of trust in leadership | Silence, passive resistance | Demonstrate credibility via small commitments |

## Change Communication Plan Template

```
## [Initiative Name] Communication Plan

### Audiences
| Audience | Size | Key concern | Primary channel | Owner |
|----------|------|-------------|----------------|-------|
| All employees | N | Job security | All-hands | CEO |
| Managers | N | Team impact | Manager briefing | CHRO |
| Affected teams | N | Process change | Team meeting | Dept head |
| External (customers) | N | Service continuity | Email | CCO |

### Communication Cadence
| Phase | Date | Message | Channel | Owner |
|-------|------|---------|---------|-------|
| Pre-announce | [date] | "Something is coming" hint | Town hall | CEO |
| Announce | [date] | Full announcement | All-hands + email | CEO |
| 30 days | [date] | Progress update + FAQ | Manager cascade | Leadership |
| 60 days | [date] | Early wins + learnings | Newsletter | Program mgr |
| 90 days | [date] | Assessment + next phase | All-hands | CEO |

### Key Messages
1. Why: [Business rationale — one sentence]
2. What: [What is changing — specific]
3. What's not changing: [Stability anchors]
4. Timeline: [Milestones]
5. How to get help: [Resource, contact]
```

## Change Champion Network

### Role of Champions
- Early adopters who influence peers
- Translate change from corporate → team language
- Surface ground-level resistance back to program team
- Demonstrate new behaviors publicly

### Selection Criteria
- Informal influence (not just formal authority)
- Respected by peers for credibility
- Open to the change (not necessarily enthusiastic)
- Representative of impacted groups

### Champion Activities
| Activity | Frequency | Purpose |
|----------|-----------|---------|
| Champion briefing | Weekly (during rollout) | Early info, talking points |
| Feedback loop | Bi-weekly | Surface ground-level concerns |
| Recognition | Monthly | Sustain engagement |
| Success story sharing | As they occur | Build momentum |

## Adoption Measurement

### Leading Indicators (before behavior change)
- Awareness survey scores (ADKAR A/D stages)
- Training completion rate
- Champion network activation

### Lagging Indicators (after behavior change)
- % using new process/tool (system data)
- Error rates on new vs old process
- Productivity recovery curve (expected dip, then recovery)
- Employee sentiment on the change (monthly pulse)

### Adoption Curve Tracking
```
Month 1: Target 20% adoption (innovators + early adopters)
Month 3: Target 50% adoption (early majority)
Month 6: Target 80% adoption (late majority)
Month 12: Target 95% adoption (laggards accommodated or managed out)
```

## Change Saturation Assessment

Too many simultaneous changes causes initiative fatigue.

### Saturation Risk Factors
- More than 3 significant changes active simultaneously for one group
- No recovery period between major initiatives
- Change recipients didn't choose this change
- Managers are also change recipients (double burden)

### Change Inventory Matrix
| Initiative | Impacted groups | Start date | End date | Saturation risk |
|------------|----------------|------------|----------|----------------|
| [Name] | [Teams] | [Date] | [Date] | High/Med/Low |

**Rule of thumb:** If a team has >2 high-effort changes active, deprioritize or sequence.

## Change Curve (Kübler-Ross Adapted)

```
Performance
    |        _______________
    |       /               \____
    |      /                     \____
    |  ___/                           \___________
    | /
    |/
    +-----------------------------------------> Time
    
    Shock → Denial → Frustration → Depression → Experiment → Decision → Integration
```

**Manager action by stage:**
- Shock/Denial: Communicate facts, create safety to question
- Frustration/Depression: Acknowledge the difficulty; don't minimize
- Experiment: Celebrate attempts, tolerate mistakes
- Integration: Reinforce, recognize, embed in processes

## Change Post-Mortem

Run 90 days after rollout completion:

```
## Change Post-Mortem: [Initiative Name]

**What we set out to do:** [Goal]
**Adoption achieved:** [% vs target]
**Timeline:** [Planned vs actual]

**What worked:**
- [Champion network was effective]
- [...]

**What didn't work:**
- [Communications were too infrequent]
- [...]

**What we'd do differently:**
- [...]

**Lessons to carry forward:**
- [...]
```