Loading content
The ADKAR model is a practical change-management approach that defines five sequential elements required for successful change: Awareness (understanding the need for change), Desire (motivation to support and participate in the change), Knowledge (knowing how to change), Ability (being capable of implementing the change in daily work), and Reinforcement (sus…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
The ADKAR Model structures individual change as five sequential outcomes: awareness, desire, knowledge, ability, and reinforcement.
Jeff Hiatt developed the ADKAR Model at Prosci; its name groups five individual outcomes of successful change. Prosci established the approach as part of its change-management practice.
Treat change like a staircase: a person first understands the reason, then develops personal willingness. Knowledge shows the path, ability makes it workable day to day, and reinforcement prevents regression. A gap on one step slows the next ones.
Understanding the reason and consequences provides orientation.
Personal willingness makes participation more likely.
Knowledge explains the approach; practice and support turn it into action.
Feedback and visible confirmation stabilize new behavior.
ADKAR helps diagnose resistance and support needs in change initiatives. It focuses interventions on individual conditions; organizational structure, power, and culture require additional analysis.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.