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

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

ADKAR Diagnostic

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

ADKAR Implementation Timeline

Resistance Patterns and Responses

Resistance Diagnostic Matrix

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

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 Fatigue

Fatigue Detection

Fatigue Prevention Rules

Change Inventory

Before launching any new change, inventory all active changes:

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

Playbook 1: Process Change

Timeline: 4-8 weeks | Hardest Phase: Ability

Playbook 2: Org Change

Timeline: 3-6 months | Hardest Phase: Desire

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

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

Adoption Measurement

Adoption vs. Compliance

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

Adoption Metrics

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

Output Artifacts

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

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