Framework comparison
ADKAR vs. Kotter
ADKAR and Kotter's 8-step model are the two frameworks change management practitioners cite most often — and they're frequently mistaken for competitors. They're not. They operate at different levels and answer different questions, which is why so many practitioners end up using both rather than choosing between them.
The short version
Kotter's model is organizational: an eight-step sequence for how leadership builds and sustains momentum behind a change initiative. ADKAR is individual: it describes the five things that have to happen, in order, for one person to actually change how they work. Kotter tells you how to lead the change; ADKAR tells you whether it's actually landing.
Kotter's 8 steps
Create a sense of urgency
Make the case for why standing still is riskier than changing — a real threat or opportunity, not manufactured panic.
Build a guiding coalition
Assemble a group with enough authority, credibility and reach across the organization to lead the change.
Form a strategic vision
Give the coalition a clear picture of the future state, simple enough to explain in a few sentences.
Enlist a volunteer army
Communicate the vision widely enough that people opt in rather than wait to be told what to do.
Enable action by removing barriers
Find and clear the structural obstacles — systems, processes, hierarchies — that block people who want to move.
Generate short-term wins
Deliver visible, unambiguous results early, before skeptics have time to consolidate opposition.
Sustain acceleration
Use the credibility from early wins to tackle bigger, harder changes rather than declaring victory too soon.
Institute change
Anchor the new behaviors in culture — norms, hiring, promotion — so they outlast the initiative that introduced them.
Side by side
| ADKAR | Kotter | |
|---|---|---|
| Origin | Prosci, a change management research and training organization | Dr. John Kotter, Harvard Business School — Leading Change (1996) |
| Level of focus | Individual — one person's path through change | Organizational — how the initiative itself is led and sequenced |
| Core question | Is this specific person or group actually adopting the change? | Is the organization building enough momentum to make the change stick? |
| Typical output | A readiness or gap assessment per stakeholder group | A leadership and communication sequence for the whole initiative |
| What it doesn't tell you | How to build a coalition, set a vision, or generate organizational momentum | Whether any specific person has actually built the ability to work the new way |
Using them together
In practice, they slot together cleanly: Kotter's early steps (urgency, coalition, vision) happen before the ADKAR clock starts for most people — you need a reason to change and a plan before anyone can build Awareness of it. From there, Kotter keeps sequencing the organizational moves — removing barriers, generating wins, sustaining acceleration — while ADKAR is the diagnostic you run on specific stakeholder groups to see who's stuck and why. A change impact analysis is useful regardless of which framework is structuring the initiative — it's the input both approaches need to know who's affected and how much.
FAQ
Is ADKAR better than Kotter's model?
Not a fair comparison — they're not competing for the same job. ADKAR is a diagnostic for individual change; Kotter's model is a playbook for leading organizational change. Most practitioners don't pick one over the other; they use each for what it's designed for.
Can you use ADKAR and Kotter's model together?
Yes, and it's a common pairing. Kotter's steps structure the initiative at the organizational level — building urgency, a coalition, a vision, and early wins. ADKAR runs underneath that, checking whether specific people and teams are actually moving through Awareness, Desire, Knowledge, Ability and Reinforcement as the initiative unfolds.
Does ainachi support Kotter's model?
ainachi's generated deliverables — Change Story, Impact Analysis, stakeholder communications — are grounded in ADKAR today, since it maps cleanly onto individual-level artifacts. The workflow isn't architecturally tied to one framework, and organizational-level, Kotter-style planning (coalition-building, vision, sequencing) is a direction we're open to as the product grows.
Structured, ADKAR-grounded deliverables — generated for you
ainachi turns a project brief into a Change Story, Impact Analysis, and stakeholder comms, sequenced to the ADKAR stage your audience is actually at.
No spam. We'll only use your email to contact you about the pilot, never share it, and remove it if you ask.