The ADKAR Model for Change Management

The ADKAR Model is a Prosci methodology for managing organizational change. It's applied during large-scale projects like ERP implementations, digital transformations, and mergers across industries like healthcare and finance.
WHY IT EXISTS Most organizational change efforts fail not because the new system or process is wrong, but because the people who have to use it never actually change their behavior. Traditional change management focused on the project plan, the training deck, the go-live date. ADKAR exists to shift that focus to the individual, because an organization only changes when enough of its people move through change one at a time.
THE MENTAL MODEL Think of ADKAR as five locked doors in a row, and a person has to unlock each one in order to reach the next. You cannot build ability, actually performing the new way of working, if the person never wanted to change in the first place. Skipping a door does not save time, it just means the person gets stuck later, at a different and harder to diagnose door.
HOW IT WORKS ADKAR is an acronym for the five sequential outcomes a person needs to reach: Awareness of why the change is happening, Desire to participate and support it, Knowledge of how to change, Ability to put the new skills into practice, and Reinforcement to make the change stick rather than reverting to old habits under stress. Prosci built the model to be diagnostic, so if adoption stalls, a change manager can assess which letter the majority of people are stuck at and target that specific gap, rather than re-running generic training on everyone.
WHEN IT MATTERS ADKAR earns its keep on changes big enough that behavior, not just configuration, has to shift: an ERP rollout, a merger integrating two teams' workflows, adoption of a new tool inside a workflow. The footgun is running communication campaigns that only build Awareness and Desire, declaring victory at go-live, and then watching adoption collapse weeks later because nobody reinforced the new behavior once the launch excitement faded.
ONE CONCRETE EXAMPLE A hospital replacing its scheduling software finds adoption stuck at 40 percent a month after launch. An ADKAR assessment shows staff are aware of the change and know how to use the new system, but never wanted to leave the old one, a Desire gap. The fix is not more training, it is nurse managers addressing specific frustrations directly, not another tutorial video.
Read the original → prosci.com
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.