The ADKAR method is an individual-centered change management model developed by Jeff Hiatt, founder of the Prosci consultancy. Its acronym stands for five sequential steps: Awareness, Desire, Knowledge, Ability, and Reinforcement. Unlike frameworks that describe change from the organization’s perspective, ADKAR assumes that a transformation project only succeeds if each employee personally passes through these five stages.
Adoption Threshold: The Criterion That ADKAR Requires Measuring
Most change management models focus on technical deployment. A solution is delivered, a tool is configured, and the project is declared complete. ADKAR shifts the focus to actual usage.
See also : Everything You Need to Know About Gosling Growth: Key Stages and Development
Change management practitioners identify a critical adoption threshold (often around 70 to 80% of active users) below which the project remains at risk, even if the technical delivery is complete. ADKAR provides a framework to manage this threshold step by step: as long as the Awareness phase is not reached by a majority of employees, moving to training (Knowledge) wastes budget.
This management by usage, not just by project timeline, explains why companies adopting the ADKAR method and its training on Campus Recrutement are redirecting their success indicators towards usage rates rather than production dates.
See also : Discover everything you need to know about the HDTS format
The Five ADKAR Steps Analyzed in Order
Each letter of the acronym represents a prerequisite for the next. Skipping a step or conducting them in parallel weakens the process.
Awareness: Diagnosing Before the Remedy
Awareness focuses on the nature of the change and the reasons that make it necessary. At this stage, the goal is not to convince but to inform. An employee who does not understand why their business tool will be replaced will resist any training, even excellent training.
Desire: Fostering Individual Commitment
The desire to participate in the change cannot be decreed. It depends on each person’s perception of the personal and collective benefits. The role of the immediate manager is crucial at this stage, as the direct relationship with the superior influences the willingness to engage more than any institutional communication.
Knowledge: Transferring Necessary Skills
Knowledge concerns the “how.” It encompasses training, documentation, and practical workshops. A training plan launched too early (before Awareness and Desire are established) results in sessions where participants disengage.
Ability: Moving from Theory to Practice
Knowing is not enough. Ability is verified in the actual execution of new tasks, in the field. This step takes time and requires close support: coaching, pairing, and a gradual ramp-up period.
Reinforcement: Anchoring Change Over Time
Without anchoring mechanisms (recognition, monitoring indicators, adjustments), old habits resurface. Reinforcement closes the loop and protects the investment made in the previous four steps.
ADKAR vs. Kotter and Lewin: Choosing Based on the Type of Transformation
Guides published by consulting firms since 2023-2024 explicitly compare ADKAR to two other widely used frameworks: Kotter’s eight steps and Lewin’s Unfreeze-Change-Refreeze model. The choice depends on the nature of the project.
- The Lewin model is suitable for simple transformations, with a clear initial state and target state. Its strength lies in its clarity, but it does not provide an individual analysis framework.
- Kotter’s eight steps structure change at the organizational level, with a strong emphasis on the leadership coalition and vision communication. Kotter is relevant when change is driven from the top of the hierarchy.
- ADKAR stands out for its individual granularity. It allows for precise identification of where an employee or group is stuck (awareness, desire, competence) and adjusts support accordingly.
These models are not mutually exclusive. Teams use Kotter to frame the overall strategy and ADKAR to manage adoption on a case-by-case basis. This complementarity is increasingly documented in recent consulting offerings.
Diagnosing a Blockage with ADKAR: The Resistance Point Method
One of ADKAR’s most concrete contributions is its ability to locate a blockage. For each employee or group, it is enough to go through the five steps in order and identify the first one that is not validated. This is the point of resistance.
A common example: a team has undergone comprehensive training on new software (Knowledge acquired), but the usage rate remains low. The reflex would be to offer additional training. With ADKAR, a quick diagnosis often reveals that the problem lies upstream, at the Desire level. Employees understand the tool but do not see the point in changing their habits.
Addressing the right level avoids wasting resources on the wrong lever. This is the difference between unnecessarily retraining and working on managerial buy-in.
This diagnostic logic also works at the scale of an entire project. By aggregating points of resistance by step, the project team obtains a map that guides corrective actions: a communication campaign if Awareness is low, manager involvement if Desire is an issue, field coaching if Ability is blocked.
The ADKAR model derives its value not from a promise of rapid transformation but from a framework that makes each blockage identifiable and each corrective action targeted. A change project driven by actual usage is more likely to achieve its objectives than a project measured solely by its technical milestones.