Prosci ADKAR Model (Awareness–Desire–Knowledge–Ability–Reinforcement)

Prosci ADKAR Model (Awareness–Desire–Knowledge–Ability–Reinforcement)

1. What Is Prosci ADKAR Model (Awareness–Desire–Knowledge–Ability–Reinforcement)?

The Prosci ADKAR Model is a practical, individual-centered framework for managing organizational change. It defines five building blocks that a person must progress through for a change to take root: Awareness of the need for change, Desire to participate and support it, Knowledge of how to change, Ability to apply new skills and behaviors, and Reinforcement to sustain results. When enough individuals make the transition, the organization changes.

Within the Organization function, it sits in the Change Management & Transformation family. Consultants and executives use ADKAR to diagnose adoption barriers at the level of people and roles, tailor interventions, and track progress throughout rollouts of new processes, systems, structures, or cultural norms.

In plain language: ADKAR helps you answer five questions for each stakeholder group—Do they understand why? Do they want to do it? Do they know what to do? Can they do it on the job? Will they keep doing it?—and act on the weakest link.

2. Origin and Background

The ADKAR Model was developed by Jeff Hiatt at Prosci in the late 1990s and early 2000s, and popularized through Prosci’s research and publications, including “ADKAR: A Model for Change in Business, Government and our Community” (2006). Prosci synthesized lessons from thousands of change projects into a human-centered structure that complements program and project management.

Why it was created: many transformations failed not because plans were poor, but because the people who needed to change didn’t—sponsors were invisible, stakeholders resisted silently, training didn’t translate to behavior, and new ways failed to stick. ADKAR offered a simple, diagnostic way to focus leadership time and resources where adoption actually breaks down.

How it spread: through practitioner training, corporate change programs, and integration into broader transformation methods. Today, ADKAR is one of the most widely used models for individual change within enterprise transformations.

3. How the ADKAR Model Works

ADKAR is built on a simple but powerful idea: organizational change succeeds when enough individuals make the shift. The model provides both a checklist and a diagnostic sequence. The components are:

  • Awareness (of the need for change)
    • What it is: Understanding the business reasons for the change and the risks of not changing.
    • How to create it: Compelling case for change, credible sponsor messages, data and customer stories, two-way communications that address “why now.”
  • Desire (to participate and support the change)
    • What it is: Personal motivation to engage—shaped by “what’s in it for me,” peer norms, trust in leadership, and perceived fairness.
    • How to create it: Visible sponsorship, manager coaching, incentives and recognition, mitigating personal losses (e.g., reskilling offers), and involving people in solution shaping.
  • Knowledge (on how to change)
    • What it is: The information, skills, and understanding of new processes, tools, and behaviors required.
    • How to build it: Role-based training, job aids, simulations, quick-reference guides, shadowing—delivered just-in-time and reinforced on the job.
  • Ability (to implement required skills and behaviors)
    • What it is: The demonstrated capability to perform in the new way in the real work environment.
    • How to enable it: Practice with feedback, removal of obstacles, coaching, process/tech usability, workload and time to apply, and performance support (e.g., “floor walkers”).
  • Reinforcement (to sustain the change)
    • What it is: Mechanisms that make the new way the default and recognize/require continued adherence.
    • How to ensure it: Updated KPIs and incentives, leader routines, audits and dashboards, recognition, consequences for non-adherence, and continuous improvement forums.

A critical principle in ADKAR is the barrier point: progress is limited by the first element that is insufficient. If a group lacks Desire, more Knowledge training won’t help. Practitioners assess each segment, identify its barrier point, and design targeted actions—sequencing Awareness → Desire → Knowledge → Ability → Reinforcement, while recognizing elements overlap in practice.

4. When to Use the ADKAR Model

Most helpful when:

  • Success hinges on behavior change across different roles (e.g., sales adopting a new CRM, nurses using a new EHR workflow, managers applying a new performance model).
  • You need a diagnostic lens to find why adoption is lagging (awareness gaps vs. motivation vs. skills vs. friction vs. backsliding).
  • You want a scalable approach to tailor change plans by stakeholder segment and track progress with simple metrics.

Especially powerful for: Technology rollouts, process standardization, safety/quality programs, operating model shifts where role clarity and daily behaviors matter.

Use with caution when:

  • The change is purely structural with limited behavioral impact; ADKAR may be overkill.
  • Leaders treat it as a communications-only exercise; ADKAR requires sponsor action, manager coaching, training, and system/role changes.
  • The environment is highly emergent without a defined target behavior; pair ADKAR with iterative discovery and adjust the “Knowledge/Ability” content as learning unfolds.

Current practice: High-performing teams integrate ADKAR into program governance: they use it to shape communications, sponsorship, training, and reinforcement plans—while delivery uses agile/lean methods and benefits management tracks value.

5. How to Apply the ADKAR Model: Step-by-Step

  1. Clarify the change and secure sponsorship

    Define the target state (processes, roles, systems, behaviors) and success metrics (adoption, proficiency, performance). Identify the executive sponsor and change leaders. Make sponsor responsibilities explicit (communicate the “why,” model behaviors, remove barriers, reward adoption).

  2. Segment stakeholders and assess ADKAR baselines

    Identify key groups (e.g., frontline users, supervisors, middle managers, back-office, partners). Use quick surveys, interviews, and manager inputs to rate each group 1–5 on Awareness, Desire, Knowledge, Ability, and Reinforcement. Visualize results in a heat map to find barrier points.

  3. Design a targeted change plan by ADKAR element and segment

    Create a matrix mapping segments to ADKAR actions:

    • Awareness: Sponsor videos, roadshows, customer stories, data on risk/opportunity; FAQs addressing “why now.”
    • Desire: “What’s in it for me” messages by role, involvement in pilots, manager one-on-ones, incentives aligned to early adoption, credible assurances on job impacts (reskilling, no-surprise policies).
    • Knowledge: Role-based curricula, e-learning + live practice, job aids, knowledge checks.
    • Ability: Practice labs, side-by-side coaching, simplified workflows, usability fixes, time allocations to practice.
    • Reinforcement: Updated KPIs, dashboards, recognition programs, policy/process lock-ins, audits, manager routines.

    Sequence interventions so no group is asked to perform before Awareness/Desire and Knowledge are in place.

  4. Launch Awareness and Desire waves

    Lead with the sponsor’s case for change and data-backed storytelling. Equip line managers with talk tracks and FAQs; they are the primary creators of Desire. Involve influencers in demos and pilots; showcase their candid feedback. Address losses fairly and transparently (e.g., role changes, reskilling timelines).

  5. Deliver Knowledge effectively (not just training)

    Build role-based content tied to real tasks. Use blended formats (short videos, hands-on practice, peer coaching). Time training close to go-live; provide searchable job aids. Confirm learning with simple assessments; remediate quickly.

  6. Enable Ability on the job

    Stand up “floor walkers,” hotlines, and SMEs during go-live. Reduce workload temporarily so people can practice. Remove process/tech friction fast (tickets triaged within 24–72 hours). Have managers observe and coach; track proficiency metrics (e.g., error rates, handle times).

  7. Reinforce and institutionalize

    Update scorecards, incentives, SOPs, and governance to make the new way the default. Recognize adopters and teams; address non-adherence consistently. Decommission old tools and processes to avoid backsliding. Establish communities of practice and cadence for continuous improvement.

  8. Measure, learn, and iterate

    Track both ADKAR states (via pulse surveys or manager ratings) and outcomes (adoption, proficiency, performance). Reassess barrier points by segment monthly. Adjust interventions (e.g., more manager coaching if Desire lags; redesign workflow if Ability lags).

  9. Embed ADKAR into program governance

    Include ADKAR metrics in steering reviews. Make a leader accountable for sponsor effectiveness, manager coaching, training quality, and reinforcement mechanisms. Tie executive bonuses partially to adoption/proficiency where appropriate.

6. Example: ADKAR in Action

Context: A $1.0B industrial services company rolled out a mobile field-service platform to 1,200 technicians across 8 regions. Prior attempts faltered—paper workarounds persisted, data quality lagged, and billing cycle times remained high.

Approach: The COO mandated a relaunch using ADKAR, integrated with an agile delivery plan.

  • Assessment: Baseline heat map showed:
    • Technicians: moderate Awareness, low Desire (“tracking my work” concerns), low Knowledge, low Ability.
    • Supervisors: high Awareness, mixed Desire (fear of productivity dips), moderate Knowledge, low Ability to coach.
    • Billing: high Awareness/Desire; low Knowledge of new data flows.
  • Targeted plan:
    • Awareness: Sponsor videos linking delays to customer complaints and cash; field ride-alongs by the COO.
    • Desire: “What’s in it for me” sessions for techs (less paperwork, faster pay, fewer callbacks); small bonus tied to first 60 days of accurate digital jobs; peer champions recruited.
    • Knowledge: Hands-on role-based training; 2-hour “day in the life” simulations; laminated job aids on vans.
    • Ability: Floor-walker SMEs in each depot for 4 weeks; workload reduced 10% during ramp; UX tweaks prioritized via a 48-hour defect SLA.
    • Reinforcement: Leaderboards for digital completion rates; weekly recognition; updated KPIs for supervisors; old paper forms removed after week 6 with escalation exceptions only.

Outcomes (16 weeks): Digital completion reached 95% (from 52%), first-time data accuracy improved by 18 points, billing cycle time dropped 23%, and technician satisfaction rose 9 points. Reinforcement (new KPIs, paper retirement, ongoing coaching) kept adherence above 93% three months post-ramp. The company reused the ADKAR playbook to deploy predictive maintenance features.

7. Strengths and Limitations

Strengths

  • Simple and actionable: Five plain-language states make it easy to diagnose and plan interventions.
  • Human-centered: Focuses leadership attention on the real adoption levers—sponsorship, manager coaching, motivation, practice, and reinforcement.
  • Segmentable and measurable: Works at persona/role level; enables heat maps and targeted plans rather than one-size-fits-all communications.
  • Complementary: Fits neatly with program governance, agile delivery, and benefits tracking; pairs well with Kotter and Lewin.

Limitations

  • Not a program plan: ADKAR doesn’t replace project management, operating model design, or process engineering; it complements them.
  • Risk of linearity: In practice, elements overlap; treating ADKAR as lockstep can delay action (e.g., useful to start early Ability pilots).
  • Surface scoring: Self-reports can be biased; triangulate with behavioral data (usage, error rates) and manager observation.
  • Limited structural guidance: ADKAR won’t tell you how to redesign incentives or governance—leaders must do that work.

8. Common Pitfalls (and How to Avoid Them)

  • Jumping to training (Knowledge) when Desire is low

    What goes wrong: People attend but don’t adopt; workarounds persist.

    How to avoid: Build Desire first through manager coaching, involvement in design/pilots, and aligned incentives; address real loss concerns.

  • Assuming “we told them” equals Awareness

    What goes wrong: One broadcast message doesn’t land; myths fill the gap.

    How to avoid: Communicate repeatedly via trusted senders (executives for “why,” managers for “what it means to me”); allow Q&A and listen.

  • Measuring attendance, not proficiency (Ability)

    What goes wrong: Go-live chaos; error rates spike.

    How to avoid: Include practice, job aids, and coaching; track on-the-job proficiency and remove friction fast.

  • Weak reinforcement

    What goes wrong: Backsliding to old tools and habits.

    How to avoid: Change KPIs/incentives, decommission legacy tools, set audit routines, and recognize adopters; make the new way the path of least resistance.

  • Ignoring middle managers

    What goes wrong: The “frozen middle” quietly slows adoption.

    How to avoid: Equip and hold managers accountable for coaching and reinforcement; include them in solution design.

  • One-size-fits-all messaging

    What goes wrong: Messages miss concerns; Desire remains low in key groups.

    How to avoid: Segment by role/persona; tailor “WIIFM,” training, and reinforcement tactically.

  • Trying to manufacture Desire where losses are real

    What goes wrong: Cynicism; active resistance.

    How to avoid: Pair honest messaging with mitigation: reskilling, fair transitions, and support; involve affected employees in shaping the path.

9. How the ADKAR Model Relates to Other Frameworks

  • Lewin Three-Stage (Unfreeze–Change–Refreeze): ADKAR operationalizes the human journey within each phase—Awareness/Desire during Unfreeze; Knowledge/Ability in Change; Reinforcement in Refreeze.
  • Kotter 8 Steps: Kotter structures the leadership and program arc (urgency, coalition, wins, anchoring). ADKAR addresses individual adoption states within that arc and supplies targeted tactics.
  • Bridges’ Transition Model: Bridges maps the psychological transitions (Ending–Neutral Zone–New Beginning). Use it to tune ADKAR communications and coaching to emotions at each stage.
  • McKinsey Influence Model: ADKAR aligns with the four building blocks (role modeling, understanding & conviction, skills, and reinforcing mechanisms).
  • Agile/Lean: Agile delivers iteratively; ADKAR ensures each release has adoption support (Awareness/Desire before release, Knowledge/Ability at release, Reinforcement post-release).
  • McKinsey 7‑S / Operating Model: Reinforcement is stronger when Structure, Systems, Staff, Skills, Style, and Shared Values are aligned with the new behaviors.

10. Key Takeaways

  • ADKAR focuses on the individual journey through change: Awareness, Desire, Knowledge, Ability, Reinforcement.
  • Find and fix the barrier point by stakeholder segment; piling on training won’t overcome low Desire or structural friction.
  • Pair ADKAR with robust program management, sponsor action, manager coaching, and operating model changes.
  • Design reinforcement early—KPIs, incentives, leader routines, and decommissioning of old tools to prevent backsliding.
  • Use ADKAR with Lewin/Kotter/Agile to connect leadership, delivery, and human adoption into one coherent change system.

11. FAQs About the Prosci ADKAR Model

How is ADKAR different from Kotter’s 8 Steps?
Kotter provides an organization-level leadership roadmap (urgency, coalition, vision, wins, anchoring). ADKAR focuses on the individual adoption states. Use Kotter to structure the program; use ADKAR to diagnose and drive adoption in each stakeholder group.

How do we measure ADKAR?
Use short surveys or manager ratings (1–5) for each element by segment, triangulated with behavioral data (e.g., system usage, error rates, proficiency). Visualize results in a heat map to locate barrier points; track movement monthly.

Can ADKAR work in agile environments?
Yes. Run mini ADKAR cycles per release: build Awareness/Desire in sprint reviews and stakeholder comms; deliver Knowledge/Ability with just-in-time training and coaching; put Reinforcement in post-release KPIs and retrospectives. Keep sponsor and manager routines active throughout.

Who “owns” ADKAR in a transformation?
The executive sponsor is accountable; line managers are the primary creators of Desire and Ability through coaching; change practitioners coordinate ADKAR assessments and plans; project teams deliver enabling solutions. It’s a shared system, not a PMO-only activity.

How long does it take to move through ADKAR?
It varies by scope and audience. For a targeted process/system change, Awareness/Desire can build in weeks; Knowledge/Ability typically ramps over 4–12 weeks around go-live; Reinforcement must run for quarters to ensure stickiness. Sequence elements, but allow overlap and iteration.

What if some groups face real losses—can we still build Desire?
Be transparent about impacts; provide reskilling, fair transitions, and voice in shaping the path. Align incentives with the new way and emphasize customer and company outcomes. Desire doesn’t mean universal enthusiasm, but sufficient willingness to engage when treated fairly and supported.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]