The ADKAR Model is useful when a Lean, Six Sigma, digital, quality, or leadership change depends on people adopting new behaviors. It helps teams diagnose where adoption is blocked and choose support actions that match the real barrier.
Definition
ADKAR is a change management model focused on individual adoption. The acronym stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. The model helps leaders evaluate whether people understand why a change is needed, want to participate, know how to change, can perform the new behavior, and receive reinforcement to sustain it.
In continuous improvement, ADKAR is useful because technical fixes often fail when adoption is weak. A new standard work document, control plan, digital system, audit process, or daily management routine only creates value if people actually use it correctly and consistently.
History
ADKAR is widely associated with Prosci change management practice and Jeff Hiatt's work on individual change. It became popular because it translates organizational change into observable individual conditions. Rather than treating adoption as a communication task alone, ADKAR asks whether each person or group has progressed through the conditions needed to change behavior.
The model is now used across manufacturing, healthcare, service, government, software, and corporate transformation work. It pairs well with Lean and Six Sigma because improvement projects often introduce new routines, controls, responsibilities, metrics, technology, or decision rights that require sustained behavior change.
When to Use
Use ADKAR when the success of an improvement depends on people changing how they work. Common uses include standard work rollout, 5S sustainment, daily management, layered process audits, new quality systems, ERP or MES deployment, control plan changes, safety behaviors, leader standard work, training transfer, and process ownership changes.
ADKAR is especially helpful when a technically sound improvement is not being adopted. If people ignore the new method, work around the system, return to old habits, resist the change, or perform inconsistently after training, the model helps diagnose whether the barrier is awareness, desire, knowledge, ability, or reinforcement.
Step-by-Step
- Define the change and impacted groups. State the specific behavior or work practice that must change. Identify operators, supervisors, engineers, managers, support functions, suppliers, or customers affected by the change.
- Assess Awareness. Determine whether people understand why the change is necessary, what problem it solves, what risk it addresses, and what happens if nothing changes.
- Assess Desire. Determine whether people are willing to support or participate in the change. Address incentives, trust, workload, fear, past failed changes, leadership credibility, and personal impact.
- Build Knowledge. Provide the information, training, job aids, examples, procedures, and expectations needed to perform the new work correctly.
- Develop Ability. Create practice, coaching, feedback, time, tools, access, and local problem solving so people can perform the new behavior under real working conditions.
- Reinforce the change. Use audits, metrics, leader follow-up, recognition, corrective coaching, visual management, standard work review, and process ownership to prevent drift back to the old method.
- Measure adoption and adjust. Track actual use, process outcomes, user feedback, variation by shift or site, and sustainment performance. Intervene at the ADKAR element where adoption is weakest.
Examples
- Standard work rollout: A production area updates standard work after a kaizen event. Awareness explains the defect and safety risk. Desire is built by involving operators in trials. Knowledge comes through job instruction. Ability is developed through coached practice. Reinforcement comes through leader standard work and layered audits.
- Digital quality system: A plant replaces paper inspection logs with a tablet system. ADKAR reveals that operators know how to use the tablet but lack desire because the system slows them down during changeovers. The team improves screen flow and adds shift-level support before enforcing compliance.
- 5S sustainment: A team launches 5S but results fade after two months. ADKAR shows that reinforcement is weak: audits are irregular, supervisors do not review findings, and no one owns corrective actions. The team adds daily ownership checks and visual accountability.
- Control plan change: Engineering changes inspection frequency after a customer complaint. Awareness covers the customer impact, Knowledge covers the revised control plan, Ability is verified through observed checks, and Reinforcement comes from SPC review and supervisor confirmation.
Common Pitfalls
- Starting with training. Training builds Knowledge, but it does not automatically create Awareness, Desire, Ability, or Reinforcement.
- Assuming communication equals adoption. People may have heard the message and still not understand, agree, know how, or have the support needed to change.
- Ignoring supervisors and local leaders. Frontline managers often determine whether a change becomes the normal way of working or another abandoned initiative.
- Blaming resistance too quickly. What looks like resistance may be missing knowledge, unclear priorities, conflicting metrics, insufficient staffing, poor tools, or unresolved process barriers.
- Measuring installation instead of adoption. A procedure can be released, a system can go live, and training can be completed while behavior remains unchanged.
- No reinforcement plan. Without follow-up, feedback, recognition, and correction, old habits usually return when attention moves elsewhere.