ADKAR is a change management model developed by Jeff Hiatt (Prosci) that structures individual change in five stages: awareness, desire, knowledge, ability and reinforcement.
The ADKAR model is a change management model developed by Jeff Hiatt, associated with the organization Prosci. It structures change at the level of the individual and breaks it into five sequential building blocks, which give the model its name: awareness, desire, knowledge, ability and reinforcement. Hiatt first published the model in 1999 in a white paper called The Perfect Change, and later work from 2006 is associated with Prosci.
Each of the five building blocks answers a specific question about a person affected by a change. Awareness covers why the change is needed. Desire describes the willingness to take part in the change and support it. Knowledge refers to what a person has to do during and after the change. Ability is the capacity to carry out the change as required. Reinforcement keeps the results in place once the change has been made. Because the focus is on the individual, ADKAR is typically used to understand why a particular person or group is not yet adopting a new way of working, rather than to describe an organization as a whole.
ADKAR is described as prescriptive and goal-oriented. Each milestone has to be achieved for the change to count as successful, and individuals can be scored from 1 to 5 on each of them. A score of 3 or below is called a barrier point and has to be addressed before moving on to the next step. According to Hiatt, the steps run in order, begin from each person's current level and cannot be skipped or reordered. The strict sequencing is presented as a design feature of the model.
In the Microsoft ecosystem, ADKAR comes up in discussions of technology adoption and change management. The M365.FM episode "Dynamics 365 Project Operations with Joe Griffin [MVP]" mentions it in the context of a migration to Dynamics 365 Project Operations. The episode says that teams need awareness and buy-in, and that the benefits of the new system, such as improved AI-driven automation and better project visibility, should be communicated. Experts are quoted as recommending the ADKAR model to guide change management efforts. The episode also advises customizing training programs for different roles, monitoring resistance, listening to feedback and addressing concerns quickly. For the final stage, it suggests recognizing team members who adapt well and tracking adoption metrics to reinforce and sustain the change.
The second episode, "Microsoft Copilot Adoption with Edyta Gorzoń [MVP]", links ADKAR to the Microsoft Engagement Framework, which the episode says follows the ADKAR model. It describes the framework as working well for change management, guiding users through awareness, desire, knowledge, ability and reinforcement so that they move from learning about Copilot to using it confidently. In the same discussion, the episode lists concerns such as privacy and trusting AI-generated content, and recommends open communication, simple language and real examples while avoiding technical jargon. It also notes that building new habits takes time and support, that instant results should not be expected, and that teams should be encouraged to use Copilot daily with ongoing training.
Taken together, the sources show how ADKAR is applied in practice: as a checklist of individual stages that helps decide where a rollout is stuck. A lack of awareness calls for communication about the reasons for a change. Low desire points to resistance that needs to be heard. Gaps in knowledge and ability call for role-specific training and support. Weak reinforcement calls for recognition and adoption tracking. The article on ADKAR does not describe criticism aimed specifically at the model; the criticism it mentions concerns Kurt Lewin's three-step model, which some scholars called simplistic.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
This episode goes straight into the uncomfortable truth behind Microsoft Copilot: the same AI that accelerates your workflows can also expose your most sensitive data if you don’t govern it correctly. We unpack how Copilot for Microsoft 365 pulls information…
In this episode of the m365.fm podcast, Mirko Peters speaks with Microsoft MVP and Copilot adoption expert Edyta Gorzoń about why successful Microsoft Copilot adoption is far more than a technical deployment project. The conversation focuses on the gap many…
Timeline of episodes about ADKAR model
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What are the five stages of the ADKAR model? (AI)
The five stages are awareness, desire, knowledge, ability and reinforcement. They describe why a change is needed, the willingness to support it, what to do, the capacity to do it and how the results are kept in place.
Who developed the ADKAR model? (AI)
Jeff Hiatt developed it and first published it in 1999 in a white paper called The Perfect Change. Later work from 2006 is associated with his organization Prosci.
How does ADKAR relate to Microsoft Copilot and Dynamics 365 adoption? (AI)
The M365.FM episodes mention ADKAR as a guide for change management in a Dynamics 365 Project Operations migration. They also say that the Microsoft Engagement Framework for Copilot adoption follows the ADKAR model.
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.