ADKAR.

ADKAR is a change model that says change never happens to a business. It happens to one person at a time, and each of those people needs five things in order: Awareness of why, Desire to take part, Knowledge of how, Ability to do it under real conditions, and Reinforcement so it survives. Somebody stalls at the first one they are missing, and everything you do above that point is wasted effort.

The model was developed by Jeff Hiatt and is used through Prosci. Its value to an owner is not motivational, it is diagnostic: it turns "they are resisting it" into a specific, fixable answer for each named person.

What does ADKAR actually describe?

You announced the change at a Monday meeting. You explained it well. Three months later about a third of the team are doing it, a third are doing a version of it, and a third have quietly carried on as before. You are irritated, and the irritation is aimed at the whole group.

ADKAR says the group is the wrong unit of analysis. Five people can be stuck at five different points, and the fix for each is completely different: a ten-minute conversation, an honest negotiation, half an hour of training, a change to the workload, or a manager who actually opens the report. Handled as a group, four of those five get the wrong treatment.

The five elements, strictly in order

Awareness — do they know why?

They understand the reason in terms of the business rather than the announcement. Not "we are moving to job costing" but "we do not know which jobs make money, and two of last year's biggest ones lost us cash." Awareness delivered as a policy statement rarely lands; awareness delivered as a number usually does.

Desire — do they want to?

They personally want to take part, or at least accept it. This is the one element you cannot instruct, because desire is a private answer to a private question about what the change costs them: status, comfort, an easier Friday, the thing they were good at. No amount of explaining moves it. A straight conversation sometimes does.

Knowledge — do they know how?

Which buttons, in which order, and what good looks like. This is the element businesses over-invest in, for the simple reason that training is the easiest thing to buy. If somebody was on holiday for the training day, this is a half-hour fix and the cheapest item on the list.

Ability — can they do it on a busy Thursday?

Knowing how and being able to are not the same. Ability is doing it at half past four on a busy Thursday, not in a quiet room with somebody sitting next to them. If the new way takes an extra fifteen minutes a day because a job code has to be looked up every time, that is a design problem wearing a compliance problem's clothes.

Reinforcement — does it survive week four?

It sticks because somebody looks at the output, uses it, and notices when it does not appear. Adoption at week six is not adoption. The honest test is week twelve, after the first genuinely busy fortnight, and what carries it through is somebody senior visibly making a decision from the output.

Why owners get this wrong

Two reasons, and both are understandable. The first is that the team gets treated as one thing. "They are resisting" is not a diagnosis, it is a mood, and it leads to a firmer email — which addresses none of the five elements for any of the people.

The second is that Knowledge is the only element with an obvious product attached. You can buy training. You cannot buy Desire, and no amount of training fixes an Ability problem that is really a capacity problem. So the money goes where the invoice exists rather than where the barrier is.

What it looks like in practice

Take an eleven-person agency introducing time recording so it can finally see job profitability. The example is illustrative, but the sequence is the ordinary one. Announced in March. Software bought. Training day in April with everyone present. By the end of June, four of the eleven are recording time reliably, three are reconstructing it in bulk on a Friday afternoon from memory, and four have effectively stopped.

The instinct is another training session and a firmer email. Run ADKAR name by name instead and the picture separates out. Two people never understood why — they were on client work during the March meeting and picked it up second hand as "the boss wants timesheets." That is Awareness, and it is a ten-minute conversation with last year's two loss-making jobs on the table.

Three believe it is surveillance. They think the real purpose is to find out who is slow, which is exactly why the Friday reconstruction exists. That is Desire, and no training touches it. It needs the owner to say plainly what the data will and will not be used for, then to behave consistently for a couple of months, because they will be watching.

One was on holiday for the training day and has been guessing since. That is Knowledge: half an hour. Two more can do it, but it costs them roughly fifteen minutes a day they do not have because of the job code lookup. That is Ability, and the fix is a shorter code list and a default job per person, not encouragement.

And the rest drifted because in fourteen weeks nobody mentioned the output. No report, no review, no decision visibly taken as a result. That is Reinforcement, and it is the owner's failure rather than the team's. Five barriers, five different fixes, one costing half an hour and one requiring the owner to change their own behaviour.

How to use it this week

1. Pick the change that is currently half-landed. Everyone has one — the system, the process, the meeting discipline that nearly took.
2. Write the names down the side of a page and A D K A R across the top. Tick or cross each box for each person, from evidence rather than impression.
3. Find the first cross on each row. That, and only that, is the barrier for that person. Ignore everything to the right of it.
4. Deal with the Awareness gaps individually. Ten minutes each, with the actual business reason and a number attached. Not in a group.
5. Ask the Desire cases the direct question. "What is the downside of this for you?" Then listen without defending. You will usually get an answer worth having, and occasionally one you should act on.
6. Fix one Ability blocker properly. Time the new way against the old one. If it costs fifteen minutes a day more, you have a design problem.
7. Put Reinforcement in your own diary. A fortnightly slot where you open the output and make one visible decision from it. Change dies where nobody looks.

The mistake most owners make

Treating Reinforcement as optional because the change appears to have landed. The other is going straight to Desire and calling it attitude. If two people are not doing it, the useful question is not "why are they being difficult" but "which of the five is missing for them?" Sometimes the answer genuinely is Desire, and then you have a real conversation with real consequences. Far more often it is Awareness or Ability, and you were about to have entirely the wrong conversation.

Questions to ask yourself

• Out of 10, how confident are you that every person affected by your last change could explain, in their own words, why it was happening?
• Think of the last thing that failed to stick. Which of the five was actually missing, and how long did you spend fixing a different one?
• What are you currently calling resistance that is really a capacity problem you created?
• When did you last make a visible decision using the output of a change you introduced? If the answer is never, why would anyone keep feeding it?

This is the diagnostic underneath Leadership Coaching, and it sits directly beneath the guide on leading your team through change. Two related models are worth reading next: Ask, Don't Tell, because the Desire conversation is asked rather than announced, and Backbone and Heart, for the conversation you have when the answer really is Desire.