Most Lean Six Sigma projects don’t fail because of bad data or flawed process maps. They fail because people aren’t ready for the change. You can redesign a workflow down to the second, but if the team running it doesn’t understand why it matters, or how to sustain it, the improvement won’t stick. That’s exactly the gap the Prosci ADKAR model fills. It gives you a structured, repeatable way to move individuals through change, one building block at a time: Awareness, Desire, Knowledge, Ability, and Reinforcement.
At Lean Six Sigma Experts, we’ve seen this play out across hundreds of engagements since 2011. Organizations invest heavily in process improvement only to watch results erode within months. The missing piece is almost always change management at the individual level. ADKAR provides the framework to close that gap, and it pairs naturally with the data-driven, engineering-based approach we bring to consulting, training, and recruiting.
This guide breaks down each of the five ADKAR building blocks, explains how they work in sequence, and shows you how to apply them to real organizational change. Whether you’re rolling out a new standard work process, restructuring a production line, or deploying Lean across multiple sites, you’ll walk away with a clear, actionable understanding of how to use ADKAR to make change actually last. Let’s get into it.
What the Prosci ADKAR model is
The Prosci ADKAR model is a goal-oriented change management framework that focuses on individuals rather than organizations as a whole. The name is an acronym: Awareness, Desire, Knowledge, Ability, and Reinforcement. These five elements represent the building blocks that every person must move through for a change to take hold. If any single element is missing, the change stalls at that point, and no amount of top-down pressure will push it forward sustainably.
The origin of ADKAR
Prosci founder Jeff Hiatt developed the ADKAR model in the 1990s after studying hundreds of organizational changes across multiple industries. He noticed that successful changes shared a common pattern: people moved through the same sequence of personal transitions, regardless of the type or scale of the change. Hiatt formalized those observations into the ADKAR framework and published the model in his 2006 book, which Prosci later built an entire change management methodology around.
ADKAR is one of the most widely used change management models in the world because it answers a question most frameworks ignore: what does an individual actually need to change successfully?
What separates ADKAR from earlier change theories is its bottom-up orientation. Most change models focus on organizational levers like communication plans, governance structures, or project timelines. ADKAR starts with the person doing the work and treats individual adoption as the fundamental unit of change, which is why it tends to produce more durable results when applied correctly.
The five letters explained
Each letter in ADKAR maps to a specific psychological or behavioral state that a person must reach before moving to the next. Skipping a step, or assuming someone has already reached it, is one of the fastest ways to derail a change effort. Here is what each element means in practice:
| Letter | Element | What it means |
|---|---|---|
| A | Awareness | The person understands why the change is needed |
| D | Desire | The person actively wants to support and participate in the change |
| K | Knowledge | The person knows how to change, including required skills and behaviors |
| A | Ability | The person can apply the knowledge and demonstrate the new behavior |
| R | Reinforcement | The new behavior is sustained through recognition, feedback, and accountability |
The model is strictly sequential by design. You cannot build Desire before someone has Awareness, and you cannot expect Ability without first providing Knowledge. This sequencing is not arbitrary; it reflects how people actually process and internalize change, which is what gives ADKAR its diagnostic power.
How ADKAR fits into the Prosci methodology
Prosci developed a broader three-phase change management process that includes preparing for change, managing the change, and sustaining outcomes. The ADKAR model sits at the core of all three phases, providing the individual-level lens through which every activity is filtered. When you build a communication plan, you are targeting Awareness. When you run training sessions, you are building Knowledge and Ability.
Organizations that use the full Prosci methodology apply ADKAR assessments at regular intervals throughout a project to identify exactly where individuals are getting stuck. This turns ADKAR from a conceptual model into a practical diagnostic tool that tells you where to focus resources at any given moment. For teams already running Lean Six Sigma projects, this kind of precision feels familiar because it mirrors the same root-cause thinking that drives effective process improvement work.
Why ADKAR works for change
Most change management approaches focus on the organization as a system. They produce project charters, steering committees, and communication plans, but they rarely ask the harder question: what does each individual person actually need to shift their behavior? That gap is exactly why so many change efforts fail at the ground level even when leadership is aligned and resources are committed. The prosci adkar model works because it closes that gap by treating individual change as the primary unit of analysis, not an afterthought.
It targets the right level of change
Organizations don’t change. People within them do. This sounds obvious, but most change frameworks design interventions at the organizational level and assume the individual will follow. ADKAR flips that assumption. Every tactic you deploy, whether it’s a town hall, a training session, or a supervisor conversation, gets evaluated against one question: does this move a specific person forward in the five-element sequence?
The moment you start measuring change at the individual level, you stop guessing and start managing.
This individual focus makes ADKAR highly practical for operations and plant managers who already track performance at the person and team level. You don’t need to abstract change into theoretical constructs. You identify where each team member is in the sequence and apply the right intervention at the right time.
It gives you a diagnostic tool, not just a theory
Many frameworks tell you what good change looks like in hindsight. ADKAR tells you where a change is breaking down in real time. Because the five elements are sequential and measurable, you can assess each person at any point in a project and pinpoint the exact barrier preventing adoption.
If someone has Awareness and Desire but lacks Knowledge, the fix is targeted training, not more communication. If they have Knowledge but can’t demonstrate Ability, the fix is coaching or hands-on practice, not another email. This precision prevents the most common waste in change management: applying the wrong intervention to the wrong problem.
Scaling is where ADKAR continues to deliver. You can aggregate individual assessments to identify systemic barriers across a department or location, then address them with coordinated action. For organizations running Lean Six Sigma programs across multiple facilities, that kind of scalable diagnostic precision is not optional; it is a requirement for sustainable improvement that holds up months after the project closes.
The five ADKAR building blocks
Each element in the prosci adkar model functions as a milestone, not a checkbox. A person must genuinely reach each state before the next one becomes achievable. Understanding what each building block actually means in practice, not just in theory, is what separates change managers who get lasting results from those who watch improvements backslide within a quarter.
Awareness and Desire
Awareness is the starting point. It means the person understands why the change is necessary, including the risk of not changing. This is not the same as being informed. You can announce a change without creating Awareness if the communication does not clearly connect the "why" to something that person cares about. Effective Awareness-building requires context, not just information.
Desire is where many change efforts quietly fall apart. A person can understand why a change is happening and still choose not to support it. Desire is an active, personal commitment to participate, and you cannot mandate it. Your job is to create the conditions that make supporting the change the logical, even attractive, choice, through credible leadership, visible consequences, and honest two-way dialogue.
Building Desire requires addressing individual motivations, not delivering organizational talking points.
Knowledge and Ability
Knowledge covers what a person needs to know in order to change: the new processes, behaviors, skills, and tools involved. This is where structured training, documentation, and coaching come into play. Knowledge without Ability, however, produces people who understand the new way but cannot yet execute it consistently. That gap is common and it is manageable if you recognize it early.
Ability is the demonstrated capacity to perform the change. It only develops through practice, feedback, and time. Some people move from Knowledge to Ability quickly; others need more repetitions, more coaching, or a different instructional approach. Treating Ability as automatic once training is complete is one of the most common and costly assumptions in change management.
Reinforcement
Reinforcement is what prevents regression. Once someone demonstrates the new behavior, the environment around them must actively support sustaining it through recognition, accountability structures, and corrective feedback loops. Without Reinforcement, people naturally drift back to familiar patterns, especially under pressure. This is not a character flaw; it is a predictable human response to an environment that no longer rewards the new behavior.
Your Reinforcement plan should include both positive recognition and mechanisms for catching and correcting slippage early, before it becomes the new norm.
How to apply ADKAR step by step
Applying the prosci adkar model in a real project is not about running through five checkboxes in sequence and calling it done. It requires intentional planning at the start, active monitoring throughout, and structured follow-through after go-live. The steps below give you a practical sequence for putting ADKAR to work, from the first day of your change initiative to the point where the new behavior becomes standard practice across your team.
Start with a change readiness assessment
Before you build any communication plan or training schedule, you need to know where your people currently stand relative to the change. Conduct structured conversations or a brief survey with a representative sample of the individuals most affected. Your goal is to determine whether Awareness even exists yet, and whether early resistance signals a Desire gap or a deeper misalignment with the change rationale. This baseline information shapes every subsequent decision you make about intervention design and timing.
Skipping the readiness assessment means designing interventions based on assumptions, which is the fastest route to wasted effort.
Map your interventions to each ADKAR element
Once you have a baseline, align every planned activity to a specific element in the sequence. This is where most teams gain real clarity, because it forces them to examine whether their communication plan actually builds Awareness or simply announces the change. Use the mapping structure below as a starting framework:
| ADKAR Element | Intervention Type | Example |
|---|---|---|
| Awareness | Communication | Town halls, leader messaging, project briefings |
| Desire | Engagement | One-on-one conversations, visible leadership support |
| Knowledge | Training | Structured courses, job aids, standard work documentation |
| Ability | Practice | Coaching, supervised repetition, pilot runs |
| Reinforcement | Accountability | Recognition programs, audits, performance feedback |
Each intervention should have a clear owner and a measurable outcome so you can track whether it is actually moving people forward or just generating activity on your project plan.
Run structured checkpoints throughout the project
ADKAR assessments are not a one-time exercise. You need to reassess individuals at defined intervals, particularly at major project milestones like pilot completion, full rollout, and the 30-to-90-day post-go-live window. Ask direct questions about each element and compare results to your baseline. When you find someone who has stalled, identify the specific element where they are blocked and apply a targeted intervention rather than repeating the same general communication that already failed to move them forward.
How to diagnose and remove ADKAR barriers
A barrier in the prosci adkar model is any point where an individual stops progressing through the five-element sequence. Barriers are not signs of failure; they are diagnostic data. The model’s sequential structure means you can pinpoint exactly where someone has stalled and apply a specific fix rather than a generic response. The faster you identify the barrier, the less time you waste applying the wrong intervention to the wrong problem.
How to identify the exact barrier
Most barriers reveal themselves through observable behavior and direct conversation. When someone resists a change, the instinct is often to send more communication or repeat the training. But resistance at the Ability stage looks completely different from resistance at the Desire stage, and treating them the same way guarantees poor results. Your first job is to ask structured diagnostic questions that correspond to each ADKAR element before you design any response.
The barrier is never "resistance to change" in the abstract. It is always a specific gap in one of the five elements, and your intervention needs to match that gap exactly.
Use this question set to pinpoint where someone is blocked:
| ADKAR Element | Diagnostic Question |
|---|---|
| Awareness | Does this person understand why the change is happening? |
| Desire | Does this person want to support the change? |
| Knowledge | Does this person know what to do differently? |
| Ability | Can this person demonstrate the new behavior consistently? |
| Reinforcement | Does the environment reward and sustain the new behavior? |
The first "no" answer you hit identifies the exact barrier. Everything above that point is irrelevant to address until you close the actual gap you have identified.
How to remove each type of barrier
Awareness barriers require better communication, specifically the kind that connects the change to something the individual personally values or risks losing. Desire barriers require direct leadership involvement, honest dialogue about concerns, and visible consequences for not changing. You cannot train your way out of a Desire problem, and more information will not fix a motivation gap.
Knowledge barriers respond well to targeted training, job aids, and clear documentation of new procedures. Ability barriers require practice time, hands-on coaching, and a safe environment to make mistakes without penalty. Reinforcement barriers are structural: they require you to redesign the feedback and accountability systems in the work environment so the new behavior is consistently rewarded and early signs of slippage are corrected before they become the new default.
How to measure adoption and reinforcement
Measuring adoption is not the same as measuring activity. Most project teams track whether people attended training or received a communication, but those metrics tell you what happened to people, not whether they actually changed. The prosci adkar model requires a different measurement mindset: you need to track behavioral evidence that each person has genuinely moved through the five elements, particularly Ability and Reinforcement, which are the hardest to fake and the most predictive of whether the change will last.
Track behavioral indicators, not just completion rates
The most reliable evidence of adoption is observable behavior on the job, not a signed training acknowledgment form. Work with frontline supervisors to define two or three specific behaviors that demonstrate the new standard is being practiced correctly. Then build a lightweight observation and documentation routine so those behaviors get tracked consistently at regular intervals, not just during the first week after go-live.
This does not require a complex tracking system. A structured checklist that supervisors complete during regular floor walks or team huddles generates the data you need. Use the following categories to shape your behavioral measurement approach:
| Measurement Category | What to Track |
|---|---|
| Process compliance | Are people following the new procedure consistently? |
| Error and rework rates | Has the defect or exception rate shifted since go-live? |
| Supervisor observation | Are the target behaviors visible on the job daily? |
| Peer feedback | Are team members reinforcing the new way with each other? |
Behavioral data tells you whether adoption is real. Completion data only tells you whether the event happened.
Build a reinforcement feedback loop
Reinforcement without a feedback mechanism is just hope. Once you have behavioral data coming in consistently, you need a structured process for acting on it. When the data shows someone is drifting back toward the old behavior, the response must be immediate, specific, and supportive, not punitive. The goal is to catch regression early and correct it before it spreads across the team and quietly becomes the new default.
Positive reinforcement matters just as much. Identify and visibly recognize individuals who are consistently demonstrating the new behavior, and make that recognition visible to the broader team. When people see that adopting the change produces real acknowledgment from leadership, it strengthens both Desire and Reinforcement for everyone observing it. Build this recognition loop into your standard management cadence so it runs automatically rather than only when someone on the project team remembers to act on it.
Common ADKAR mistakes and fixes
Even when teams are familiar with the prosci adkar model, implementation errors tend to cluster around the same predictable patterns. Understanding where these mistakes happen, and what to do instead, keeps your change effort moving forward without losing months to rework or watching adoption slip backward after go-live.
Treating ADKAR as a one-time sequence
The most common mistake is running through the five elements once, marking each as complete, and moving on. ADKAR is a living diagnostic tool, not a project phase you graduate from. People cycle back through elements when workloads spike, when team composition changes, or when they move into a new role affected by the change. If you treat the model as a linear checklist, you will miss the regressions that quietly undo your results.
Adoption is not an event. It is a sustained state that requires active maintenance well past the go-live date.
The fix is to build recurring ADKAR checkpoints into your standard operating rhythm, not just your project schedule. Quarterly check-ins for high-impact changes are a reasonable minimum, and frontline supervisors should know how to spot early signs that someone is slipping back toward an earlier element.
Skipping reinforcement planning
Many change managers front-load their energy into Awareness and Knowledge activities and treat Reinforcement as a vague afterthought. This is the direct cause of the "six-month backslide" that operations teams recognize immediately: strong early adoption that erodes once the project team disbands and attention moves elsewhere. Reinforcement is not optional; it is the structural support that keeps everything above it in place.
The fix is to design your reinforcement mechanisms before go-live, not after you notice regression. Identify the specific recognition actions, accountability checkpoints, and feedback loops that will sustain the new behavior, assign clear owners to each, and tie them to existing management routines so they run without depending on project team involvement.
Applying the wrong intervention to the right problem
Sending more communication to someone stuck at the Ability stage wastes everyone’s time. Scheduling another training session for someone blocked by Desire produces the same result. Mismatched interventions are one of the most expensive mistakes in change management because they consume resources without moving anyone forward.
The fix is straightforward: diagnose before you intervene. Ask the structured diagnostic questions that correspond to each ADKAR element, identify the first gap you find, and apply only the intervention that directly addresses that specific element. Precision here is not optional if you want results that hold.
Prosci ADKAR model vs other change models
The prosci adkar model is not the only change framework available, and it does not claim to be. What separates it from the alternatives is its individual-level focus and diagnostic specificity. Understanding how it compares to the most common competing frameworks helps you choose the right tool for the right problem, or decide how to layer multiple approaches together when a project demands it.
ADKAR vs Kotter’s 8-Step Model
Kotter’s 8-Step Model is one of the most recognized change frameworks in organizational leadership. It was designed to guide senior leaders through a top-down transformation sequence, moving from creating urgency to anchoring change in culture. The steps are logical and the framework is well-documented, but it operates primarily at the organizational level. It tells leadership teams what to do in sequence; it does not tell you why a specific employee on the production floor is still using the old process three months after go-live.
ADKAR fills the gap that Kotter leaves open: it addresses what each individual needs, not just what leadership should do next.
That distinction matters significantly for operations teams running Lean Six Sigma projects. You can follow every step in Kotter’s model and still watch adoption collapse at the ground level if you have not addressed individual-level barriers. The two frameworks are not competitors; they are complementary at different layers of the organization.
ADKAR vs McKinsey 7-S and Lewin’s Change Model
Lewin’s three-stage model (Unfreeze, Change, Refreeze) provides a useful conceptual lens for understanding how change disrupts and then stabilizes organizational behavior. It is simple, durable, and widely taught. The limitation is that it offers no mechanism for diagnosing where individuals get stuck within any of those three stages. When adoption stalls, Lewin gives you no structured way to identify whether the problem is awareness, motivation, skill, or environment.
McKinsey’s 7-S Model focuses on seven interconnected organizational elements (strategy, structure, systems, shared values, style, staff, and skills) and is most useful for analyzing whether an organization’s internal elements are aligned before and after a change. It is a strong diagnostic tool at the organizational level, but it does not speak to individual behavior in any granular way.
ADKAR is the only major framework in this group that gives you a person-by-person diagnostic tool that pinpoints the exact barrier preventing adoption and tells you which specific intervention will address it. For teams accountable for measurable, sustained results, that level of precision is what converts change management from a soft discipline into an engineering-grade practice.
Key takeaways
The prosci adkar model gives you a structured, sequential way to move individuals through change by addressing Awareness, Desire, Knowledge, Ability, and Reinforcement in order. Skip any element and the change stalls at that exact point.
What makes ADKAR practical is its diagnostic precision. When adoption breaks down, you can pinpoint the specific element causing the barrier and apply only the intervention that addresses it directly. That precision prevents the most common waste in change management: applying the wrong fix to the wrong problem.
Sustained results require more than a strong go-live. Reinforcement planning must start before the project closes, and behavioral measurement needs to run continuously, not just during rollout. Combine ADKAR with your existing Lean Six Sigma discipline and you close the gap between process improvement on paper and improvement that actually holds.
Ready to put these principles to work in your organization? Contact Lean Six Sigma Experts to get started.