change-management

name	change-management
description	Framework for rolling out organizational changes without chaos, using ADKAR adapted for startups. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, or managing change resistance.
license	MIT + Commons Clause
metadata	{"version":"2.0.0","author":"borghei","category":"c-level","domain":"change-management","updated":"2026-03-09T00:00:00.000Z","frameworks":["adkar-startup","change-communication","resistance-management","change-fatigue","change-playbooks","adoption-measurement"],"triggers":["change management","ADKAR","organizational change","reorg","restructure","process change","tool migration","strategy pivot","change resistance","change fatigue","change communication","stakeholder management","adoption","compliance","change rollout","transition","new process","announce change","manage resistance"]}

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

---

Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• The change type (process, org/reorg, strategy pivot, or culture) — selects the playbook, timeline, and which ADKAR phase is hardest
• What is changing and the honest business WHY — the WHY anchors every communication; without it the rollout reads as arbitrary and breeds resistance
• Who is affected and how (directly affected vs. broader org) — drives communication sequencing and the order in which audiences hear it
• How many other changes are already active — if 3+ changes are running and under-absorbed, the plan must address change fatigue before adding more

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

---

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
Awareness	People understand WHY the change is happening	"Nobody told me why"
Desire	People want to participate (or at least don't resist)	"I understand but I don't agree"
Knowledge	People know HOW to do things the new way	"I want to but I don't know how"
Ability	People have time, tools, and support to change	"I know how but I can't do it yet"
Reinforcement	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
Process	Heads-up to leads	All-hands email	FAQ published	Adoption check	Old way removed
Org	1:1s with affected	Synchronous meeting	FAQ + manager 1:1s	Retro	Health check
Strategy	Leadership alignment	All-hands with Q&A	Team-level "what does this mean"	Resource proof	First milestone
Culture	Input gathering	Story-based announcement	Behavior anchors	Reviews reflect it	Ongoing

---

Change Fatigue

Fatigue Detection

Signal	Severity	Response
Eye-rolls during announcements	Early	Acknowledge the pace, show results of previous changes
Low attendance at change sessions	Moderate	Make attendance optional but results visible
Fast paper compliance, slow real adoption	Significant	Pause non-critical changes
"Here we go again" comments	Significant	Audit change inventory, communicate stability
Complete disengagement	Critical	Freeze changes, rebuild trust

Fatigue Prevention Rules

Rule	Implementation
Finish what you start	Do not launch new change while previous is absorbing
One major change at a time	Space 2-3 months between significant changes
Announce stability	Explicitly state what is NOT changing
Show results	Publish what previous change achieved before launching next
Change budget	Treat organizational attention as a finite resource

Change Inventory

Before launching any new change, inventory all active changes:

Change	Phase	Start Date	Absorption %	Can It Pause?
New CRM rollout	Ability	2 weeks ago	60%	No
Engineering reorg	Desire	1 month ago	40%	Yes
Values refresh	Reinforcement	3 months ago	75%	No

Rule: If 3+ changes are active and < 70% absorbed, do not add another.

---

Playbook 1: Process Change

Timeline: 4-8 weeks | Hardest Phase: Ability

Week	Activity	Owner
-2	Announce WHY + go-live date	Change sponsor
-1	Training sessions available	Change team
0	Go-live + support person available	Change team
2	Adoption check: who is using it, who is not	Change team
4	Feedback collection + public wins	Change sponsor
8	Old system deprecated	IT + Change team

---

Playbook 2: Org Change

Timeline: 3-6 months | Hardest Phase: Desire

Timing	Activity	Owner
Day 0	Announce with WHY -- synchronous, in-person preferred	CEO/leader
Day 1	1:1s with most affected by their manager	Managers
Week 1	FAQ published with honest answers	HR + Change team
Week 2-4	New structure operating (do not delay)	All leaders
Month 2	First retrospective	Change team
Month 3-6	Regular health check-ins	HR

What to say about a leader departure: Be honest about what you can share. Never say "we can't share the reasons" without offering what you CAN say about what it means for the team.

---

Playbook 3: Strategy Pivot

Timeline: 3-12 months | Hardest Phase: Awareness

Timing	Activity	Owner
Pre-announcement	Leadership alignment (everyone must be on same page)	CEO
Day 0	Internal announcement first (employees BEFORE press)	CEO
Week 1	Team-level "what does this mean for us" conversations	Team leads
Week 2	Resource reallocation announced	CFO + COO
Month 1	First milestone of new direction visible	Relevant leader
Ongoing	Regular updates on new direction progress	CEO

What kills pivots: Announcing a new direction while still funding the old one at the same level. Move the resources or the pivot is not real.

---

Playbook 4: Culture Change

Timeline: 12-24 months | Hardest Phase: Reinforcement

Phase	Activity	Timeline
Input	Involve representative sample in defining the change	Month 1-2
Announce	Story-based announcement with observed behaviors	Month 2
Anchor	Define observable behaviors for each culture change	Month 2-3
Model	Leadership team visibly models new behavior first	Month 3+
Integrate	New behaviors appear in performance reviews	Next review cycle
Celebrate	Publicly recognize new behavior when observed	Ongoing

---

Adoption Measurement

Adoption vs. Compliance

Dimension	Compliance	Adoption
Behavior	Does it when watched	Does it because it is better
Duration	Reverts when enforcement relaxes	Sustained without enforcement
Attitude	Reluctant	Willing or enthusiastic
Source	External pressure	Internal belief

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

Adoption Metrics

Metric	How to Measure	Target
Usage rate	% of people actively using new process/tool	> 80% by week 8
Reversion rate	% reverting to old way	< 10%
Satisfaction	Survey: "Is the new way better?"	> 60% agree
Speed	Time to complete task old way vs. new way	New way faster by week 4
Support requests	Volume of help requests	Declining week over week

---

Red Flags

• Change announced on Friday afternoon -- people stew over the weekend
• "This is final, questions are not welcome" framing -- creates underground resistance
• No published FAQ or way to ask questions safely -- concerns go unaddressed
• Old system still running 6 weeks after go-live -- change is not real
• Leaders exempt from the change they are asking everyone to make -- destroys credibility
• No measurement of adoption -- assuming go-live equals success
• Multiple major changes running simultaneously -- change fatigue guaranteed
• No post-change retrospective -- missing the feedback loop
• Change announced without a named owner -- nobody is accountable for success

---

Integration with C-Suite

When...	Change Management Works With...	To...
Process change	COO (coo-advisor)	Design new process before announcing
Org restructure	CHRO + CEO	People impact assessment, communication
Strategy pivot	CEO (ceo-advisor)	Alignment and narrative
Culture change	Culture Architect (culture-architect)	Values-to-behaviors translation
Tool migration	CTO (cto-advisor)	Technical rollout plan
Operating system change	Company OS (company-os)	New rhythms and cadences
Alignment after change	Strategic Alignment (strategic-alignment)	Verify cascade post-change

---

Output Artifacts

Request	Deliverable
"Plan a change rollout"	ADKAR-based change plan with timeline and owners
"We're doing a reorg"	Org change playbook with communication plan
"Manage resistance to [change]"	Resistance diagnosis + targeted responses
"Are we in change fatigue?"	Change inventory + fatigue assessment + recommendations
"Communication plan for [change]"	Sequenced communication with templates
"Measure adoption of [change]"	Adoption metrics dashboard with targets

---

Tool Reference

change_readiness_assessor.py

Assesses organizational readiness using ADKAR model, identifies resistance patterns, measures change fatigue, and generates intervention plans.

# Run with demo data
python scripts/change_readiness_assessor.py

# Specify change type
python scripts/change_readiness_assessor.py --type org

# From JSON assessment data
python scripts/change_readiness_assessor.py --input assessment.json

# JSON output
python scripts/change_readiness_assessor.py --json

adoption_tracker.py

Tracks usage rates, reversion rates, satisfaction, and support requests to distinguish real adoption from surface compliance.

# Run with demo data
python scripts/adoption_tracker.py

# From JSON with weekly data
python scripts/adoption_tracker.py --input adoption_data.json

# JSON output
python scripts/adoption_tracker.py --json

communication_planner.py

Generates audience-sequenced communication plans with templates, channel recommendations, and timing.

# Generate for process change
python scripts/communication_planner.py --type process --name "New CRM Rollout" --date 2026-04-15

# Generate for org change
python scripts/communication_planner.py --type org --name "Engineering Restructure"

# From JSON
python scripts/communication_planner.py --input comm_plan.json

# JSON output
python scripts/communication_planner.py --type strategy --json

---

Troubleshooting

Problem	Likely Cause	Fix
Usage rate high but satisfaction low	Compliance without adoption -- people use it because forced to	Investigate satisfaction drivers; don't rely on enforcement alone; improve the tool/process itself
Adoption plateaus at 60-70%	Remaining 30% have unaddressed ADKAR gaps (often Ability)	Segment non-adopters; run 1:1 diagnostics; provide targeted support
Change reverts within weeks of go-live	Reinforcement phase skipped; old system still accessible	Remove old system access; measure and recognize new behavior; embed in performance reviews
Leaders exempt themselves from the change	"Do as I say, not as I do" pattern	Leaders must go first and visibly. No exceptions. This is the #1 credibility destroyer
Multiple changes running and all struggling	Change fatigue -- organizational attention exhausted	Inventory active changes; pause non-critical ones; space major changes 2-3 months apart
Communication plan exists but concerns persist	Communication was broadcast-only with no feedback channel	Add Q&A sessions, named contact person, anonymous feedback channel

---

Success Criteria

• ADKAR readiness score above 70/100 before go-live (measured via change_readiness_assessor.py)
• Adoption rate exceeds 80% within 8 weeks of go-live (usage, not just compliance)
• Reversion rate below 10% by week 8 (measured by system usage data)
• Satisfaction survey shows 60%+ agreement that "the new way is better" by week 8
• Support requests decline week-over-week after week 2 (ability phase resolving)
• No change announced on Friday afternoon (measured by communication log timestamps)
• Post-change retrospective conducted within 90 days with documented lessons learned

---

Scope & Limitations

In Scope: ADKAR-based readiness assessment, resistance diagnosis and response, change fatigue measurement, communication planning and sequencing, adoption tracking, playbooks for process/org/strategy/culture changes.

Out of Scope: Specific tool migration execution (CRM, ERP configuration), legal compliance for workforce reductions, union negotiation, employment law, individual coaching or therapy.

Limitations: ADKAR scores are based on assessment inputs -- they reflect perception, not objective measurement. Adoption tracker requires manual data collection for most metrics. Communication planner provides templates but cannot account for company-specific political dynamics. Change fatigue assessment is directional; actual organizational capacity varies by company culture.

---

Integration Points

Skill	Integration
coo-advisor	Process change design before announcing; operational readiness
chro-advisor	People impact assessment; communication sequencing for reorgs
ceo-advisor	Strategy pivot narrative alignment; CEO as primary communicator
culture-architect	Culture change playbook; values-to-behaviors translation
company-os	New OS rollout follows ADKAR model; meeting rhythm changes
chief-of-staff	Routes change management questions; orchestrates cross-functional alignment
strategic-alignment	Verifies goal cascade post-change; validates new direction is reflected in OKRs