ADKAR Change Management Model

1. What Is ADKAR Change Management Model?

The ADKAR Change Management Model is a practical, individual-centered framework for driving adoption and behavior change. ADKAR is an acronym that captures the five outcomes a person needs to achieve for change to stick:

• A — Awareness of the need for change
• D — Desire to participate and support the change
• K — Knowledge of how to change
• A — Ability to implement required skills and behaviors
• R — Reinforcement to sustain the change

In plain terms: organizations don’t change—people do. ADKAR ensures each impacted person understands why change is necessary, wants it, knows what to do, can do it, and keeps doing it. The model gives leaders and change teams a focused way to diagnose adoption risks, target interventions, and measure progress at the human level.

Executives and consultants use ADKAR to increase the ROI of transformations—ERP/CRM/cloud rollouts, pricing and policy shifts, operating-model redesigns—by turning abstract change goals into specific, trackable adoption outcomes.

2. Origin and Background

ADKAR was developed by Jeff Hiatt, founder of Prosci, and published in the early 2000s (notably in “ADKAR: A Model for Change in Business, Government and our Community,” 2006). It emerged from research on hundreds of projects to understand why some changes succeed and others fail.

Why it emerged: classic change guidance often focused on organizational steps (vision, urgency, coalitions) but struggled to translate to the individual adoption journey. ADKAR filled that gap by defining the minimum outcomes required in each person’s head and hands. It sits at the intersection of project/change management—linking program milestones to human adoption.

ADKAR became widely known through Prosci’s practitioner community, training, and toolkits, and is now a staple in corporate change playbooks and consulting practices.

3. How ADKAR Works

ADKAR is both a diagnostic and a design model. It clarifies what successful adoption requires—and where to act when it’s at risk. The five elements are sequential in logic but often progress in parallel for different individuals and groups.

Awareness (of the need for change)

• People need to understand the “why”: market forces, customer expectations, risk/compliance imperatives, performance gaps, and the cost of inaction.
• Effective tactics: change story, external benchmarks, customer/employee voice, storytelling from trusted leaders; transparency about risks of the status quo.

Desire (to participate and support)

• Awareness doesn’t automatically create willingness. Desire is shaped by personal motivations: WIIFM (“what’s in it for me”), peer norms, incentives, job security, and trust in leadership.
• Effective tactics: credible sponsors, manager engagement, role-based “why it matters,” incentives and recognition, addressing fears and perceived losses.

Knowledge (how to change)

• People must know what is expected: new processes, tools, policies, and skills—at the right level of depth and timing.
• Effective tactics: https://umbrex.com/services/organization/change-management/training-and-adoption-planning/, job aids, sandbox environments, FAQs, office hours, coaching; integrate learning into workflow (not just events).

Ability (to implement the change)

• Knowledge ≠ performance. Ability requires practice, feedback, capacity, systems support, and removal of practical barriers.
• Effective tactics: hands-on practice, shadowing, performance support tools, reconfigured processes, time protection, access to experts; fix “plumbing” (access, permissions, data quality).

Reinforcement (to sustain)

• Even well-adopted changes backslide without reinforcement. People need ongoing cues, rewards, and consequences that align with the new way.
• Effective tactics: KPIs and dashboards, recognition, coaching, governance reviews, refresher training, integrating new behaviors into performance and talent systems.

In practice, you assess where each stakeholder group is along ADKAR, address the first gap (e.g., low Desire → don’t jump to training), and move groups through the elements. The model scales—from 1:1 coaching (“What does this person need next?”) to enterprise programs (“Which persona is stuck at Desire?”).

4. When to Use the ADKAR Model

Most helpful for:

• Technology-enabled change: ERP/CRM/cloud, data governance, cybersecurity, AI augmentation—where adoption is the value driver.
• Policy/process shifts: pricing and discounting rules, risk/compliance procedures, service playbooks.
• Operating-model changes: agile ways of working, shared services, sales coverage realignment.

Especially powerful when:

• Programs are well scoped but adoption is lagging (“the system works; people aren’t using it”).
• You need a measurable adoption plan that line-managers and change agents can execute.

Less effective or potentially misleading when:

• Used as a checklist divorced from the specific change context or without strong sponsorship and economics.
• Applied only as communications/training while ignoring structural barriers (roles, incentives, capacity, system performance).
• Confused with an organizational change roadmap—ADKAR operates at the individual level; pair it with program governance and portfolio management.

Practice today: High-performing teams run ADKAR in tandem with program management (scope, budget, milestones) and operating-model change (decision rights, incentives). They segment stakeholders, quantify ADKAR baselines, and adjust interventions sprint by sprint.

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

1. Define the change and value at stake

   Write a crisp statement of the change (what, who, when) and the economics (revenue, cost, risk, customer impact). Clarify non-negotiables (compliance, safety) and adoption KPIs (e.g., % users active, error rate, cycle time).

2. Segment stakeholders and build personas

   Group impacted people by role, geography, seniority, and exposure (e.g., sales reps, sales managers, pricing analysts, finance controllers). Create 3–6 personas that capture goals, pains, incentives, and likely ADKAR gaps.

3. Assess current ADKAR state

   For each persona, score A–D–K–A–R on a simple 1–5 scale using interviews, pulse surveys, sponsor/manager input, and behavioral data (e.g., pilot usage). Identify the first failing link—the earliest element scoring below threshold (e.g., ≤3).

4. Design targeted interventions per element

   For each persona, craft interventions that close the first failing link, then the next:

   • Awareness: compelling change story, customer evidence, scenario risk; sponsor videos; peer testimonials.
   • Desire: WIIFM messaging, incentives, recognition, manager 1:1s, addressing specific loss aversion.
   • Knowledge: role-based training, job aids, simulations; plan training waves against cutover dates.
   • Ability: on-the-job coaching, super-user networks, help desk capacity, system performance fixes.
   • Reinforcement: KPIs in scorecards, ongoing recognition, refresher modules, governance reviews.

   Map owners, timelines, and success measures; integrate with program plan.

5. Mobilize sponsors and people leaders

   Effective change lives or dies with visible sponsorship and front-line manager engagement. Identify primary sponsors; equip them with a cadence (visible acts, communications). Train managers to hold ADKAR-aligned conversations and coach Ability on the job.

6. Enable the ecosystem (remove barriers)

   Fix structural blockers: decision rights (RAPID), execution roles (RASCI), incentives, capacity (time protection), system access/permissions, data quality, and process design. Don’t ask people to do the impossible.

7. Run sprints and measure

   Operate in 2–4 week cycles. Track ADKAR scores by persona, adoption KPIs (active use, completion, error rates), and sentiment. Use dashboards to identify where to pivot interventions. Celebrate short-term wins tied to Reinforcement.

8. Anchor and scale

   Integrate new behaviors into hiring, onboarding, performance, and rewards. Codify playbooks and communities of practice. Keep Reinforcement visible for 6–12 months to prevent snap-back; plan refreshers at key moments (e.g., release cycles).

6. Example: ADKAR in Action

Context: “NorthStar Insurance,” a $4.5B multiline insurer, launched a new underwriting platform and analytics-driven appetite guidelines. A prior attempt failed—agents avoided the tool; underwriters reverted to spreadsheets. Leadership set a 9-month push to achieve 85% digital quote-to-bind and reduce average turnaround time by 30%.

Approach

• Define & segment: Personas included field agents, underwriters, underwriting assistants, and regional managers. Adoption KPIs: % submissions in platform, straight-through processing rate, cycle time, and loss ratio impact in two pilot lines.
• Assess ADKAR (baseline): Agents scored low Awareness/Desire (“another tool, more clicks”); underwriters scored Knowledge moderate (trained before) but Ability low due to real-world data hurdles; managers had high Awareness but Reinforcement missing in their scorecards.
• Interventions:
  • Awareness/Desire: Customer story (broker churn due to slow quotes), competitor benchmark, and a “less rework” WIIFM; regional leaders did roadshows; small pilot bonuses for digital submissions.
  • Knowledge: Role-based microlearning modules; 30-minute “task to task” videos; searchable job aids; office hours with product SMEs.
  • Ability: “War room” to fix data mapping and permissions; super-user network in each region; on-the-job coaching with shadowing for first 10 cases; simplified appetite rules in UI; time protection in peak weeks.
  • Reinforcement: Added digital adoption and cycle-time KPIs to manager scorecards; monthly recognition for top-adopting teams; quarterly business reviews included platform metrics; small spiffs for agents hitting digital thresholds.
• Sponsorship: COO and Chief Underwriting Officer were visible sponsors; regional managers held weekly huddles; change agents embedded in underwriting teams.

Outcomes (6 months)

• Digital quote-to-bind rose from 41% to 79%; cycle time reduced by 27% (target 30% by month 9); straight-through processing up 18 pts in pilot lines; early loss ratio moved favorably vs. prior year.
• ADKAR scores improved: agents moved from 2.4/5 to 4.1 on Awareness/Desire; underwriter Ability rose from 2.8 to 4.0 after system fixes and coaching.
• Backsliding mitigated: Reinforcement via metrics and recognition sustained adoption; release updates packaged with refresher microlearning.

Why it worked: the team treated adoption as the product—diagnosed the first failing link for each persona, fixed system frictions (Ability), and made Reinforcement unavoidable through KPIs and recognition.

7. Strengths and Limitations

Strengths

• Simple and actionable: Provides a clear checklist of outcomes per person; easy to explain to sponsors and managers.
• Diagnostic power: Identifies the first failing link—you don’t waste time on training when Desire or Ability is the issue.
• Measurable: Supports baselining and tracking of adoption progress and targeted interventions.
• Scalable: Works 1:1 (coaching) and enterprise-wide (persona-based plans) across functions and geographies.

Limitations

• Individual focus: Must be paired with organizational levers (governance, incentives, decision rights) and delivery excellence.
• Checklist risk: Treating ADKAR as a communication/training plan without addressing structural barriers leads to superficial adoption.
• Subjectivity: ADKAR scoring can be qualitative; requires triangulation (surveys, behavioral data, manager input).
• Time and attention: Sponsorship and manager coaching are essential—underinvesting here undermines Desire/Ability.

8. Common Pitfalls (and How to Avoid Them)

• Jumping to training (Knowledge) too soon
  What goes wrong: Desire is low; training attendance is high but adoption is low.
  How to avoid: Diagnose first failing link; build Awareness/Desire with a credible story, WIIFM, and sponsor engagement before training.
• Confusing Knowledge with Ability
  What goes wrong: People know what to do but can’t do it due to system access/data/performance or lack of practice.
  How to avoid: Provide hands-on practice, fix “plumbing,” create super-users, and protect time to build muscle memory.
• Ignoring manager role
  What goes wrong: Sponsors broadcast; front-line managers are passive; adoption stalls.
  How to avoid: Equip managers with scripts, coaching guides, and KPIs; hold them accountable for team ADKAR outcomes.
• Underpowered reinforcement
  What goes wrong: Early adoption fades; people revert to old ways.
  How to avoid: Bake behaviors into KPIs, reviews, and rewards; maintain cadence of recognition and refreshers for 6–12 months.
• One-size-fits-all messaging
  What goes wrong: Diverse personas hear generic messages; Desire doesn’t move.
  How to avoid: Segment and tailor communications by role and incentive; use credible messengers (peers, customers).
• Not removing structural barriers
  What goes wrong: People want to change but processes and systems block them.
  How to avoid: Pair ADKAR with RAPID/RASCI, process redesign, incentives, and IT fixes; don’t assign heroic workarounds.

9. How ADKAR Relates to Other Frameworks

• Kotter’s Eight Steps: Kotter focuses on the organizational flow of change (urgency → coalition → vision → wins → culture). ADKAR focuses on the individual adoption journey. Use Kotter to architect the program; use ADKAR to drive person-level adoption.
• Stakeholder Mapping / Influence Maps: Identify who matters and who influences whom; ADKAR clarifies what each needs next (A/D/K/A/R) and which messengers move them.
• RAPID / RASCI: Clarify decision rights and execution roles—critical for Ability and Reinforcement (barriers and accountability).
• Decision Quality Chain: Ensures the change strategy itself is a high-quality decision; ADKAR ensures people can and will execute it.
• Agile / OODA / OKRs: Provide cadence and measurable outcomes for sprints; ADKAR interventions can be planned and tested in agile increments.
• Behavioral economics / Nudges: Complement Desire and Reinforcement through defaults, prompts, and friction reduction.

10. Key Takeaways

• ADKAR defines five outcomes—Awareness, Desire, Knowledge, Ability, Reinforcement—that each person needs for change to stick.
• Diagnose the first failing link by persona and target interventions accordingly; don’t jump to training if Desire or Ability is the constraint.
• Successful adoption requires visible sponsorship, manager coaching, and structural enablers (governance, incentives, system fixes).
• Measure adoption with ADKAR scores and behavioral KPIs; run sprints and celebrate short-term wins to build momentum.
• Use ADKAR alongside Kotter (organization), RAPID/RASCI (governance), and stakeholder/influence tools to turn strategy into sustained behavior change.

11. FAQs About ADKAR Change Management Model

How is ADKAR different from Kotter’s model?
Kotter orchestrates organizational change (urgency, coalition, vision, wins, culture). ADKAR operates at the individual level—what each person needs to adopt the change. They are complementary: Kotter for the program, ADKAR for adoption.

How do we measure ADKAR?
Use short surveys and interviews to score each element (1–5) by persona, triangulated with behavioral data (usage, completion, error rates). Track the earliest weak element and define interventions and thresholds to move it above target.

How long does an ADKAR effort take?
It aligns to your change timeline. For a 6–9 month rollout, expect 2–4 week ADKAR sprints (assess → intervene → measure) per persona, with Reinforcement extending 6–12 months post go‑live.

Can small organizations use ADKAR?
Yes. Keep it lightweight: 2–3 personas, simple 1–5 scoring, targeted interventions (sponsor messages, role-based training, super-users), and a basic dashboard of adoption KPIs.

What tools are required?
Spreadsheets and survey forms suffice to start. Larger programs benefit from change management platforms, LMS content, analytics dashboards, and collaboration tools. The discipline matters more than the tooling.

What if Desire remains low despite communications?
Communications alone rarely move Desire. Engage direct managers, adjust incentives and WIIFM, address perceived losses, and enlist credible peers/customers. Remove friction so the new way is easier than the old.

How do we sustain change after go‑live?
Bake Reinforcement into KPIs, reviews, recognition, and governance. Maintain super-user communities, schedule refreshers aligned to release cycles, and monitor adoption metrics; act quickly on backsliding.

Does ADKAR apply to non-technology changes?
Absolutely. Policy and process changes, culture shifts, and operating-model moves all require individuals to understand, want, know, do, and sustain new behaviors.

Who “owns” ADKAR in a program?
Sponsors and line leaders own outcomes; change leaders orchestrate assessments and interventions; managers coach at the front line. Everyone has a role: ADKAR is a shared responsibility to make change real.