Change Management

What This Skill Does

• The Change Management Playbook helps organizations successfully implement changes using the ADKAR model adapted for startups.
• It focuses on addressing awareness, desire, knowledge, ability, and reinforcement to overcome resistance and ensure adoption.
• This skill is useful for leaders managing organizational changes such as reorgs, process changes, or tool migrations.

When to Use

• Managing organizational restructuring effectively.
• Implementing new processes or workflows.
• Migrating to new software or tools.
• Pivoting business strategy or direction.
• Addressing change resistance from employees.
• Improving change adoption and compliance.

Key Features

• Adapts the ADKAR model for startup environments.
• Emphasizes the importance of communicating the 'why'.
• Focuses on creating desire for change among stakeholders.
• Provides strategies for addressing employee concerns.
• Offers startup shortcuts for effective communication.
• Highlights the need for reinforcement to sustain change.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedChange 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:

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.
• 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: Week -2: Announce the why + go-live date Week -1: Training sessions available Week 0 (go-live): Launch + point person available Week 2: Adoption check-in (who's using it? Who isn't?) Week 4: Feedback collection + public wins 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: Day 0: Announce the change with the "why" — in person or synchronous video Day 1: 1:1s with most affected team members by their manager Week 1: FAQ published with honest answers to the 10 most common concerns Week 2–4: New structure is operating (don't delay implementation) Month 2: First retrospective — what's working, what needs adjustment 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.

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:

• Internal first, always.
• Employees should never hear about a pivot from a press release. All-hands with full context: what changed in the market, what you're doing, what it means for teams Each team leader runs a "what does this mean for us?" conversation with their team Resource reallocation announced within 2 weeks (if the money doesn't move, people won't believe the pivot) 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