ADKAR Model: 5 Stages to Make Digital Transformation Stick

The article opens with a familiar scenario: a transformation review meeting where training materials, videos, and 100% attendance look perfect on paper, yet the team lead senses people will quietly revert to old methods. A colleague sketches the ADKAR model — a five-stage framework developed by Prosci founder Jeff Hiatt after studying hundreds of organizations — arguing that most teams only deliver the Knowledge stage (manuals, training) while neglecting Awareness, Desire, Ability, and Reinforcement.

The ADKAR Five Stages

A | Awareness : Understanding why change is necessary — the pain points, external risks, and cost of inaction.

D | Desire : Personal willingness to participate and support the change; driven by individual benefits (less rework, lower risk, fewer penalties).

K | Knowledge : Knowing the concrete steps, standards, rules, and boundaries — the "how-to".

A | Ability : Actually performing the new behavior in real scenarios, handling exceptions, and producing stable output.

R | Reinforcement : Sustaining the change through positive recognition and corrective oversight to prevent regression.

Prosci's benchmark research shows the biggest barrier to organizational change is not lack of ability but lack of awareness — people don't resist because they can't do it, but because they don't see why they must.

Sequence Is Fixed: Training Comes Third

Human change follows a fixed order: without Awareness there is no genuine Desire; without Desire, training is mere theater; without Ability, people revert when difficulties arise; without Reinforcement, short-term compliance collapses once pressure lifts. The article emphasizes that Desire is a "personal subjective choice" that cannot be mandated by policy or KPI. Command-driven compliance yields only surface conformity — behavior persists only while pressure exists.

Mapping ADKAR to Project Phases

The author maps the five letters onto a three-phase project timeline (a practical engineering adaptation, not Prosci's original wording):

1. Pre-launch: Solve "Why change? Why should I cooperate?"

Awareness: Communicate current pain points, industry risks, and the price of staying put — not corporate strategy.

Desire: Translate benefits to the individual level (WIIFM — What's In It For Me): reduced workload, lower risk, less rework, less blame.

Actions: Honest dialogue about problems, focus on frontline value, open Q&A to surface anxieties, incubate seed users who adopt early and create replicable patterns. Leadership support is critical as arbiters of cross-department conflict and direct influencers of teams.

2. During (Pilot): Solve "Understand it, learn it, use it reliably"

Distinguish Knowledge (theoretical steps, rules) from Ability (hands-on execution, exception handling, troubleshooting). The gap between "hearing" and "doing" requires extensive practice, coaching, and real-time correction.

Actions: Teach with real business scenarios; run small-scale pilots first; document pitfalls into standard Q&A assign dedicated coaches for on-site support and immediate course-correction; feed frontline bottlenecks back to simplify processes and tools.

The author shares personal experience coaching a project team daily, resolving employee questions and doubts late into the night, which deepened understanding of frontline realities.

3. Post-launch: Solve "No rebound, becomes habit, normalized"

Most transformations fail here: they manage the launch but not the reinforcement. Human nature favors the familiar; without reinforcement, inertia wins.

Reinforcement is two-way:

Positive: Timely recognition for those who follow new rules and deliver quality; deliver on promised value.

Negative: Regular reviews, spot checks, intervene when regression appears.

Establish correct business rules, periodic quality audits, and "lighthouse metrics" that reflect transformation health; address issues signaled by those metrics. A diagram illustrates two divergent curves three weeks post-launch: with reinforcement, adoption sustains; without, it collapses.

Diagnostic Guide: Pinpoint the Blockage from One Line of Feedback

Frontline quote: "Another change? Not necessary." → Stuck at: A Awareness → Countermeasure: Don't talk strategy; talk pain, risk, cost of no change.

Frontline quote: "Agree verbally, but don't act." → Stuck at: D Desire → Countermeasure: Match personal benefits, give choice, provide positive incentives.

Frontline quote: "Want to, but don't know how to fill it." → Stuck at: K Knowledge → Countermeasure: Supply standards, boundaries, positive/negative examples, operation guides.

Frontline quote: "Know the process, but revert under deadline pressure." → Stuck at: A Ability → Countermeasure: Coaching practice, simplify tools, codify exception-handling paths.

Frontline quote: "Serious at first, then slack off and rebound." → Stuck at: R Reinforcement → Countermeasure: Restore review cadence, enforce rewards/penalties, normalize supervision.

The article concludes with a guiding principle: "Change driven by pressure vanishes instantly; change aligned with human nature endures." Real change management relies not on hype or rallies, but on locating the exact blockage, closing the gap, respecting psychology, and following the natural sequence.