change-management

---
name: change-management
description: Use when announcing a reorg, tool migration, strategy pivot, or leadership change. Apply ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement), resistance patterns, and change fatigue.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# Change Management Playbook

Most changes fail at implementation, not design. The ADKAR model tells you why and how to fix it.

## 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

## Core Model: ADKAR Adapted for Startups

ADKAR is a change management model by Prosci, built for enterprises. Below is the startup-speed adaptation.

### A — Awareness
People understand WHY the change is happening — the business reason, not just the announcement.

**The mistake:** Communicating the WHAT before the WHY. "We're moving to a new CRM" before "here's why our current process is killing us."

**What people need to hear:** What problem are we solving (be honest — if it's "cut costs," say that); why now and what happens if we don't change; who decided and how.

**Startup shortcut:** A 5-minute video from the CEO explaining the "why" in plain language beats a formal change document.

### D — Desire
People want to make the change happen — or at least don't actively resist it.

**The mistake:** Assuming communication creates desire. Awareness ≠ desire; people can understand a change and still hate it.

**What creates desire:** answering "what's in it for me" honestly per stakeholder group; involving people in the "how" even when the "what" is decided; naming fears directly instead of pretending the change is better for everyone than it is.

**What destroys desire:** overselling, ignoring legitimate losses, announcing without consultation.

**Startup shortcut:** Run a short "concerns and questions" session within 48 hours of announcement — not to reverse the decision, but to show you're listening.

### K — Knowledge
People know HOW to operate in the new world — specific skills, behaviors, and processes.

**The mistake:** Announcing the change and assuming people will figure it out.

**What people need:** step-by-step documentation, training/practice before go-live, clear answers for common scenarios, a named person to ask when stuck.

**Knowledge-transfer methods and when to use them:**
| Method | Best for | When |
|--------|---------|------|
| Live training | Skill-based changes, complex tools | Before go-live |
| Documentation | Process changes, reference material | Always |
| Video walkthroughs | Tool migrations | Self-paced, always available |
| Shadowing / peer learning | Behavior changes | Weeks 2–4 after launch |
| Office hours | Changes with many edge cases | First 4–6 weeks |

### A — Ability
People have the time, tools, and support to actually do things differently. Training is knowledge; ability is practice — "we've trained everyone" ≠ "everyone can now do it."

**What creates ability:** practice time before evaluation; a safe environment to fail without public shaming; reduced workload during transition; accessible help (Slack channel, point person, docs).

**Signs of an ability gap:** people revert to old behavior under pressure; workarounds emerge; training scores are high but behavior hasn't changed.

### R — Reinforcement
The change sticks and becomes the default. Changes fail because they're never reinforced past go-live.

**What creates reinforcement:** visible adoption measurement; recognizing early adopters publicly; leaders modeling the new behavior (if the CEO uses the old way, everyone will); removing the old option when possible; stated, consistently-applied consequences for non-adoption.

**Adoption vs. compliance:** compliance is doing it when watched, reverting when not. Adoption is doing it because people believe it's better. Only reinforcement creates adoption — aim for adoption, not compliance.

## Change Types and ADKAR Application

### Process Change (new tools, new workflows)
**Timeline:** 4–8 weeks to full adoption. **Hardest phase:** Ability. **Critical reinforcement:** deprecate the old tool/process.

Sequence: Week -2 announce why + go-live date → Week -1 training available → Week 0 launch + point person → Week 2 adoption check-in → Week 4 feedback + public wins → Week 8 old system deprecated.

### Org Change (reorg, new leader, team splits/merges)
**Timeline:** 3–6 months to stabilize. **Hardest phase:** Desire (people fear for roles/relationships). **Critical reinforcement:** consistent behavior from new leadership.

Sequence: Day 0 announce with the "why" synchronously → Day 1 manager 1:1s with affected staff → Week 1 FAQ answering the 10 most common concerns honestly → Weeks 2–4 new structure operating (don't delay) → Month 2 first retrospective → Months 3–6 regular team-health check-ins.

**On a leader leaving/being replaced:** never say "we can't share the reasons" — say either the truthful explanation or "we can't share specifics, but here's what this means for you."

### Strategy Pivot (new direction, killed products)
**Timeline:** 3–12 months for full alignment. **Hardest phase:** Awareness (people don't believe the pivot is real). **Critical reinforcement:** resource reallocation that visibly proves it.

Sequence: internal first, always (employees should never hear about a pivot from a press release) → all-hands with full market/decision context → each team lead runs a "what does this mean for us" conversation → resource reallocation announced within 2 weeks (if money doesn't move, people won't believe it) → first milestone celebrated publicly.

**What kills pivots:** announcing a new direction while still funding the old one at the same level.

### Culture Change (values refresh, behavior expectations)
**Timeline:** 12–24 months for genuine behavior change. **Hardest phase:** Reinforcement. **Critical reinforcement:** visible decisions reflecting the new values.

Sequence: build with input from a representative sample of the company → announce with the observed story and the change → state each behavior anchor in observable terms → leadership visibly models it first → new behaviors enter performance reviews within one cycle → name and celebrate exemplars publicly.

## Resistance Patterns
Resistance is information, not defiance — diagnose before responding.

| Resistance pattern | What it signals | Response |
|-------------------|-----------------|---------|
| "This won't work" | Awareness or credibility gap | Explain the evidence base |
| "Why now?" | Awareness gap | Explain urgency |
| "I wasn't consulted" | Desire gap | Acknowledge, involve them in the "how" now |
| "I don't have time for this" | Ability gap | Reduce load or push the timeline |
| "We tried this before" | Trust gap | Name what's specifically different this time |
| Silent non-compliance | Any gap | 1:1 to diagnose |

**The worst response to resistance:** dismissing it as a personality flaw rather than a signal.

## Change Fatigue
When organizations change too fast, people stop believing any change will stick.

**Signals:** eye-rolls at announcements ("here we go again"); low attendance at change sessions; fast paper compliance, slow practical adoption; "last month X, now Y" comments.

**Prevention:** finish what you start — don't launch a new change while the last is still being absorbed; space changes 2–3 months apart; announce what's NOT changing; publish results of the previous change before launching the next.

**If already in change fatigue:** pause non-critical changes; run a change inventory (how many are in flight simultaneously); prioritize ruthlessly; communicate stability explicitly.

## Key Questions
- Who are the most skeptical people about this change? Have we talked to them directly?
- Do people understand why we're doing this, or just what we're doing?
- Have we given people time to practice before measuring performance on the new way?
- Is the old way still available? If so, people will use it.
- Are leaders modeling the new behavior themselves?
- How many changes are we running simultaneously right now?

## Red Flags
- Change announced Friday afternoon (people stew over the weekend)
- "This is final, questions are not welcome" framing
- No published FAQ or safe way to ask questions
- Old system/process still running 6 weeks after "go-live"
- Leaders exempted from the change they're asking everyone else to make
- No measurement of adoption — assuming go-live equals success