Jeff Hiatt's ADKAR model (Prosci) is an individual-level change model. Its premise: organizational change only happens when individuals change, so manage the change one person at a time, in sequence.

Evidence: Weak. Commercially developed, with essentially no independent validation. The sequential barrier logic is plausible and clinically useful, and the specific distinction between Knowledge and Ability is well supported by the training transfer literature, which finds repeatedly that classroom learning does not survive contact with real conditions without practice and environmental support. The five-element structure itself is unproven.

Use when: a defined change affects a defined population and you need to find where individuals are stuck.

Do not use when: the required change is unknown or emergent. ADKAR presumes a known target behavior.

The five elements, in order

  1. Awareness of the need for change. Do I know why?
  2. Desire to participate and support it. Do I want to?
  3. Knowledge of how to change. Do I know what to do?
  4. Ability to implement the required skills and behaviors. Can I do it in real conditions?
  5. Reinforcement to sustain the change. Does anything keep me doing it?

The diagnostic power: the barrier point

The sequence matters. Find the first element that is missing — that is the barrier point — and address it. Interventions aimed past the barrier point are wasted.

Barrier point Wrong intervention Right intervention
Awareness Training Communication of why, with evidence, from a trusted source
Desire More communication Address what the person loses; involve them; manage resistance individually
Knowledge Exhortation Training, documentation, job aids
Ability More training Practice, coaching, time, tooling, removing real obstacles
Reinforcement Declaring success Metrics, recognition, consequences, removing the old path

The most common mistake in every sector: training people who lack Desire. They attend, they pass, and nothing changes — because the barrier was at step 2.

The second most common: assuming Knowledge equals Ability. Knowing the technique is not being able to do it under pressure at 3 a.m. with an interruption.

Examples by audience

  • Health care: a new documentation standard. Nurses have Awareness and Knowledge; they lack Ability, because the workstation is two corridors away and the shift has no slack. No amount of training moves this; moving the workstation does.

  • Software: adopting a new testing practice. Engineers often have Knowledge and lack Desire, because the previous three mandated practices were abandoned. The barrier is credibility, not competence.

  • Executive: executives are usually strong on Awareness and Desire — they chose the change — and weak on Reinforcement, because reinforcement is boring and happens after attention has moved to the next initiative.

Using it operationally

  • Assess each element 1–5 per group, or per person for key individuals.
  • Score below 3 marks the barrier point; stop there and work it.
  • Reassess after each intervention; barrier points move.
  • Combine with an organization-level model. ADKAR tells you about people; it says nothing about structure, strategy, or systems.

Limitations

  • Practitioner-derived with limited independent validation. See evidence-based-practice.
  • Individual focus omits structural causes; a person can have all five elements and still fail inside a system that prevents the behavior.
  • Presumes the change is correct, and offers no mechanism for the possibility that resistance is information.

See also

Organizational Development — a comprehensive practitioner's guide to OD for health care professionals, software engineers, and senior executives. Every framework says what the evidence is, and where it is weak.

Source and contributions: github.com/organizational-development. Built with the Lily Design System™.