ADKAR Is Not a Checklist. It Is a Diagnostic.

There is a version of change management that treats ADKAR as a sequence of boxes to check.

Awareness communication: sent. Desire survey: administered. Knowledge training: scheduled. Adoption metrics: tracked. Reinforcement plan: filed. Change complete.

Anyone who has worked inside a real transformation knows that version does not work. Not because the framework is wrong. It is not. But because it is being used as a production process when it is actually a thinking tool.

The difference matters. Enormously.

ADKAR describes the internal states a person needs to move through in order to change: Awareness of the need to change, Desire to support it, Knowledge of how to change, Ability to demonstrate the new behavior, and Reinforcement to sustain it. The sequence is logical and, in my experience, accurate. People really do get stuck at these five points. They really do fail to adopt changes for identifiable, diagnosable reasons.

But the framework only helps you if you use it to diagnose, not to prescribe.

The question is not: have we delivered an awareness communication? The question is: do people actually understand why this change is happening, and do they believe the reason is legitimate? The question is not: have we administered a desire survey? The question is: what are the real barriers to people wanting this change, and are we willing to look at them honestly?

Those are harder questions. They require curiosity rather than compliance. They require sitting with discomfort about what you might find.

The most common failure mode I have seen in change programs is not a lack of methodology. It is a lack of diagnostic honesty. Organizations run through the ADKAR motions and then express genuine surprise when adoption stalls at go-live. If you look back at the awareness phase, the communications were technically sent — they just did not say anything employees could connect to their actual situation. Or the desire survey results showed low enthusiasm, which the team noted in a risk log and moved past without actually doing anything about it.

The framework told them where the problem was. They just did not want to hear it.

This is where the real discipline of change work lives. Not in the templates or the toolkits, but in the willingness to stop and ask: what does this data actually mean, and what are we willing to do about it? That question gets uncomfortable fast. Low desire is often a signal that there is a legitimate grievance in the organization that leadership has not addressed. Low ability is often a signal that the training was insufficient, which means the timeline might need to change. These are not easy conclusions to bring to a sponsor.

But they are the conclusions that honest diagnostic work produces. And they are the conclusions that, if acted on, actually lead to adoption.

What makes this methodology enduring across industries, across decades, across wildly different types of change, is that it is fundamentally about people and not about projects. ADKAR does not describe a project plan. It describes a human experience. And human experiences do not follow Gantt charts.

The organizations that get the most out of the framework are the ones that use it to stay in genuine contact with the experience of people going through change. Not to manage them through a process, but to understand where they actually are and meet them there.

That is harder than checking boxes. It requires more than methodology.

It requires the willingness to be honest about what you find.

And in my experience, that willingness more than any framework or tool is what separates change programs that stick from ones that quietly fade after go-live, while everyone moves on to the next initiative and wonders what happened.