ADKAR — The Change Model for Individual Behavior

60-Second Summary

Prosci's ADKAR: Awareness, Desire, Knowledge, Ability, Reinforcement.
Change happens one person at a time — ADKAR diagnoses where each person is stuck.
Most failed change has plenty of A and K, almost no D or R.
Use as a manager's checklist when rolling out anything from new tools to new strategy.
Pairs perfectly with Kotter (org) or Lewin (system).

An HR team rolled out a new performance management system. Training completion: 98%. Adoption six months later: 22%. They built Awareness and Knowledge meticulously, never built Desire, and never put Reinforcement in place. ADKAR predicted exactly what happened. The training was perfect; the adoption was a different problem entirely.

Why it matters

Jeff Hiatt's Prosci ADKAR model is the most useful per-person change framework. Org-level models (Kotter, Lewin) assume people will move once the system is updated; ADKAR makes that movement debuggable at the individual level. Most stalled change has plenty of awareness and knowledge — and zero desire or reinforcement. The acronym lets you point to the missing letter rather than vaguely 'pushing harder'.

The other use: it's a manager's checklist. When rolling out anything — a new tool, a new policy, a new strategy — you can score each affected team on A, D, K, A, R, see the lowest letter, and invest there. It is the cheapest way to avoid the 'we trained everyone and nothing changed' failure mode.

5 letters

A · D · K · A · R

all required; the lowest is your bottleneck

D + R

the most-skipped

leaders default to A and K because they're easier

<25%

adoption

typical for rollouts that skip D and R

The 5 elements

ADKAR

1
A — Awareness
Why the change is needed. Often confused with announcement; people need to feel it.
2
D — Desire
Personal motivation to participate. Address WIIFM ('what's in it for me') honestly.
3
K — Knowledge
What and how. Training, docs, examples.
4
A — Ability
Practiced skill, with coaching and time to develop.
5
R — Reinforcement
Recognition, metrics, manager habits that prevent regression.

Where each team is stuck

Each letter has a different symptom — and a different fix.

Symptom	Bottleneck	Wrong fix	Right fix
'I didn't know we were doing this.'	Awareness	More mandates.	Re-launch with concrete reasons + data.
'I get it, I just don't care.'	Desire	More training.	Honest WIIFM conversation; tie to personal goals.
'I want to but don't know how.'	Knowledge	More mandates.	Docs, examples, walkthroughs.
'I know how but can't quite do it.'	Ability	More docs.	Coaching, practice reps, time to fail safely.
'I did it for a month, then stopped.'	Reinforcement	Re-train.	Manager check-ins, metrics, recognition.

ADKAR drop-off funnel

Awareness
everyone has heard
Desire
fewer actually want to
Knowledge
fewer know how
Ability
fewer can do it under pressure
Reinforcement
fewer keep doing it past month 3

Example

When Microsoft rolled out the growth mindset shift, each manager was given an ADKAR-style toolkit: scripts (A+K), why-this-matters-for-you conversations (D), 1:1 practice (Ability), and quarterly reviews on culture behaviors (R). The R is what made it stick where slogan-only rollouts fail. The same shift in companies that built only A and K decayed within two quarters.

Apply on Monday

For your current change, score each affected team on A, D, K, A, R (0-5).
Target investment at the lowest score, not your favourite letter.
Build R (reinforcement) into manager scorecards from day 1.
Don't move to K until D is honestly above 3.
Re-score every 6 weeks — bottlenecks shift.

Common mistakes

Pumping A and K and assuming D will follow (it won't).
Ignoring R — and watching adoption decay.
Treating ADKAR as a one-time exercise instead of an ongoing diagnostic.
Solving for the average — different teams stick at different letters.
Confusing 'I attended the training' with 'I have the ability'.
Reinforcing only at performance review — too slow.

Reflection prompts

On my biggest change right now, which letter is the bottleneck?
Where am I investing in A/K when D is the gap?
What R mechanism would I bet on to prevent regression?
Which team has a different bottleneck than the average — and am I treating them differently?

Takeaways

ADKAR is the per-person debug tool for change.
Most stalled change is a D or R problem dressed up as A or K.
Score per team — the bottleneck is rarely uniform.
Reinforcement is what separates adoption from theatre.

Visual summary

Awareness → Desire → Knowledge → Ability → Reinforcement. Score per team. Invest at the lowest letter. R is the difference between adoption and theatre.