change-management

# Change Management Playbook

Most changes fail at implementation, not design. This skill provides the complete framework for rolling out organizational changes -- from process tweaks to full strategic pivots -- with minimal disruption and maximum adoption.

## Keywords

change management, ADKAR, organizational change, reorg, process change, tool migration, strategy pivot, change resistance, change fatigue, change communication, stakeholder management, adoption, compliance, change rollout, transition

---

## Change Type Selection

```
START: Change is needed
  |
  v
[What type of change?]
  |
  +-- Process Change (new tools, workflows)
  |     Timeline: 4-8 weeks
  |     Hardest phase: Ability
  |     See: Process Change Playbook
  |
  +-- Org Change (reorg, new leader, team restructure)
  |     Timeline: 3-6 months
  |     Hardest phase: Desire
  |     See: Org Change Playbook
  |
  +-- Strategy Pivot (new direction, killed products)
  |     Timeline: 3-12 months
  |     Hardest phase: Awareness
  |     See: Strategy Pivot Playbook
  |
  +-- Culture Change (values refresh, behavior expectations)
        Timeline: 12-24 months
        Hardest phase: Reinforcement
        See: Culture Change Playbook
```

---

## Core Model: ADKAR (Startup-Adapted)

### Overview

| Phase | What It Is | Failure Symptom |
|-------|-----------|----------------|
| **A**wareness | People understand WHY the change is happening | "Nobody told me why" |
| **D**esire | People want to participate (or at least don't resist) | "I understand but I don't agree" |
| **K**nowledge | People know HOW to do things the new way | "I want to but I don't know how" |
| **A**bility | People have time, tools, and support to change | "I know how but I can't do it yet" |
| **R**einforcement | The change sticks as the new default | "We tried but went back to the old way" |

### ADKAR Diagnostic

When a change is struggling, identify which phase is broken:

| Symptom | Broken Phase | Fix |
|---------|-------------|-----|
| "Why are we doing this?" | Awareness | Re-communicate the WHY with data |
| "This is a bad idea" | Desire | Address concerns, involve in HOW |
| "I don't know how to do this" | Knowledge | Training, documentation, office hours |
| "I keep reverting to old habits" | Ability | Practice time, reduce workload, support |
| "We started but stopped" | Reinforcement | Measurement, recognition, remove old way |

### ADKAR Implementation Timeline

| Week | Phase | Key Activities |
|------|-------|---------------|
| -4 | Awareness prep | Identify stakeholders, draft communication |
| -2 | Awareness launch | CEO/leader video explaining WHY |
| -1 | Desire building | Concerns session, address fears, involve in HOW |
| 0 | Knowledge + Go-live | Training, documentation, launch |
| 1-2 | Ability support | Office hours, help desk, reduced load |
| 3-4 | Ability + early Reinforcement | Adoption check, public wins, feedback |
| 6-8 | Full Reinforcement | Old way deprecated, adoption measured, recognized |

---

## Resistance Patterns and Responses

### Resistance Diagnostic Matrix

| Pattern | What They Say | What It Signals | Response |
|---------|-------------|-----------------|---------|
| Vocal opposition | "This won't work" | Awareness or credibility gap | Present evidence, acknowledge concern |
| Timing challenge | "Why now?" | Awareness gap | Explain urgency and cost of delay |
| Process complaint | "I wasn't consulted" | Desire gap | Acknowledge, involve in the HOW now |
| Capacity excuse | "I don't have time" | Ability gap | Reduce load or extend timeline |
| Historical reference | "We tried this before" | Trust gap | Name what is different this time |
| Silent non-compliance | [No verbal pushback, just doesn't change] | Could be any phase | 1:1 conversation to diagnose |
| Malicious compliance | [Does it technically but undermines] | Deep desire gap | Direct conversation about real concern |

### Resistance Response Decision Tree

```
START: Resistance detected
  |
  v
[Is it vocal or silent?]
  |
  +-- VOCAL --> Good. They care enough to push back.
  |              |
  |              v
  |            [Is the concern valid?]
  |              |
  |              +-- YES --> Modify the change. Resistance is information.
  |              +-- NO  --> Address with data and empathy. Do not dismiss.
  |
  +-- SILENT --> Dangerous. Could be any ADKAR phase.
                 |
                 v
               [1:1 conversation with specific questions]
                 "What concerns you about this change?"
                 "What would need to be true for this to work for you?"
                 "What support would help?"
```

### The Worst Response to Resistance

"Some people are just resistant to change."

This treats resistance as a personality flaw rather than a signal. Every resistance pattern is information about which ADKAR phase is broken. Diagnose before responding.

---

## Change Communication Framework

### Communication Sequencing

| Audience | Order | Channel | Content |
|----------|-------|---------|---------|
| Leadership team | 1st | In-person/video meeting | Full context + their role in rollout |
| Directly affected employees | 2nd | Manager 1:1 or small group | Personal impact + support available |
| All employees | 3rd | All-hands or written + Q&A | WHY + WHAT + timeline + FAQ |
| External stakeholders | 4th (if applicable) | Appropriate channel | Need-to-know only |

### Communication Template (CEO/Leader Announcement)

```
Structure:
  1. What is changing (1-2 sentences, direct)
  2. Why it is changing (the business reason -- honest)
  3. What this means for you (practical impact)
  4. What is NOT changing (stability anchor)
  5. Timeline (specific dates)
  6. How to ask questions (channel, person, office hours)
  7. What happens next (first concrete step)
```

### Communication Cadence by Change Type

| Change Type | Pre-announcement | Launch Day | Week 1 | Month 1 | Month 3 |
|-------------|-----------------|--