Cloud concept · Updated

ADKAR Model - The ADKAR Model is Prosci’s individual change-management framework for building Awareness, Desire, Knowledge, Ability, and Reinforcement to sustain organizational change.

In short

ADKAR helps leaders identify why people are struggling with a change and select interventions that address the actual barrier. For enterprise AI adoption, it connects communication, employee involvement, practical training, supported experimentation, and ongoing reinforcement rather than treating deployment or course completion as evidence of readiness.

Cloud Concepts Hub →

6 key aspects of ADKAR Model

ADKAR connects five individual change outcomes with targeted leadership actions that help employees adopt and sustain new ways of working.

01
Awareness of the need for change

Explain the business problem, why change is needed now, and what it means for each affected role. Use concrete workflow examples and acknowledge AI limitations instead of relying on broad transformation messages.

02
Desire to participate

Address employee motivations and concerns through involvement, credible sponsorship, transparent role discussions, and aligned incentives. Treat resistance as information to investigate rather than proof that employees need more training.

03
Knowledge of how to change

Provide role-specific instruction on tools, approved workflows, responsible AI practices, and escalation paths. Teach employees when not to use AI as well as how to use it.

04
Ability to perform

Provide access, protected practice time, coaching, and realistic exercises so employees can apply their knowledge. Assess demonstrated task performance rather than equating course completion with operational competence.

05
Reinforcement of new behaviors

Sustain adoption through manager follow-up, recognition, updated procedures, and balanced outcome measures. Reward safe, effective behavior and honest reporting rather than raw usage.

06
Barrier-focused leadership interventions

Identify the earliest unmet ADKAR outcome for an affected person or group and tailor support accordingly. For example, use bounded experiments to address risk concerns and blameless learning reviews to reduce fear of failure.

Cloud services for ADKAR Model

These services support the technical conditions for an ADKAR-informed AI rollout rather than implementing the model itself. Amazon Bedrock provides a platform for approved AI exercises and pilots, IAM limits access to appropriate resources, and CloudWatch supplies operational evidence for review. Leaders combine those capabilities with clear communication, employee participation, coaching, and recognition. A practical rollout starts with a bounded workflow, gives participants suitable access and practice time, and reviews quality and risk outcomes alongside employee feedback before expanding adoption.

Amazon Bedrock

Amazon Bedrock can support controlled generative AI pilots and hands-on exercises that build Knowledge and Ability. Application-level human review and configured safeguards can help define experimentation boundaries, but the service does not implement ADKAR or resolve cultural resistance.

Amazon CloudWatchAmazon CloudWatch

CloudWatch can collect application metrics and logs that support pilot reviews and ongoing operational feedback. Teams must instrument meaningful measures and combine telemetry with employee feedback; activity counts alone do not demonstrate willingness, competence, or business value.

ADKAR Model exam questions

Real practice exam questions on ADKAR Model, with the correct answer and its explanation. Answer them with every option in the exam simulator.

AIB-C01 (beta)

A financial services company introduces an AI-assisted document review workflow. Employees understand why the change is needed, helped design the workflow, and demonstrated correct output verification and escalation during a supervised pilot. Adoption was initially high but declined after employees returned to their regular teams. Interviews reveal that supervisors still reward the number of documents completed and treat time spent investigating questionable AI outputs as poor productivity. Employees now avoid the AI workflow because following its verification requirements could hurt their performance ratings. Which leadership intervention should be prioritized to sustain adoption?

Show answerCORRECT ANSWER

Align supervisor scorecards with verified review quality and appropriate escalation, and recognize employees who consistently follow the approved workflow.

This addresses the missing reinforcement in the ADKAR model. Employees initially adopted the workflow and demonstrated competence, but existing rewards undermine sustained use. Aligning performance measures and recognition with responsible AI behaviors supports continued adoption without weakening verification requirements.

Practice ADKAR Model in a full exam

Questions on ADKAR Model in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is ADKAR Model

2 min read

The ADKAR Model describes five outcomes individuals need to adopt and sustain a change: Awareness of the need for change, Desire to participate and support it, Knowledge of how to change, Ability to demonstrate the required skills and behaviors, and Reinforcement to sustain the change. Developed by Prosci, it focuses on the people side of transformation. An enterprise can deploy a cloud AI platform successfully while employees continue using old workflows because one or more of these outcomes is missing.

Awareness requires a credible explanation of why the organization is changing. For an AI-assisted support workflow, leaders should explain the business problem, expected improvements, limitations, and consequences of doing nothing. A general announcement that AI is strategically important is insufficient. Employees need to understand what will change in their own work, which decisions remain with people, and how customer data will be protected.

Desire concerns willingness to participate, not simply understanding the announcement. Resistance may reflect concerns about job security, workload, professional identity, unreliable outputs, or unfair performance evaluation. Leaders should invite affected employees into workflow design, explain likely role changes honestly, provide reskilling opportunities, and resolve conflicting incentives. More technical training rarely fixes a lack of trust or a belief that adopting AI will threaten someone’s career.

Knowledge covers what employees must learn, including approved use cases, data-handling rules, prompt techniques, output verification, and escalation procedures. Ability is different: people must demonstrate those skills under realistic working conditions. Engineers might understand retrieval-augmented generation in a classroom yet still need supervised practice to diagnose unsupported answers or configure access correctly. Protected learning time, coaching, accessible tools, and representative exercises help turn knowledge into performance.

Cultural barriers require targeted leadership interventions. Risk aversion can be addressed through bounded pilots, explicit approval criteria, least-privilege access, and clear accountability. Fear of failure calls for psychological safety: leaders should distinguish good-faith experimentation within approved boundaries from negligent behavior and use blameless reviews to extract lessons. Resistance to change often requires listening, employee participation, and visible action on legitimate concerns rather than labeling employees as difficult.

Reinforcement makes the new behavior sustainable. Managers should recognize responsible use, incorporate validated practices into operating procedures, provide ongoing coaching, and review whether the change improves business outcomes. For example, an AI support pilot should measure resolution quality, rework, and appropriate escalation alongside usage. Rewarding prompt volume alone can encourage unnecessary use or discourage employees from reporting errors.

ADKAR is useful as a diagnostic framework, not a rigid project schedule or a substitute for technical governance. Outcomes generally build on one another, but teams may revisit earlier needs as tools, roles, or risks change. Interviews, practical assessments, and workflow observations add context that telemetry cannot provide. The trade-off is that individualized support takes time and leadership attention; a uniform rollout is simpler but can overlook very different barriers across teams. Cloud controls can enable safe practice, but no service creates employee willingness or trust automatically.

Learn ADKAR Model in lessons

1 short lesson on ADKAR Model in 1 certification course.

Open the lessons