The ADKAR Model: Change Management Explained

The ADKAR model is a change management framework that breaks organizational change into five sequential stages every individual must clear before a change can stick: Awareness, Desire, Knowledge, Ability, and Reinforcement. Developed by Prosci founder Jeff Hiatt after studying change patterns across more than 700 organizations, it is one of the most widely used frameworks in organizational development today.

Change fails more often than it succeeds. Prosci's benchmarking research, drawn from more than 10,800 contributors across 25 years, finds that organizations with excellent change management are seven times more likely to meet their project objectives than those with poor change management. Fabric uses the ADKAR model when onboarding enterprise clients onto its AI interview platform, treating recruiter adoption as a change initiative rather than a training checkbox. The ADKAR model is one of the tools that separates organizations that manage change from those that only announce it.

What Is the ADKAR Model?

The ADKAR model is a goal-oriented change management framework that tracks whether individual employees have made the shift a change initiative requires. The acronym stands for Awareness, Desire, Knowledge, Ability, and Reinforcement: the five outcomes each person must reach for a change to be real, not just announced. ADKAR was introduced by Jeff Hiatt, founder of Prosci, in 2006. Unlike change models that focus on organizational phases or project milestones, ADKAR focuses on the individual. A company can redesign its entire process, retrain its teams, and still fail if enough people have not genuinely moved through all five stages. ADKAR makes that individual-level gap visible and diagnosable. It turns the common question "why is this change not working?" into something answerable at the level of each person: which of the five stages have they not reached, and why?

The model is intentionally sequential. Each stage builds on the last. You cannot shortcut Desire by piling on Knowledge, and you cannot sustain a change through Reinforcement if people never had real Ability. Skipping a stage does not speed up the change. It creates a gap the change eventually falls into.

If you are planning a hiring technology rollout, the ADKAR model is a practical framework for managing recruiter adoption from day one. See how Fabric applies it in practice →

The 5 Stages of ADKAR Change Management

The ADKAR model identifies five stages that every individual must move through for a change to succeed: Awareness, Desire, Knowledge, Ability, and Reinforcement. The model is sequential by design. Each stage is a prerequisite for the next. An employee who knows how to perform a new behavior but does not want to will not. An employee who wants to change but does not know how cannot. ADKAR's diagnostic value comes from this structure: when a change initiative stalls, the model tells you exactly which stage is missing at the individual level, rather than pointing vaguely at "resistance" or "adoption." Organizations that use ADKAR as a measurement tool, checking each stage per team or per person, can redirect resources to the specific gap rather than applying generic remedies to the whole workforce. That precision is what makes ADKAR a measurement framework, not just a communications plan.

Awareness

Awareness means employees understand the reason for the change, the risk of not changing, and what the change means for them personally. A company-wide email from leadership is not awareness. It is an announcement. Real awareness happens through conversations with direct managers, context that connects the change to what employees already care about, and enough time for the message to land.

Organizations that rush past Awareness by moving straight to training often find employees resistant, not because they reject the change, but because they do not understand why it is happening. The fix is not more training. The fix is going back to Awareness.

Desire

Desire is the stage that no training budget can replace. It is personal. Each employee decides, consciously or not, whether they want to support this change or resist it. Organizations can influence Desire by addressing the "what's in it for me" question directly, involving employees early in design decisions, and naming resistance openly rather than treating it as insubordination. But Desire cannot be forced. When it is missing, the change stalls after rollout.

Knowledge

Knowledge covers what people need to know to change. This includes training on new processes, documentation, job aids, and the institutional knowledge transition that moves understanding from people who know the old way to people building the new one. Training sessions are the start of knowledge transfer, not the end. Organizations that measure knowledge by training attendance rather than retention routinely underinvest in this stage.

Ability

Ability is the gap between knowing and doing. Employees can attend every training session and still not execute the new behavior under real working conditions. Closing the Ability gap means hands-on practice: role plays, sandbox environments, shadowing, with feedback loops that catch mistakes before they calcify. Ability takes longer to build than Knowledge. Treating them as the same thing is one of the most common ADKAR implementation errors.

Reinforcement

Reinforcement is what keeps a change from reverting. It includes metrics, recognition of compliance, active correction of backsliding, and embedding the new behavior into normal operations and performance expectations. Organizations that measure Reinforcement seriously, tracking adoption rates, spotting teams slipping back to old patterns, and publicly recognizing exemplary compliance, sustain the change. Organizations that stop after launch typically run the same initiative again 18 months later.

ADKAR in Practice: A Change Management Example

The ADKAR model is most useful when you can trace it through a real change. Consider what happens when an HR team transitions from manual resume screening to AI-assisted screening. Without a structured change management approach, this kind of technology rollout typically produces low adoption: recruiters maintain workarounds, revert to old habits, or comply on paper while avoiding the tool in practice. The ADKAR model prevents this by diagnosing where each individual is in their adoption journey. Awareness asks whether recruiters know why the change is happening. Desire asks whether they have chosen to participate. Knowledge asks whether they have the skills and information to act. Ability asks whether they can execute under real conditions, not just in training. Reinforcement asks whether the new behavior is being sustained over time. Working through each stage in sequence is what turns a technology rollout into a change that holds.

Here is how that maps to a real AI screening rollout:

• Awareness: Recruiters are shown why manual screening is costing the business: slower time-to-fill, inconsistent quality, recruiters spending most of their working hours on first-round screening that produces unreliable shortlists.
• Desire: Team leads meet with recruiters individually to surface concerns about being replaced or evaluated differently. Those concerns are addressed directly. Early adopters are invited into a pilot with genuine feedback loops, not a rubber-stamp preview.
• Knowledge: Recruiters go through hands-on training, receive a recorded walkthrough they can revisit, and get a job aid covering their most common use cases in the new system.
• Ability: They run three live roles using the new tool with a manager reviewing each and providing real-time feedback. They do not go fully independent until they have handled several sessions end to end.
• Reinforcement: Adoption is tracked. A dashboard shows which recruiters are using the tool consistently. High-adoption teams are recognized in monthly reviews. Teams slipping back to manual screening get a check-in, not a reprimand.

The change succeeds not because the technology is good, but because each recruiter moved through all five ADKAR stages.

ADKAR and Organizational Development

Organizational development is the discipline concerned with improving an organization's long-term capacity through planned, evidence-based interventions: restructuring, culture change, and the adoption of new tools and processes. ADKAR is one of the most widely applied frameworks in organizational development because it gives practitioners a way to diagnose exactly where a change is failing, not just that it is failing. When a change stalls, ADKAR makes the diagnosis specific. Are people stuck at Awareness, where they do not know why the change is happening? At Desire, where they know but do not want to participate? At Ability, where they understand but cannot execute under real conditions? Each barrier has a different fix. Treating a Desire problem with more Knowledge training wastes resources and erodes trust. ADKAR gives organizational development practitioners the precision to match the intervention to the actual barrier, not the assumed one.

Prosci's research found that 62% of successful change projects, those rated "good" or "excellent," use a specific change methodology, versus only 6% of projects rated "poor." The gap between organizations that manage change and organizations that announce it is largely methodological.

For organizational development professionals, ADKAR pairs naturally with succession planning and workforce restructuring. A 9-box grid can help identify which employees need more support at the Desire and Ability stages. Those with high potential but lower current performance often have the readiness to move but need more deliberate Reinforcement to sustain new behaviors.

ADKAR for Implementing Hiring Technology

When organizations introduce AI-assisted hiring tools, they are running a change initiative whether or not they call it one. The people most affected are the recruiters and hiring managers who have to change how they work daily. Running that rollout through the ADKAR model is what separates a sustainable adoption from a tool that gets abandoned three months after launch. The technology is rarely the problem. The problem is that organizations invest heavily in selecting and configuring the software and almost nothing in moving their people through Awareness, Desire, Knowledge, Ability, and Reinforcement. Recruiters who do not understand why the tool is being introduced tend to ignore it or build workarounds. Those who understand but feel their role is threatened resist it. Those who lack hands-on practice under-use it even after completing training. Managing the change with the same rigor as the implementation itself is what produces real adoption.

Fabric is an AI interview platform that runs a candidate's first round: resume screening, eligibility checks, and a live AI-led interview, before a recruiter gets involved. It does not replace the hiring decision; it gives recruiters a verified, panel-ready shortlist so human time goes to final-round decisions, not first-round screening. Implementing Fabric means changing how recruiters spend their day. That is a behavioral change, and it needs to be managed as one.

Fabric's onboarding is designed to move teams through each ADKAR stage: clear documentation of why the change matters (Awareness), pilot programs with genuine feedback loops (Desire), live training and reference materials (Knowledge), supported first runs on real roles with manager review (Ability), and adoption metrics with regular check-ins (Reinforcement). The ADKAR model is not just something CHROs read about. It is the framework behind how responsible hiring technology gets adopted.

*This article is for informational purposes only. Fabric's Interview Engine screens, scores, and records Round 1 interviews; it does not make the final hiring decision. The recruiter or hiring panel using Fabric remains responsible for all hiring decisions.*

Common ADKAR Mistakes to Avoid

Most ADKAR implementation failures come down to one of five mistakes: skipping stages, conflating Knowledge with Ability, neglecting Reinforcement after launch, using the model as a linear checklist rather than a diagnostic tool, or assuming every team member is stuck at the same barrier. Each mistake has a distinct symptom: low training retention, post-launch regression, employee workarounds, or teams that understood the change in theory but never adopted it in practice. ADKAR is not a prescription to follow in a single direction; it is a diagnostic to run in both directions. When a change is not sticking, the right response is to identify which specific stage has the gap and address that gap directly, not restart the entire rollout. Understanding where ADKAR fails in practice helps organizations avoid the failure modes that affect even well-resourced change programs.

Jumping to Knowledge before Desire is real. Training that arrives before employees understand or want the change produces low retention and high resistance. Sequence matters more than speed.

Confusing Ability with Knowledge. Attending a training is not the same as being able to execute. Knowledge is what people know; Ability is what they can actually do under real conditions. Build in practice time with feedback, not just delivery time.

Treating Reinforcement as a post-launch bonus. Most organizations concentrate change management effort on rollout and then stop. Reinforcement is what determines whether the change lasts. Track adoption actively; do not wait for problems to surface.

Using ADKAR as a communications checklist. ADKAR's real value is diagnostic: it tells you exactly which stage is failing when a change is not landing. Organizations that use it only as a rollout plan miss the model's most useful function.

Assuming one ADKAR barrier for everyone. Different team members get stuck at different stages. A team-wide Desire workshop will not help the person who is already bought in but lacks Ability. Diagnose at the individual or team level where you can.

FAQ

What does ADKAR stand for?

ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. Each word names one of the five outcomes an individual must reach for an organizational change to succeed at the individual level.

Who created the ADKAR model?

Jeff Hiatt, founder of Prosci, developed the ADKAR model in 2006. It emerged from research into change patterns across more than 700 organizations conducted over nearly a decade.

Is ADKAR a sequential model?

Yes. ADKAR is intentionally sequential. Each stage must be reached before the next is meaningful. Providing Knowledge training before Desire is established typically produces low retention and active resistance, because employees are not yet invested in the change.

What is the difference between ADKAR and Kotter's 8-Step Model?

Kotter's model focuses on organizational-level steps that leadership takes. ADKAR focuses on the individual employee's journey through a change. The two are complementary: Kotter describes what leaders do; ADKAR describes what needs to happen inside each person for those leadership actions to actually work.

When should you use the ADKAR model?

ADKAR is most useful when a change requires people to genuinely shift their ongoing behavior, not comply once, but work differently on a sustained basis. Software rollouts, process redesigns, reorganizations, and cultural shifts all benefit from an ADKAR approach. It is less suited to one-time procedural changes that require no sustained behavioral shift.

Related Posts

• 15 Best HRIS Systems: Compare Features, Pricing, and Reviews
• What Is an AI Interview? The Complete Guide for 2026
• How to Implement AI Interviews in Your Hiring Process

If your HR team is implementing new hiring technology, or planning to, the ADKAR model is the framework that turns a software rollout into a change that sticks. Fabric's enterprise onboarding is built with this in mind.