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... |
| Awareness |
"Do they know why this change is happening?" |
More communication on the why |
| Desire |
"Do they want to support this change?" |
Address WIIFM (what's in it for me), involve them |
| Knowledge |
"Do they know how to change?" |
Training, documentation, coaching |
| Ability |
"Can they actually perform the new behavior?" |
Practice, feedback loops, remove barriers |
| Reinforcement |
"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:**
- [...]
1---2name: change-management3description: When to activate: change management, organizational change, ADKAR, Kotter 8-step, resistance to change, change communication, adoption, transformation4---56# Change Management78## Kotter 8-Step Model910| Step | Action | Common failure |11|------|--------|----------------|12| 1. Create urgency | Show why change is essential now | "We'll be fine" complacency |13| 2. Form coalition | Build cross-functional leadership team | One person driving alone |14| 3. Create vision | Clear, inspiring picture of the future | Too vague or too complex |15| 4. Communicate vision | Repeat via every channel, consistently | One announcement then silence |16| 5. Remove obstacles | Clear structural and procedural barriers | Ignoring systemic blockers |17| 6. Create quick wins | Visible early wins to build momentum | Waiting too long for results |18| 7. Build on change | Accelerate after early wins | Declaring victory too soon |19| 8. Anchor in culture | Embed change in systems, processes, norms | Change fades when leader moves on |2021## ADKAR Model (Prosci)2223Use ADKAR to diagnose where individuals are in the change journey:2425| Stage | Question to ask | If stuck here... |26|-------|----------------|-----------------|27| **A**wareness | "Do they know why this change is happening?" | More communication on the why |28| **D**esire | "Do they want to support this change?" | Address WIIFM (what's in it for me), involve them |29| **K**nowledge | "Do they know how to change?" | Training, documentation, coaching |30| **A**bility | "Can they actually perform the new behavior?" | Practice, feedback loops, remove barriers |31| **R**einforcement | "Will the change stick?" | Recognition, accountability, measurement |3233**Diagnosis exercise:** Survey each impacted group (1-5 scale) on each ADKAR stage. Lowest stage = the constraint to fix first.3435## Stakeholder Resistance Mapping3637### Resistance Quadrants38```39 Impact on them40 Low High41High | Educate | Engage deeply |42 | (inform) | (co-create) |43Low | Monitor | Manage |44 | (light touch) | (address fears) |45Power46```4748### Resistance Root Causes and Responses49| Root cause | Signs | Response |50|------------|-------|----------|51| Loss of control | "No one asked us" | Involve earlier, give choices |52| Uncertainty | "What does this mean for my role?" | Clarity, specifics, timeline |53| Past failures | "We tried this before" | Acknowledge history, explain what's different |54| Workload concern | "We don't have capacity" | Show the plan, phase-in, support |55| Values conflict | "This isn't who we are" | Connect change to values they hold |56| Lack of trust in leadership | Silence, passive resistance | Demonstrate credibility via small commitments |5758## Change Communication Plan Template5960```61## [Initiative Name] Communication Plan6263### Audiences64| Audience | Size | Key concern | Primary channel | Owner |65|----------|------|-------------|----------------|-------|66| All employees | N | Job security | All-hands | CEO |67| Managers | N | Team impact | Manager briefing | CHRO |68| Affected teams | N | Process change | Team meeting | Dept head |69| External (customers) | N | Service continuity | Email | CCO |7071### Communication Cadence72| Phase | Date | Message | Channel | Owner |73|-------|------|---------|---------|-------|74| Pre-announce | [date] | "Something is coming" hint | Town hall | CEO |75| Announce | [date] | Full announcement | All-hands + email | CEO |76| 30 days | [date] | Progress update + FAQ | Manager cascade | Leadership |77| 60 days | [date] | Early wins + learnings | Newsletter | Program mgr |78| 90 days | [date] | Assessment + next phase | All-hands | CEO |7980### Key Messages811. Why: [Business rationale — one sentence]822. What: [What is changing — specific]833. What's not changing: [Stability anchors]844. Timeline: [Milestones]855. How to get help: [Resource, contact]86```8788## Change Champion Network8990### Role of Champions91- Early adopters who influence peers92- Translate change from corporate → team language93- Surface ground-level resistance back to program team94- Demonstrate new behaviors publicly9596### Selection Criteria97- Informal influence (not just formal authority)98- Respected by peers for credibility99- Open to the change (not necessarily enthusiastic)100- Representative of impacted groups101102### Champion Activities103| Activity | Frequency | Purpose |104|----------|-----------|---------|105| Champion briefing | Weekly (during rollout) | Early info, talking points |106| Feedback loop | Bi-weekly | Surface ground-level concerns |107| Recognition | Monthly | Sustain engagement |108| Success story sharing | As they occur | Build momentum |109110## Adoption Measurement111112### Leading Indicators (before behavior change)113- Awareness survey scores (ADKAR A/D stages)114- Training completion rate115- Champion network activation116117### Lagging Indicators (after behavior change)118- % using new process/tool (system data)119- Error rates on new vs old process120- Productivity recovery curve (expected dip, then recovery)121- Employee sentiment on the change (monthly pulse)122123### Adoption Curve Tracking124```125Month 1: Target 20% adoption (innovators + early adopters)126Month 3: Target 50% adoption (early majority)127Month 6: Target 80% adoption (late majority)128Month 12: Target 95% adoption (laggards accommodated or managed out)129```130131## Change Saturation Assessment132133Too many simultaneous changes causes initiative fatigue.134135### Saturation Risk Factors136- More than 3 significant changes active simultaneously for one group137- No recovery period between major initiatives138- Change recipients didn't choose this change139- Managers are also change recipients (double burden)140141### Change Inventory Matrix142| Initiative | Impacted groups | Start date | End date | Saturation risk |143|------------|----------------|------------|----------|----------------|144| [Name] | [Teams] | [Date] | [Date] | High/Med/Low |145146**Rule of thumb:** If a team has >2 high-effort changes active, deprioritize or sequence.147148## Change Curve (Kübler-Ross Adapted)149150```151Performance152 | _______________153 | / \____154 | / \____155 | ___/ \___________156 | /157 |/158 +-----------------------------------------> Time159 160 Shock → Denial → Frustration → Depression → Experiment → Decision → Integration161```162163**Manager action by stage:**164- Shock/Denial: Communicate facts, create safety to question165- Frustration/Depression: Acknowledge the difficulty; don't minimize166- Experiment: Celebrate attempts, tolerate mistakes167- Integration: Reinforce, recognize, embed in processes168169## Change Post-Mortem170171Run 90 days after rollout completion:172173```174## Change Post-Mortem: [Initiative Name]175176**What we set out to do:** [Goal]177**Adoption achieved:** [% vs target]178**Timeline:** [Planned vs actual]179180**What worked:**181- [Champion network was effective]182- [...]183184**What didn't work:**185- [Communications were too infrequent]186- [...]187188**What we'd do differently:**189- [...]190191**Lessons to carry forward:**192- [...]193```
Mattakushi432