AgentAlley
Submit

Change Management Playbook

Framework for rolling out organizational changes without chaos.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/change-management.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/c-level-advisor/skills/change-management#main ~/.claude/skills/change-management

For one project only, change the path to .claude/skills/change-management.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Change Management Playbook

Show the full text254 lines
change-management/SKILL.md254 lines · 11.2 KB
Outline
RawView on GitHub
namedescriptionlicensemetadata
change-managementFramework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or when user mentions change management, change rollout, managing resistance, org change, reorg, or pivot communication.MIT version: 1.0.0 author: Alireza Rezvani category: c-level domain: change-management updated: 2026-03-05 frameworks: change-playbook

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. Original version is for enterprises. This is the startup-speed adaptation.

A — Awareness

What it is: 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 is the problem we're solving? (Be honest. If it's "we need to cut costs," say that.)
  • Why now? What would happen if we didn't change?
  • Who made this decision and how?

Startup shortcut: A 5-minute video from the CEO or decision-maker explaining the "why" in plain language beats a formal change announcement document every time.

D — Desire

What it is: 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:

  • "What's in it for me?" — answer this for each stakeholder group, honestly
  • Involving people in the "how" even if the "what" is decided
  • Addressing fears directly: "Some people are worried this means their role is changing. Here's the truth: [honest answer]"

What destroys desire:

  • Pretending the change is better for everyone than it is
  • Ignoring the legitimate losses people will experience
  • Making announcements without any consultation

Startup shortcut: Run a short "concerns and questions" session within 48 hours of announcement. Not to reverse the decision — to address the fears and show you're listening.

K — Knowledge

What it is: People know HOW to operate in the new world — the specific skills, behaviors, and processes.

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

What people need:

  • Step-by-step documentation of new processes
  • Training or practice sessions before go-live
  • Clear answers to "what do I do when [common scenario]?"
  • Who to ask when they're stuck

Types of knowledge transfer:

Method Best for When
Live training Skill-based changes, complex tools Before go-live
Documentation Process changes, reference material Always
Video walkthroughs Tool migrations Available 24/7, self-paced
Shadowing / peer learning Behavior changes Weeks 2–4 after launch
Office hours Any change with many edge cases First 4–6 weeks
A — Ability

What it is: People have the time, tools, and support to actually do things differently.

The mistake: "We've trained everyone" ≠ "everyone can now do it." Training is knowledge. Ability is practice.

What creates ability:

  • Time to practice before being evaluated
  • A safe environment to make mistakes (no public shaming for early struggles)
  • Reduced load during transition (if you're asking people to learn new skills, don't simultaneously pile on new work)
  • Access to help (a Slack channel, a point person, documentation)

Signs of ability gap:

  • People revert to old behavior under pressure
  • Workarounds emerge (people invent their own way around the new system)
  • Training scores are high but actual behavior hasn't changed
R — Reinforcement

What it is: The change sticks. The new behavior becomes the default.

The mistake: Declaring victory at go-live. Changes fail because they're never reinforced.

What creates reinforcement:

  • Visible measurement (are we tracking adoption?)
  • Recognition of early adopters ("Sarah fully migrated to the new workflow in week 2 — ask her how")
  • Leader modeling (if the CEO uses the old way, everyone will)
  • Removing the old option (when possible — eliminate the path of least resistance)
  • Consequences for non-adoption (stated clearly, applied consistently)

Adoption vs. compliance:

  • Compliance: People do it when watched, revert when not
  • Adoption: People do it because they believe it's better

Only reinforcement creates adoption. Compliance is the result of enforcement. Aim for adoption.

Change Types and ADKAR Application

Process Change (new tools, new workflows)

Timeline: 4–8 weeks for full adoption Hardest phase: Ability (people know what to do but haven't built the habit) Critical reinforcement: Remove or deprecate the old tool/process

Communication sequence:

  1. Week -2: Announce the why + go-live date
  2. Week -1: Training sessions available
  3. Week 0 (go-live): Launch + point person available
  4. Week 2: Adoption check-in (who's using it? Who isn't?)
  5. Week 4: Feedback collection + public wins
  6. Week 8: Old system deprecated
Org Change (reorg, new leader, team splits/merges)

Timeline: 3–6 months for full stabilization Hardest phase: Desire (people fear for their roles and relationships) Critical reinforcement: Consistent behavior from new leadership

Communication sequence:

  1. Day 0: Announce the change with the "why" — in person or synchronous video
  2. Day 1: 1:1s with most affected team members by their manager
  3. Week 1: FAQ published with honest answers to the 10 most common concerns
  4. Week 2–4: New structure is operating (don't delay implementation)
  5. Month 2: First retrospective — what's working, what needs adjustment
  6. Month 3–6: Regular check-ins on team health and morale

What to say when a leader is leaving or being replaced: Be honest about what you can share. Never: "We can't share the reasons." Always: either a truthful explanation or "we're not able to share the specifics, but I can tell you [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 the pivot is happening

Communication sequence:

  1. Internal first, always. Employees should never hear about a pivot from a press release.
  2. All-hands with full context: what changed in the market, what you're doing, what it means for teams
  3. Each team leader runs a "what does this mean for us?" conversation with their team
  4. Resource reallocation announced within 2 weeks (if the money doesn't move, people won't believe the pivot)
  5. First milestone of the new direction 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 (behavior doesn't change just because values were announced) Critical reinforcement: Visible decisions that reflect the new values

Communication sequence:

  1. Build with input: involve a representative sample of the company in defining the change
  2. Announce with story: "Here's what we observed, here's what we're changing and why"
  3. Behavior anchors: for each culture change, state the specific behavior in observable terms
  4. Leader behavior: leadership team must visibly model the new behavior first
  5. Performance integration: new expected behaviors appear in reviews within one cycle
  6. Celebrate the right behaviors: when someone exemplifies the new culture, name it publicly

Resistance Patterns

Resistance is information, not defiance. Diagnose before responding.

Resistance pattern What it signals Response
"This won't work" Awareness gap or credibility gap Explain the evidence base for the change
"Why now?" Awareness gap Explain urgency — what happens if we don't change
"I wasn't consulted" Desire gap Acknowledge the gap; involve them in the "how" now
"I don't have time for this" Ability gap Reduce their load or push the timeline
"We tried this before" Trust gap Acknowledge what's different this time. Be specific.
Silent non-compliance Could be any gap 1:1 conversation to diagnose

The worst response to resistance: Dismissing it. "Some people are resistant to change" as if resistance is a personality flaw rather than a signal.

Change Fatigue

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

Signals
  • Eye-rolls during change announcements ("here we go again")
  • Low attendance at change-related sessions
  • Fast compliance on paper, slow adoption in practice
  • "Last month we were doing X, now we're doing Y" comments
Prevention
  • Finish what you start. Don't announce a new change while the last one is still being absorbed.
  • Space changes. One significant change at a time. Give 2–3 months of stability between major changes.
  • Announce what's NOT changing. People in change-fatigue need to know what's stable.
  • Show results. Publish what the previous change achieved before launching the next.
When you're already in change fatigue
  • Pause non-critical changes
  • Run a "change inventory": how many changes are in progress simultaneously?
  • Prioritize ruthlessly: which changes are essential now? Which can wait?
  • Communicate stability: "Here's what is NOT changing this quarter"

Key Questions for Change Management

  • "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 we measure 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 on Friday afternoon (people stew over the weekend)
  • "This is final, questions are not welcome" framing
  • No published FAQ or way to ask questions safely
  • 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 = success

Detailed References

  • references/change-playbook.md — ADKAR deep dive, resistance counter-strategies, communication templates, change fatigue management
1---
2name: "change-management"
3description: "Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or when user mentions change management, change rollout, managing resistance, org change, reorg, or pivot communication."
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: c-level
9 domain: change-management
10 updated: 2026-03-05
11 frameworks: change-playbook
12---
13 
14# Change Management Playbook
15 
16Most changes fail at implementation, not design. The ADKAR model tells you why and how to fix it.
17 
18## Keywords
19change management, ADKAR, organizational change, reorg, process change, tool migration, strategy pivot, change resistance, change fatigue, change communication, stakeholder management, adoption, compliance, change rollout, transition
20 
21## Core Model: ADKAR Adapted for Startups
22 
23ADKAR is a change management model by Prosci. Original version is for enterprises. This is the startup-speed adaptation.
24 
25### A — Awareness
26 
27**What it is:** People understand WHY the change is happening — the business reason, not just the announcement.
28 
29**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."
30 
31**What people need to hear:**
32- What is the problem we're solving? (Be honest. If it's "we need to cut costs," say that.)
33- Why now? What would happen if we didn't change?
34- Who made this decision and how?
35 
36**Startup shortcut:** A 5-minute video from the CEO or decision-maker explaining the "why" in plain language beats a formal change announcement document every time.
37 
38---
39 
40### D — Desire
41 
42**What it is:** People want to make the change happen — or at least don't actively resist it.
43 
44**The mistake:** Assuming communication creates desire. Awareness ≠ desire. People can understand a change and still hate it.
45 
46**What creates desire:**
47- "What's in it for me?" — answer this for each stakeholder group, honestly
48- Involving people in the "how" even if the "what" is decided
49- Addressing fears directly: "Some people are worried this means their role is changing. Here's the truth: [honest answer]"
50 
51**What destroys desire:**
52- Pretending the change is better for everyone than it is
53- Ignoring the legitimate losses people will experience
54- Making announcements without any consultation
55 
56**Startup shortcut:** Run a short "concerns and questions" session within 48 hours of announcement. Not to reverse the decision — to address the fears and show you're listening.
57 
58---
59 
60### K — Knowledge
61 
62**What it is:** People know HOW to operate in the new world — the specific skills, behaviors, and processes.
63 
64**The mistake:** Announcing the change and assuming people will figure it out.
65 
66**What people need:**
67- Step-by-step documentation of new processes
68- Training or practice sessions before go-live
69- Clear answers to "what do I do when [common scenario]?"
70- Who to ask when they're stuck
71 
72**Types of knowledge transfer:**
73| Method | Best for | When |
74|--------|---------|------|
75| Live training | Skill-based changes, complex tools | Before go-live |
76| Documentation | Process changes, reference material | Always |
77| Video walkthroughs | Tool migrations | Available 24/7, self-paced |
78| Shadowing / peer learning | Behavior changes | Weeks 2–4 after launch |
79| Office hours | Any change with many edge cases | First 4–6 weeks |
80 
81---
82 
83### A — Ability
84 
85**What it is:** People have the time, tools, and support to actually do things differently.
86 
87**The mistake:** "We've trained everyone" ≠ "everyone can now do it." Training is knowledge. Ability is practice.
88 
89**What creates ability:**
90- Time to practice before being evaluated
91- A safe environment to make mistakes (no public shaming for early struggles)
92- Reduced load during transition (if you're asking people to learn new skills, don't simultaneously pile on new work)
93- Access to help (a Slack channel, a point person, documentation)
94 
95**Signs of ability gap:**
96- People revert to old behavior under pressure
97- Workarounds emerge (people invent their own way around the new system)
98- Training scores are high but actual behavior hasn't changed
99 
100---
101 
102### R — Reinforcement
103 
104**What it is:** The change sticks. The new behavior becomes the default.
105 
106**The mistake:** Declaring victory at go-live. Changes fail because they're never reinforced.
107 
108**What creates reinforcement:**
109- Visible measurement (are we tracking adoption?)
110- Recognition of early adopters ("Sarah fully migrated to the new workflow in week 2 — ask her how")
111- Leader modeling (if the CEO uses the old way, everyone will)
112- Removing the old option (when possible — eliminate the path of least resistance)
113- Consequences for non-adoption (stated clearly, applied consistently)
114 
115**Adoption vs. compliance:**
116- **Compliance:** People do it when watched, revert when not
117- **Adoption:** People do it because they believe it's better
118 
119Only reinforcement creates adoption. Compliance is the result of enforcement. Aim for adoption.
120 
121---
122 
123## Change Types and ADKAR Application
124 
125### Process Change (new tools, new workflows)
126 
127**Timeline:** 4–8 weeks for full adoption
128**Hardest phase:** Ability (people know what to do but haven't built the habit)
129**Critical reinforcement:** Remove or deprecate the old tool/process
130 
131**Communication sequence:**
1321. Week -2: Announce the why + go-live date
1332. Week -1: Training sessions available
1343. Week 0 (go-live): Launch + point person available
1354. Week 2: Adoption check-in (who's using it? Who isn't?)
1365. Week 4: Feedback collection + public wins
1376. Week 8: Old system deprecated
138 
139---
140 
141### Org Change (reorg, new leader, team splits/merges)
142 
143**Timeline:** 3–6 months for full stabilization
144**Hardest phase:** Desire (people fear for their roles and relationships)
145**Critical reinforcement:** Consistent behavior from new leadership
146 
147**Communication sequence:**
1481. Day 0: Announce the change with the "why" — in person or synchronous video
1492. Day 1: 1:1s with most affected team members by their manager
1503. Week 1: FAQ published with honest answers to the 10 most common concerns
1514. Week 2–4: New structure is operating (don't delay implementation)
1525. Month 2: First retrospective — what's working, what needs adjustment
1536. Month 3–6: Regular check-ins on team health and morale
154 
155**What to say when a leader is leaving or being replaced:**
156Be honest about what you can share. Never: "We can't share the reasons." Always: either a truthful explanation or "we're not able to share the specifics, but I can tell you [what this means for you]."
157 
158---
159 
160### Strategy Pivot (new direction, killed products)
161 
162**Timeline:** 3–12 months for full alignment
163**Hardest phase:** Awareness (people don't believe the pivot is real)
164**Critical reinforcement:** Resource reallocation that visibly proves the pivot is happening
165 
166**Communication sequence:**
1671. Internal first, always. Employees should never hear about a pivot from a press release.
1682. All-hands with full context: what changed in the market, what you're doing, what it means for teams
1693. Each team leader runs a "what does this mean for us?" conversation with their team
1704. Resource reallocation announced within 2 weeks (if the money doesn't move, people won't believe the pivot)
1715. First milestone of the new direction celebrated publicly
172 
173**What kills pivots:** Announcing a new direction while still funding the old one at the same level.
174 
175---
176 
177### Culture Change (values refresh, behavior expectations)
178 
179**Timeline:** 12–24 months for genuine behavior change
180**Hardest phase:** Reinforcement (behavior doesn't change just because values were announced)
181**Critical reinforcement:** Visible decisions that reflect the new values
182 
183**Communication sequence:**
1841. Build with input: involve a representative sample of the company in defining the change
1852. Announce with story: "Here's what we observed, here's what we're changing and why"
1863. Behavior anchors: for each culture change, state the specific behavior in observable terms
1874. Leader behavior: leadership team must visibly model the new behavior first
1885. Performance integration: new expected behaviors appear in reviews within one cycle
1896. Celebrate the right behaviors: when someone exemplifies the new culture, name it publicly
190 
191---
192 
193## Resistance Patterns
194 
195Resistance is information, not defiance. Diagnose before responding.
196 
197| Resistance pattern | What it signals | Response |
198|-------------------|-----------------|---------|
199| "This won't work" | Awareness gap or credibility gap | Explain the evidence base for the change |
200| "Why now?" | Awareness gap | Explain urgency — what happens if we don't change |
201| "I wasn't consulted" | Desire gap | Acknowledge the gap; involve them in the "how" now |
202| "I don't have time for this" | Ability gap | Reduce their load or push the timeline |
203| "We tried this before" | Trust gap | Acknowledge what's different this time. Be specific. |
204| Silent non-compliance | Could be any gap | 1:1 conversation to diagnose |
205 
206**The worst response to resistance:** Dismissing it. "Some people are resistant to change" as if resistance is a personality flaw rather than a signal.
207 
208---
209 
210## Change Fatigue
211 
212When organizations change too fast, people stop believing any change will stick.
213 
214### Signals
215- Eye-rolls during change announcements ("here we go again")
216- Low attendance at change-related sessions
217- Fast compliance on paper, slow adoption in practice
218- "Last month we were doing X, now we're doing Y" comments
219 
220### Prevention
221- **Finish what you start.** Don't announce a new change while the last one is still being absorbed.
222- **Space changes.** One significant change at a time. Give 2–3 months of stability between major changes.
223- **Announce what's NOT changing.** People in change-fatigue need to know what's stable.
224- **Show results.** Publish what the previous change achieved before launching the next.
225 
226### When you're already in change fatigue
227- Pause non-critical changes
228- Run a "change inventory": how many changes are in progress simultaneously?
229- Prioritize ruthlessly: which changes are essential now? Which can wait?
230- Communicate stability: "Here's what is NOT changing this quarter"
231 
232---
233 
234## Key Questions for Change Management
235 
236- "Who are the most skeptical people about this change? Have we talked to them directly?"
237- "Do people understand why we're doing this, or just what we're doing?"
238- "Have we given people time to practice before we measure performance on the new way?"
239- "Is the old way still available? If so, people will use it."
240- "Are leaders modeling the new behavior themselves?"
241- "How many changes are we running simultaneously right now?"
242 
243## Red Flags
244 
245- Change announced on Friday afternoon (people stew over the weekend)
246- "This is final, questions are not welcome" framing
247- No published FAQ or way to ask questions safely
248- Old system/process still running 6 weeks after "go-live"
249- Leaders exempted from the change they're asking everyone else to make
250- No measurement of adoption — assuming go-live = success
251 
252## Detailed References
253- `references/change-playbook.md` — ADKAR deep dive, resistance counter-strategies, communication templates, change fatigue management
254 

Discussion

Alternatives

Also in Roadmap & prioritiesSee all 277 in Product →
🏛️ Tax Strategist AgentExpert tax strategist specializing in tax optimization, multi-jurisdictional compliance, transfer pricing, and strategic tax planning. Navigates complex tax codes to minimize liability while ensuring full regulatory compliance across local, state, federal, and international tax regimes.Business & ops · MIT📈 FP&A Analyst AgentExpert Financial Planning & Analysis (FP&A) analyst specializing in budgeting, variance analysis, financial planning, rolling forecasts, and strategic decision support. Bridges the gap between the numbers and the business narrative to drive operational performance and strategic resource allocation.Business & ops · MIT📊 Financial Analyst AgentExpert financial analyst specializing in financial modeling, forecasting, scenario analysis, and data-driven decision support. Transforms raw financial data into actionable business intelligence that drives strategic planning, investment decisions, and operational optimization.Business & ops · MITCareer changer translatorTranslate skills from one industry to another, identify transferable skillsBusiness & ops · MIT

Browse more free Claude skills or everything in Product.