ADKAR

1. What Is ADKAR?

ADKAR is a practical, outcome-oriented framework for managing the people side of change. It breaks successful adoption down into five sequential outcomes each individual must achieve for a change to stick:

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

In the Change & Transformation context of Project Management, ADKAR complements program plans and governance by making adoption measurable and manageable at the level where change actually happens—one person at a time. It provides leaders and change teams with a common language to diagnose barriers, sequence interventions, and track progress toward true adoption (not just deployment).

Consultants and executives widely use ADKAR to structure communications, training, coaching, and reinforcement activities for transformations, technology rollouts, process changes, and culture shifts. It is deliberately simple, which makes it portable across industries and types of change.

2. Origin and Background

ADKAR was developed by Jeff Hiatt at Prosci in the late 1990s and popularized through Prosci’s research, training, and publications. The model is central to Prosci’s approach to change management and was codified in Jeff Hiatt’s 2006 book “ADKAR: A Model for Change in Business, Government and our Community.”

It was created to address a practical challenge: project teams often delivered “on time and on budget,” yet benefits failed to materialize because people didn’t adopt the new ways of working. ADKAR reframed change success around individual outcomes and offered a simple diagnostic that sponsors and managers could use to remove adoption barriers.

ADKAR became widely known via practitioner benchmarking studies, certification programs, and its straightforward, memorable structure, which made it attractive to organizations seeking a common, non-technical method for the human side of change.

3. How ADKAR Works

The logic is straightforward: organizational change succeeds only when enough individuals make and sustain the personal changes required. ADKAR specifies the outcomes each person must achieve, in sequence. If one is missing, adoption stalls; the model then guides targeted interventions to close the gap.

The five ADKAR outcomes

• Awareness (of the need for change): People understand why the change is necessary now, the risks of not changing, and how it aligns with strategy and customers. Without genuine awareness, communications feel like noise.
• Desire (to participate and support): Individuals choose to engage. This is shaped by personal motivators, the credibility of leaders, peer influence, and perceived impacts. Desire cannot be mandated, but it can be cultivated.
• Knowledge (of how to change): People know what is changing for them, the skills and behaviors required, and where to go for help—through training, job aids, and process clarity.
• Ability (to implement required skills and behaviors): Beyond knowing, individuals can perform in real conditions. This requires practice, coaching, feedback, removal of local barriers, and often time to reach proficiency.
• Reinforcement (to sustain): Mechanisms ensure the change sticks—recognition, metrics tied to the new way, leadership attention, and consequences that make the preferred behavior the easy and expected behavior.

Sequencing and diagnosis

• ADKAR is sequential for the individual: you cannot substitute training (Knowledge) for missing Desire. Diagnose which outcome is the constraint and focus there before pushing downstream activities.
• At the group or enterprise level, people will be at different stages. You run multiple ADKAR activities in parallel, tuned to where each segment is on the journey.

Roles and enablers

• Sponsors: Visible, active sponsorship is the single biggest predictor of success. Sponsors create Awareness and influence Desire through vision, resources, and credibility.
• People managers: They translate the change locally, coach to Ability, and reinforce through everyday management. ADKAR gives managers a pragmatic script.
• Change and project teams: They design communications, training, coaching plans, and reinforcement mechanisms; they monitor ADKAR health and adjust.

Typical artefacts

• Change impact assessment (who is affected, how, and when)
• ADKAR baseline and pulse surveys by stakeholder segment
• Sponsor roadmap and people manager coaching plan
• Training plan and performance support (playbooks, job aids)
• Reinforcement plan tied to metrics, recognition, and incentives

4. When to Use ADKAR

Especially powerful when:

• You are implementing new technology, processes, or ways of working where benefits depend on behavior change (e.g., CRM, ERP, agile adoption, shared services, pricing discipline).
• Transformations need measurable adoption, not just deployment—e.g., mandate without buy-in has previously failed.
• Sponsors and managers need a simple, shared language to lead change without specialist jargon.

Applicable contexts: All industries and sizes—corporates, public sector, mid-market, and high-growth firms. ADKAR works for enterprise-wide programs and targeted changes within functions or sites. It is also effective in healthcare, financial services, manufacturing, and education where role-based changes are concrete.

Less suitable or potentially misleading when:

• The change is purely technical with negligible behavior impact; basic rollout checklists may suffice.
• Leaders seek a “communications-and-training” veneer without real sponsorship or removal of structural barriers.
• Teams treat ADKAR as a rigid sequence rather than an outcomes-based diagnostic; the result is activity without adoption.

Time and data requirements: A first cycle of ADKAR planning typically takes 3–6 weeks alongside project planning (impacts, baseline assessments, sponsor/manager plans, training design). Ongoing pulse checks (monthly or at gate reviews) guide course corrections. Data can be light-touch—surveys, manager feedback, adoption metrics, and usage analytics for digital tools.

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

1. Define the change and who is affected

   Clarify the case for change, desired outcomes, and what will be different for each role. Produce a change impact assessment: who, what, when, and how much (process, tools, behaviors). This becomes the backbone for all ADKAR activities.

2. Segment stakeholders and baseline ADKAR

   Group stakeholders by role, location, business unit, or influence. Use surveys, interviews, and manager input to assess where each segment stands on Awareness, Desire, Knowledge, Ability, and Reinforcement. Identify the binding constraint for each segment.

3. Build the sponsor roadmap (Awareness and Desire)

   Identify primary sponsors and a guiding coalition. Plan visible actions: town halls, site visits, storytelling, resource commitments, and issue unblocking. Equip sponsors with talking points that connect the change to strategy, customers, and risks of inaction.

4. Design communications to create genuine Awareness

   Craft concise messages tailored to each segment: why now, what is changing, what stays the same, and what it means for them. Use multiple channels and two-way forums (Q&A, listening sessions). Repeat and refresh messages as milestones are hit.

5. Cultivate Desire with personal motivators and manager engagement

   Map “what’s in it for me/us” by segment. Equip people managers to hold one-on-one conversations that address personal concerns, career implications, and local benefits. Identify and address sources of resistance early (workload spikes, perceived loss of control, incentive misalignments).

6. Design training and performance support for Knowledge

   Define the specific skills and process knowledge required by role. Build targeted training (hands-on, scenario-based) and provide job aids (checklists, quick-reference guides, embedded help). Time training close to when people will use the skills.

7. Enable Ability through practice, coaching, and barrier removal

   Plan for on-the-job practice, floor-walking support, peer champions, and manager coaching. Remove local obstacles (access, data, tools), and adjust workload or targets during ramp-up. Use simulations or pilots to build confidence before full cutover.

8. Establish Reinforcement mechanisms

   Align metrics, recognition, and consequences with the new way of working. Update performance goals, scorecards, and incentives. Celebrate early adopters and teams that model the change. Hold leaders accountable for sustaining behaviors.

9. Integrate ADKAR with the project plan and governance

   Embed ADKAR activities and checkpoints in the project schedule and stage-gates. Report adoption and proficiency alongside cost/schedule. Use issue escalation to remove barriers within 48–72 hours.

10. Measure adoption and iterate

    Track leading and lagging indicators: training completion and proficiency, system usage and adherence, process cycle times, quality metrics, and business outcomes. Reassess ADKAR stages monthly; adjust communications, coaching, or reinforcement to address new constraints.

6. Example: ADKAR in Action

Context: A $1.2B regional health insurer implemented a new claims platform to reduce cycle time and error rates. Past system rollouts had met technical deadlines but missed benefits due to low adoption and workarounds. The program affected 1,400 claims processors across four sites.

Application: The team began with a role-based impact assessment (assessors, auditors, team leads) and baseline ADKAR surveys. Results showed solid Awareness (“why”) but weak Desire in two sites due to concerns about productivity targets during transition. The COO and site directors launched a sponsor roadmap: site visits, explicit workload relief during ramp-up, and a commitment to adjust productivity metrics for 60 days post-go-live.

Communications emphasized customer impact (faster, more accurate claims) and job quality (less rework). Training combined sandbox practice with scenario labs by claim type. Peer champions provided floor support for the first four weeks. Managers ran weekly coaching huddles to address issues and share tips.

Reinforcement: Scorecards were updated to include quality adherence to the new process, not just speed. Leaders recognized teams publicly for defect reductions and customer compliments. Persistent workarounds were escalated and resolved within 72 hours.

Outcomes: Within eight weeks, system adoption reached 93% (target 90%); rework fell 28%, and average processing time improved by 17%. The two initially skeptical sites closed the Desire gap after managers received additional coaching resources and temporary relief on productivity quotas. Benefits sustained over six months as reinforcement mechanisms remained in place.

7. Strengths and Limitations

Strengths

• Simple and actionable: Clear outcomes make it easy for sponsors, managers, and teams to understand and apply.
• Diagnostic power: Quickly pinpoints where adoption is stuck (e.g., Desire vs Knowledge) so interventions are targeted.
• Role clarity: Highlights the critical roles of sponsors and people managers, not just the change team.
• Scalable: Works for enterprise transformations and local changes; integrates with program governance.
• Measurable adoption: Encourages tracking of adoption and proficiency, not just completion of activities.

Limitations

• Perceived linearity: If treated as a rigid sequence, it can be misapplied in fast-moving or iterative contexts.
• Narrow scope: Focuses on individual adoption; does not replace organizational design, portfolio decisions, or technical delivery plans.
• Measurement subjectivity: Survey-based assessments can be biased; triangulation with behavioral data is needed.
• Over-index on comms/training: Without real sponsorship and barrier removal, ADKAR activities become theater.

8. Common Pitfalls (and How to Avoid Them)

• Jumping straight to training

  What goes wrong: Knowledge increases but adoption doesn’t because Awareness/Desire are weak. Avoid: Start with a sponsor-led case for change; measure and address Desire before rolling out training at scale.

• Treating Desire as mass communication

  What goes wrong: People feel talked at, not convinced. Avoid: Use people managers for one-on-one conversations, address personal motivators, and fix local irritants that fuel resistance.

• Underpowered sponsorship

  What goes wrong: Mixed signals and slow decisions stall momentum. Avoid: Build a credible sponsor coalition with visible behaviors, rapid issue resolution, and aligned messages.

• Ignoring workload and performance targets during ramp-up

  What goes wrong: Ability suffers; people revert to old ways to hit metrics. Avoid: Temporarily adjust productivity targets; provide on-the-job support and time for practice.

• One-size-fits-all messaging and training

  What goes wrong: Irrelevant content breeds cynicism. Avoid: Tailor by role and site; use scenarios and job aids that match real work.

• No reinforcement

  What goes wrong: Adoption decays after go-live. Avoid: Update metrics, recognize desired behaviors, and maintain sponsor visibility beyond launch.

• Over-surveying without acting

  What goes wrong: Feedback fatigue; trust erodes. Avoid: Keep pulse checks short, share results, and act visibly on insights.

• Failing to integrate with project governance

  What goes wrong: Adoption risks surface too late. Avoid: Include ADKAR checkpoints in gates and dashboards; track adoption alongside cost/schedule.

9. How ADKAR Relates to Other Frameworks

• Kotter’s 8-Step Model: Kotter focuses on mobilizing the organization—urgency, coalitions, vision, and momentum. Use Kotter for enterprise mobilization and ADKAR to manage individual adoption within that journey.
• Lewin’s Unfreeze–Change–Refreeze: A high-level arc. ADKAR operationalizes it by defining the concrete outcomes people need to progress through those stages.
• Bridges’ Transition Model: Emphasizes the psychological transition (endings, neutral zone, new beginnings). Pair with ADKAR to address emotional responses and identity alongside skills and behaviors.
• Enterprise PMO (EPMO) and Project Portfolio Management (PPM): EPMO/PPM handle prioritization, funding, and delivery. ADKAR ensures initiatives achieve adoption and benefits realization.
• Agile and Lean Portfolio Management: Agile provides iterative delivery; ADKAR aligns communications, coaching, and reinforcement to sprint and PI cadences to accelerate adoption.
• Balanced Scorecard/OKRs: Translate strategy into objectives and measures. ADKAR connects those objectives to the individual behaviors and skills required to hit them.
• Prosci’s broader methodology: ADKAR sits within a larger process (e.g., preparing, managing, and sustaining change). Organizations often adopt the model with or without the full methodology, depending on maturity.

Choice guidance: Use strategy and operating-model frameworks to design the destination; use EPMO/PPM to fund and deliver; use Kotter to mobilize; use ADKAR to ensure people adopt and sustain the new ways of working.

10. Key Takeaways

• ADKAR defines the five outcomes individuals need for change to stick: Awareness, Desire, Knowledge, Ability, Reinforcement.
• Use it as a diagnostic and sequencing tool: fix the binding constraint before moving downstream.
• Sponsors and people managers are pivotal; ADKAR gives them a practical script and cadence.
• Integrate ADKAR with program governance; measure adoption and proficiency, not just activity.
• Beware “comms-and-training” theater; without Desire, Ability, and Reinforcement, adoption will stall or decay.

11. FAQs About ADKAR

Is ADKAR still relevant in agile, fast-moving environments?
Yes. Treat the five outcomes as a continuous, iterative loop. Align communications, coaching, and reinforcement to sprint/PI rhythms, and use pulse checks to adjust quickly by segment.

How does ADKAR differ from Kotter’s 8 steps?
Kotter focuses on mobilizing the organization—urgency, coalition, vision, wins, and institutionalization. ADKAR focuses on what each person needs to adopt the change. They are complementary and often used together.

Can small or early-stage companies use ADKAR?
Absolutely. Keep it light: a concise case for change, manager-led conversations to build Desire, short role-based training, on-the-job coaching, and simple reinforcement (metrics and recognition).

How long does it take to apply ADKAR on a project?
Expect 3–6 weeks to design ADKAR plans alongside project planning, with ongoing activities through go-live and stabilization (typically 8–12 weeks post-launch) and periodic reinforcement thereafter.

How do we measure Desire, which seems subjective?
Triangulate short pulse surveys with behavioral signals: attendance at optional sessions, early opt-in to pilots, usage patterns post-go-live, and manager-reported sentiment. Act on concerns quickly to convert fence-sitters.