ADKAR Change Management Model: How to Apply It to Software Rollouts

ADKAR is the most widely used change management model for software rollouts. Here's how it actually works in practice, which tools support each stage, and the common mistakes teams make applying it.

What ADKAR is and why it fits software rollouts

The ADKAR model, developed by Prosci, is a structured framework for managing change in organizations, consisting of five sequential stages: Awareness, Desire, Knowledge, Ability, and Reinforcement. Each letter represents a milestone that an individual must achieve to successfully adopt new behaviors. If any of these stages are skipped, the rollout is at risk of failure. This model is particularly effective for software rollouts because the adoption of software is fundamentally about changing individual behaviors rather than altering an organization's overall stance. For example, a Salesforce migration's success hinges on whether each sales rep updates opportunities correctly. Similarly, an ERP rollout depends on finance analysts executing the right transactions. ADKAR provides a roadmap for reaching these outcomes.

The following sections detail how each stage is applied in software rollouts, the tools that facilitate each phase, such as training videos, in-app guidance, and documentation, and the pitfalls teams often encounter during execution.

Applying ADKAR to software rollouts

A: Awareness

Creating awareness involves informing employees about the impending change and its rationale. This stage is primarily about communication: kickoff announcements, town halls, FAQ pages, and intranet posts are typical methods. A common mistake is over-investing in awareness at the beginning and neglecting it later on, resulting in employees forgetting crucial information when they actually need it. To combat this, maintain a consistent flow of updates throughout the rollout.

Tools: Platforms like Staffbase and Firstup, along with your organization's intranet, are valuable for disseminating information at scale and keeping employees informed.

D: Desire

For change to be effective, employees must have the desire to participate, or at least not actively resist the transition. This desire can be cultivated by clearly communicating the personal benefits of the change, such as easier workflows, enhanced tools, and potential career advancements. Conversely, employees should also understand the cost of not changing, such as the old system becoming obsolete or shifting performance expectations. Balancing these messages is key to fostering genuine interest and reducing resistance.

Tools: Surveys, town halls, and manager one-on-ones are useful for gauging employee sentiment and encouraging engagement. These tools also provide a platform for addressing concerns and reinforcing the benefits of the change.

K: Knowledge

Knowledge is about equipping employees with the necessary skills and understanding to use the new system effectively. This is where training and content development come into play. Pre-launch training sessions, role-specific learning paths, and accessible reference materials are essential components of this stage. Unfortunately, many rollouts fail by not investing enough in quality training, resulting in generic adoption of the software.

Tools: Trupeer's content creation capabilities, along with Learning Management Systems (LMS) for tracking progress, and platforms like Whatfix or WalkMe for in-app guidance, are instrumental in delivering targeted and effective training.

A: Ability

While knowledge is theoretical, ability is practical; it involves employees actually performing tasks within the new system. To develop ability, provide opportunities for sandbox practice, shadow work, and graduated responsibility. This stage is often overlooked, despite being a significant source of post-launch chaos when skipped. Ensuring employees can confidently execute their duties in the new environment is crucial for a smooth transition.

Tools: Sandbox environments, practice scenarios, and in-app guardrails are essential for hands-on learning and building confidence in new processes.

R: Reinforcement

Reinforcement ensures that new behaviors become ingrained over time. A minimum of six months of reinforcement activities is recommended, including ongoing content updates, manager coaching, performance evaluations, and recognition of achievements. Many rollouts make the mistake of ceasing reinforcement efforts shortly after go-live, leading to a gradual return to old habits. Consistent reinforcement sustains the momentum of change.

Tools: In-app guidance, manager scorecards, and regular content updates help maintain engagement and support continuous improvement.

Feature comparison: tools mapped to ADKAR stages

In-depth analysis: where ADKAR applications go wrong in practice

Stopping at Knowledge

One of the most prevalent failures in applying ADKAR is halting progress at the Knowledge stage. Often, teams create and deliver training, then prematurely declare success. However, Knowledge is merely the third stage in the process of five. The real adoption occurs during the Ability (practice) and Reinforcement (sustaining) stages. Training without practical application is mere theater, and practice without reinforcement is a fleeting event. Rollouts that focus solely on training often experience an adoption ceiling of 40-50%, leading executives to question the investment's value. To address this, allocate resources across all five stages, not just Knowledge.

Tools can enforce this discipline. A training library that's quick to produce and refresh, such as AI-generated video plus SOPs, makes ongoing reinforcement affordable. A Digital Adoption Platform (DAP) that offers real-time ability guardrails enables continuous practice. Without these supporting tools, teams default to focusing on the cheapest stage to produce: Knowledge content.

Ignoring Desire

The Desire stage often receives inadequate attention because it involves challenging conversations. "What's in it for me" requires honesty about the change. Some rollouts offer genuine benefits to employees, while others do not. Pretending otherwise erodes trust. Effective change leaders provide candid communication: "This will be harder for a quarter, then more efficient than the old system." Or: "This change is driven by compliance requirements." Genuine communication fosters buy-in, while spin breeds cynicism.

Underestimating Reinforcement duration

Reinforcement must extend for at least six months. Many rollouts plan for only 4-8 weeks of post-launch support before declaring the initiative complete. Old habits often resurface within a quarter. Successful rollouts plan and allocate budget for weekly reinforcement activities through month six and monthly thereafter through month twelve. Tools that make this feasible are those that generate content inexpensively: if producing a new training video takes an hour, you can release one weekly. If it requires a full sprint, you might only manage one per quarter.

Challenges applying ADKAR

Treating it as a checklist. The stages of ADKAR are not a linear checklist to tick off as each is completed. Instead, they overlap and cycle, necessitating ongoing attention to each stage rather than moving on prematurely.

Uneven investment. A common issue is pouring resources into the kickoff phase (Awareness) while underfunding critical areas like sandbox practice (Ability). This imbalance can hinder successful adoption.

One-time Reinforcement. Hosting a single all-hands meeting post-launch does not constitute reinforcement; it is merely a fleeting moment. True reinforcement is a sustained effort to cement new behaviors.

Skipping measurement. Effective application of ADKAR requires measuring progress at an individual employee level, not just assessing success at the rollout level.

Manager gap. Managers play a crucial role in fostering Desire and Reinforcement within their teams. Without proper training and engagement, these stages can falter, compromising the change effort.

Must-have elements

• Awareness campaign with clear messaging: Ensure that your communication strategy is clear, consistent, and ongoing to maintain awareness throughout the rollout.

• Honest Desire conversations with stakeholder groups: Engage in open dialogue about the impacts and benefits of the change to foster genuine buy-in.

• Role-specific Knowledge content before go-live: Tailor training materials to the specific needs of different roles to enhance relevance and effectiveness.

• Sandbox Ability practice: Provide practical, hands-on opportunities for employees to build confidence in using the new system before full implementation.

• 6-month Reinforcement plan: Design a comprehensive reinforcement strategy that extends for at least six months post-launch to solidify new behaviors.

• Manager enablement for Desire and Reinforcement: Equip managers with the skills and resources needed to support their teams through the change process effectively.

• Measurement per stage and per employee: Implement a system for tracking progress and performance at each stage and for each employee to ensure thorough evaluation and adjustment where necessary.

Use cases and personas

Healthcare EHR rollout: Dr. Aisha, CMIO, 8,500-employee hospital network

Dr. Aisha led the Epic rollout by explicitly mapping it to the ADKAR model. Awareness was raised through clinician town halls, while Desire was built by having physician advocates share honest pros and cons. Knowledge was imparted via Trupeer role-specific videos, and Ability was developed through four weeks of sandbox practice. Reinforcement was maintained with six months of physician office hours. As a result, post-launch productivity only dropped by 15%, compared to the industry average of 30-40%, and fully recovered within eight weeks.

Financial services CRM: Manish, Director of Change Management, 3,400-person wealth management firm

Manish applied the ADKAR model to a Salesforce migration. Knowledge content was developed using Trupeer, complete with SOPs for each advisor's workflow. Reinforcement was achieved through monthly content updates and manager coaching based on Salesforce data. Within 90 days, data quality metrics reached 89%, demonstrating effective adoption and integration.

Manufacturing ERP: Anne, CIO, 5,200-employee manufacturer

Anne used the ADKAR framework to guide the SAP migration, allocating 22% of the program budget proportionally across each stage. This strategic investment resulted in a six-month adoption rate of 81%. For more insights, refer to the change management plan guide for related frameworks and strategies.

Best practices

Invest across all five stages. Many organizations focus heavily on Knowledge, but true success comes from evenly distributing resources across Awareness, Desire, Knowledge, Ability, and Reinforcement.

Speak honestly in the Desire stage. Avoiding spin and maintaining transparency builds trust and encourages genuine buy-in from employees.

Budget for 6-month Reinforcement. Allocate sufficient resources for continuous reinforcement activities to ensure new behaviors become ingrained and habitual.

Train managers to own Desire and Reinforcement on their teams. Managers are critical in sustaining change, so equip them with the necessary tools and training to lead effectively.

Measure each stage. ADKAR becomes actionable when you quantify progress and outcomes at each stage, allowing for informed adjustments and targeted improvements.

Frequently asked questions

Is ADKAR better than Kotter?

The suitability of ADKAR versus Kotter's model depends on your organization's needs. ADKAR is more operational, focusing on individual behavior change, while Kotter's model is strategic, emphasizing broader organizational shifts. Many organizations find value in using both models in tandem to address different aspects of change management.

How do I measure ADKAR stages?

Measuring ADKAR stages involves using surveys tailored to each stage, linked to relevant business metrics. Prosci offers assessment tools that can help you evaluate progress effectively. Regular measurement allows for timely interventions and ensures that change initiatives remain on track.

Can ADKAR apply to small rollouts?

ADKAR is adaptable to rollouts of any size, including smaller initiatives. The fundamental stages remain the same, but the investment in each stage can be scaled according to the scope of the rollout. By adjusting the intensity and resources allocated, you can effectively apply ADKAR principles to a smaller scale project.

Does ADKAR work for DevOps / agile?

Yes, ADKAR can be applied to DevOps and agile environments with some adaptations. While the fundamental stages still apply, the cadence and execution may need to be adjusted to fit the faster-paced, iterative nature of these methodologies. Incorporating ADKAR into agile sprints can help manage change effectively within these frameworks.

What's the biggest ADKAR mistake?

The most significant mistake is treating ADKAR as a linear, bureaucratic process. In reality, the stages overlap and cycle back on each other in real-world rollouts. Recognizing this dynamic nature and being flexible in your approach can prevent stagnation and ensure a more successful change initiative.

Final word

ADKAR proves its value when teams commit to each of the five stages, measure success at each phase, and extend Reinforcement efforts beyond the initial go-live date. Many rollouts falter by stopping at the Knowledge stage and then question why adoption plateaus. With the right tools and a disciplined approach, executing all five stages is achievable. Organizations that dedicate themselves to this comprehensive process see adoption results that validate ADKAR's esteemed reputation.