Framework
The ADKAR Model, Explained
ADKAR — Awareness, Desire, Knowledge, Ability, Reinforcement — describes the five things that have to happen, in order, for one person to actually change how they work. Developed by Prosci, it's an individual-level model: it doesn't tell you how to run a project, it tells you whether the people in it are actually adopting the change.
Why sequence matters
Each letter is a gate, not a checklist item. You can't build Knowledge in someone who hasn't developed Desire — the training just won't stick. You can't reinforce Ability that was never actually built. Most stalled change initiatives, on inspection, turn out to have skipped a stage rather than failed at all of them.
Awareness
Do they understand why this change is happening?
Not the project name or the go-live date — the actual business reason, stated plainly enough that someone could repeat it back accurately. Awareness fails silently: people nod in the town hall and still have no idea why.
If you skip it: Skip this and every later stage is built on sand — you can train someone thoroughly and they'll still resist, because they were never sold on the 'why.'
Desire
Do they personally want to engage and participate?
Awareness is intellectual; Desire is personal. It's the point where 'I understand why the company is doing this' becomes 'I'm willing to change how I work.' This is where job-security fears, past-change fatigue, and 'what's in it for me' live.
If you skip it: The stage most projects skip straight past, because it can't be mandated — only influenced. Leadership can require attendance at training; they can't require Desire.
Knowledge
Do they know how to change — the specifics, for their role?
Training, documentation, job aids. The trap is generic training that covers the system but not the specific new workflow a given role now has to follow.
If you skip it: Training delivered before Desire is built — people sit through it disengaged, retain little, and you pay for the training twice.
Ability
Can they actually do it — under real deadline pressure, not just in a sandbox?
Knowledge is knowing the steps; Ability is fluency. The gap between the two is usually measured in weeks of real practice, coaching, and making mistakes in a low-stakes way.
If you skip it: Assuming Knowledge equals Ability and pulling support the day training ends — right when people need it most.
Reinforcement
Is the new way being visibly recognized and sustained, or is the old way still quietly acceptable?
The most neglected stage. Without it, adoption decays: people drift back to the old process the moment attention moves to the next project.
If you skip it: Declaring victory at go-live and moving the project team to the next thing — with no mechanism to catch backsliding.
ADKAR in practice
On a real project, the deliverables map directly onto these stages: a Change Story builds Awareness and starts building Desire. A change impact analysis tells you where Ability gaps will be largest. Stakeholder communications — sequenced by audience and by ADKAR stage — are what actually move people through Awareness and Desire rather than jumping straight to Knowledge. Reinforcement is usually the thinnest part of most plans, and the one most worth fixing.
Rolling out an AI tool specifically? The stages above apply, but the failure modes are different — see Change Management for AI Tool Rollouts.
FAQ
Is ADKAR the same as Kotter's 8-step model?
No — they operate at different levels. Kotter's model is organizational: build a coalition, set a vision, remove obstacles, generate short-term wins. ADKAR is individual: it describes the sequence one person moves through to actually change their behavior. Many practitioners use both — Kotter (or a similar model) to plan the initiative, ADKAR to check whether any given person or group is actually adopting it.
How long does each ADKAR stage take?
There's no fixed duration — it depends on the size of the change and how much support people get. What matters more than timing is sequence: don't invest in Knowledge (training) for a group that hasn't cleared Desire, and don't declare success at Ability without a Reinforcement plan.
Who created the ADKAR model?
ADKAR was developed by Prosci, a change management research and training organization. It remains one of the most widely used individual-change models in the field, particularly in North America.
Every ainachi deliverable is grounded in ADKAR
Change Story, Impact Analysis, and stakeholder comms — sequenced to match the 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.