Key Takeaways
Judge change by people's new behavior, not the project's completed tasks.
Change is personal before it is organizational. Hiatt's ADKAR model describes five outcomes people need to move through: understanding why change is needed, choosing to take part, learning how to change, demonstrating the new behavior, and sustaining it. These outcomes build on one another. A communication plan or training course is an activity, not proof that people have adopted the change.
The towel makes the sequence visible. A hotel program invited guests to reuse towels by explaining the environmental costs and giving them a simple way to signal their choice. Guests needed to understand the reason, decide to participate, and know what to do. The behavior was easy to perform, while guests and hotels benefited from the result. The practical test is not whether the project launched, but whether people can carry out the intended change.
The model's strongest move is changing the unit of analysis from project outputs to human behavior. That distinction is useful wherever leaders confuse activity with impact: a rollout can be on schedule while people quietly keep using the old process. The towel example also shows how design can make adoption easier by linking a reason to a clear action. Still, not every outcome rests with individual willingness. A person may understand, agree, and still be blocked by workload, tools, or authority. Treating adoption as a personal process works best when the surrounding system is examined too.
Find the first weak link before adding another change tactic.
Diagnose before prescribing. In ADKAR, the barrier point is the earliest weak outcome in the sequence. If people do not understand why a change is necessary, adding more training skips the actual problem. If they understand but do not want to participate, more explanations may not help. The model directs managers to investigate the first gap rather than respond to every difficulty with the same toolkit.
A public debate illustrates the distinction. Hiatt's 2005 discussion of Social Security reform rated public awareness of the funding challenge as high, while desire for substantial change was low. People could know a problem existed yet disagree about who should bear its costs. The practical lesson is to assess each group separately and ask where movement stops. Low scores are clues to investigate, not automatic proof of a single cause.
The barrier-point idea resembles fault diagnosis in engineering: repair the upstream failure before optimizing a downstream process. It discourages the familiar habit of answering every adoption problem with another email or course. Its value depends on honest listening, however. A survey score can identify where concern concentrates, but cannot by itself explain why. Employees may report low desire because of a credible objection, distrust, or fear of consequences. The assessment should open a conversation, not turn a complex human response into a label attached to a person.
Explain why the change matters before describing the shiny solution.
Lead with the reason. Awareness means understanding what is changing, why now, what happens if nothing changes, and how the change affects the person hearing about it. In a Prosci study of 411 organizations managing major change, participants most often named lack of awareness of the reason as a source of resistance. Yet sending a message is not the same as creating understanding. Trust in the sender, rumors, past failed initiatives, and people's attachment to current practices all shape what they hear.
Make the message fit its audience. Pineapple growers in Ghana were more receptive to crop standards when they learned that UK supermarkets required compliance and that following the standards could reduce costs. The relevant case was market access and profitability, not an abstract appeal to change. Senior leaders can explain business rationale; supervisors can translate its local and personal effects.
The distinction between sending information and producing awareness is unusually practical. It directs leaders to test what people understood rather than count how many announcements went out. Audience-specific explanations also respect the fact that the same change can carry different risks for different jobs. The warning about credibility matters: repeating a claim does not repair a history of broken promises. There is a further discipline implied here: if the rationale cannot withstand questions, communications cannot make a weak case persuasive. Clear explanation should invite scrutiny, not substitute for it.
Make the change worth choosing from each person's point of view.
Desire is a choice, not a memo. Whether someone supports a change depends on what the change means for them, the organization's history, their personal circumstances, and what motivates them. A new role may promise opportunity to one employee and threaten security to another. In one example, a vice president resisted a transfer because it added an hour to his commute and interfered with time he had committed to his son. The objection was not simply stubbornness; it exposed a real personal cost.
Find the concern before pushing harder. Managers can listen for objections, remove practical barriers where possible, involve employees in designing or testing the change, and align incentives with the new behavior. Existing performance measures can quietly reward the old way of working. Desire is not manufactured by one technique, and financial rewards will not resolve every conflict of values or circumstance.
This view makes resistance diagnostically useful: an objection can reveal a cost the design team has overlooked. It also guards against treating employees as interchangeable recipients of a rollout. Participation can create ownership, while fair incentives reduce the penalty for adopting a new method. A necessary caution is that meaningful choice varies with power. In a job, some changes are mandatory, even when a manager invites discussion. Honest leadership distinguishes where employees can influence the design from where they cannot, rather than presenting a constrained choice as full consent.
Keep leaders visibly committed, or the change reads as optional.
Sponsorship must stay present. The executive sponsor is expected to explain the business need, remain visibly involved, and build support among other leaders. A sponsor who appears at launch and then disappears can signal that the initiative has lost priority. Managers matter too: employees watch their direct supervisors for evidence about whether the change is real and how it affects daily work.
A coalition carries the message. Hiatt describes a manufacturing company where support varied sharply across departments. When managers were mapped by their support and ability to lead, many were indifferent or opposed. Employees often followed their local management chain. By contrast, in a government agency example, a senior executive used extended face-to-face sessions to hear objections and respond directly. The discussion shifted toward how managers could help their teams adopt the new direction. Sponsorship is a continuing behavior, not a title.
The coalition idea explains why a persuasive chief executive cannot compensate for a chain of managers who undermine the initiative in everyday decisions. Visible sponsorship aligns signals across levels and gives employees a reason to believe that the effort will endure. The agency example also shows that presence is more than charisma: leaders need to tolerate uncomfortable questions and respond to specific concerns. There is a limit, though. Strong sponsorship cannot make an unjustified change sound compelling. Leaders' credibility depends partly on whether their conduct matches the assurances they give.
Do not mistake course attendance for operational competence.
Knowing is not doing. Knowledge is the information and instruction needed to change; ability is demonstrated performance in the real setting. A network-equipment company trained salespeople to shift from pitching product features to building customer business cases. Within 90 days, about 20 percent had put at least part of the new approach into practice. Some lacked the analytical skills or confidence the work demanded. Attendance alone could not close those gaps.
Build learning around the work. Hiatt recommends practical training, job aids, peer forums, subject-matter experts, and one-on-one coaching. Practice should resemble real tasks, and training should be timed close enough to implementation that people can use what they learn. Supervisors can observe performance, distinguish a knowledge gap from a skill gap, and provide help. The required support may involve more time, better tools, or a different role, not another presentation.
Separating knowledge from ability prevents an organization from treating a completed course as a completed change. The 20 percent result is a reminder that training can expose a gap rather than solve it. Practice, coaching, and timely feedback bring the work itself into the learning process. The distinction also creates a fairer response to poor performance: first ask whether a person had a real opportunity to practice with suitable support. At the same time, support cannot guarantee that every person will attain every required skill within the available time.
Reward real progress until the new behavior survives without the project team.
Adoption can fade after launch. Reinforcement includes recognition, rewards, feedback, measurement, and accountability that help sustain a change. It is most useful when connected to actual progress and meaningful to the people involved. A personal acknowledgment from a direct supervisor may matter more than an impersonal prize. Measures and incentives also need to support the new behavior, or the organization may keep rewarding the old one.
A bank learned this the hard way. Its quality-improvement program began with executive support, a project team, training, and strong early participation. Once the team disbanded, the program was absorbed into routine training. Courses were canceled within a year, and interest collapsed. No durable accountability, measurement, or recognition had been established. The team had completed its implementation plan without making the change part of normal operations.
The bank example separates a successful launch from a sustainable practice. Project teams often create temporary energy, but the organization must decide who owns the behavior when the launch team leaves. Recognition helps only when it is fair and tied to meaningful contribution; indiscriminate rewards can erode trust. Accountability provides continuity, yet it can become mere compliance if people are measured on activity rather than useful results. Reinforcement is strongest when feedback detects problems early and gives teams a chance to correct the system, not just penalize individuals.
Use employee feedback to steer change, not merely certify a launch.
Treat the model as a working diagnostic. ADKAR can guide plans, coaching, and assessments during a change. Teams can ask employees about their understanding, willingness, preparation, ability to perform, and experience of support. Results can be separated by location, role, or department because groups may face different barriers. In one restructuring assessment, 51 percent of employees reported moderate-to-low awareness of why the change was needed, giving leaders a specific gap to address.
Keep testing the response. Messages can be checked through employee feedback, training through learning assessments, and adoption through performance data or audits. Supervisors can coach and report local obstacles; sponsors can address organization-wide concerns. The model's usefulness is its ability to focus a conversation. Hiatt closes with a manager who tried it while coaching a struggling employee and called afterward to say the conversation had helped.
A feedback loop makes the model more than a tidy planning diagram. It helps leaders discover that a message missed its audience, a process fails in an unusual case, or one department needs different support. Segmenting results also prevents a healthy average from concealing a struggling group. The manager's coaching story captures the framework's accessibility, but a successful conversation is not evidence that an entire organization has changed. Individual anecdotes should be paired with sustained measures of use, performance, and unintended effects.
Analysis
ADKAR's central contribution is not a novel catalogue of change activities. It is a way to connect activities to the human outcomes they are supposed to produce. Communication matters when it creates understanding; training matters when it builds usable knowledge; recognition matters when it helps preserve an adopted behavior. That outcome orientation gives leaders a practical defense against activity theater, where teams report meetings held and courses delivered while actual work remains unchanged.
The sequence is also a diagnostic discipline. If adoption stalls, leaders are encouraged to locate the earliest weak condition rather than default to their favorite intervention. This is intuitively powerful, especially in organizations where training is treated as a universal solvent. Yet real change is not always a clean staircase. People can learn something, discover an unexpected cost, and lose willingness; practice can reveal flaws in the proposed solution; feedback can change the rationale itself. The model is most useful when its sequence organizes inquiry, not when it becomes a rigid script.
Its individual focus has a corresponding risk. Describing change as a person's awareness, desire, and ability can make structural obstacles look like personal resistance. The book itself offers reminders that workload, incentives, time, resources, and management behavior shape adoption. Those conditions should be assessed alongside individual readiness. A person cannot exercise desire freely when choices are concealed, and cannot demonstrate ability when the tools or work design make success unlikely.
The strongest application is therefore both humane and operational. Ask what people understand, what they stand to lose or gain, what capability the work demands, and what organizational conditions sustain the new behavior. Then verify the answers with employees and performance evidence. ADKAR offers a memorable map, not proof that every change is wise or that every barrier has one cause. Its value comes from making the people side of implementation specific enough to discuss, test, and improve.
Review Summary
ADKAR receives mixed reviews, with an average rating of 3.85 out of 5. Readers appreciate its simple, practical approach to change management, finding it useful for both personal and organizational contexts. Many praise the clear framework and real-world examples. However, some criticize the book for being repetitive, outdated, and lacking depth. While some readers find it invaluable for understanding change processes, others feel it oversimplifies complex issues. The book is often recommended for beginners in change management but may be less useful for experienced practitioners.
People Also Read
Glossary
ADKAR
Individual change outcomesA model for understanding the outcomes people need to achieve for a change to take hold: Awareness of the need, Desire to participate, Knowledge of how, Ability to perform, and Reinforcement to sustain the change. The outcomes are presented in sequence and used to guide change activities and diagnose where progress is blocked.
Barrier point
First weak change outcomeThe earliest weak element in the ADKAR sequence for a person or group. It identifies where progress is currently blocked, so managers can address that gap before applying tactics aimed at later outcomes. For example, training is unlikely to resolve a change that employees do not understand or do not want to support.
Sponsorship coalition
Leaders aligned behind changeA group of leaders and managers who actively support a change and help communicate its purpose and importance throughout the organization. The coalition extends visible executive sponsorship through management levels, so employees receive consistent signals and local leaders do not quietly undermine adoption.
What’s in it for me (WIIFM)
Personal impact of changeA way of examining how a proposed change affects an individual. People consider whether it offers an opportunity or threat, how fairly it is applied, and what it means for their work and personal circumstances. Understanding this perspective helps managers explain the change in terms that matter to each person.
Burning platform
Urgent case for changeA highly urgent or compelling situation used to focus attention on why change is necessary. The approach can help people recognize a serious risk quickly, but repeated use can weaken its credibility if every initiative is presented as an emergency.
FAQ
1. What is "ADKAR: A Model for Change in Business, Government and our Community" by Jeffrey M. Hiatt about?
- Individual-Focused Change Model: The book introduces the ADKAR model, a framework for understanding and managing change at the individual level, which can then be scaled to organizations and communities.
- Five Key Elements: It outlines five essential building blocks for successful change: Awareness, Desire, Knowledge, Ability, and Reinforcement.
- Practical Application: The book provides real-world case studies, practical tactics, and tools for applying the ADKAR model in various settings, including business, government, and community initiatives.
- Bridging Theory and Practice: Hiatt integrates research findings and best practices to help leaders and managers minimize risks and increase the success rate of change initiatives.
2. Why should I read "ADKAR: A Model for Change in Business, Government and our Community" by Jeffrey M. Hiatt?
- Results-Oriented Framework: The ADKAR model is praised for being simple, actionable, and focused on achieving measurable results in change management.
- Addresses People Side of Change: The book emphasizes the often-overlooked human factors that determine the success or failure of change efforts.
- Applicable Across Contexts: Whether you’re a business leader, project manager, or community organizer, the model is robust and adaptable to various types and scales of change.
- Research-Backed Insights: Hiatt’s approach is grounded in extensive research with hundreds of organizations, making the advice credible and evidence-based.
3. What are the key takeaways from "ADKAR" by Jeffrey M. Hiatt?
- Change is Individual: Successful organizational change is rooted in facilitating change with one person at a time.
- Sequential Building Blocks: All five ADKAR elements—Awareness, Desire, Knowledge, Ability, and Reinforcement—must be achieved in order for change to be realized and sustained.
- Diagnosing Failure Points: The model helps identify "barrier points" where change initiatives stall, allowing targeted interventions.
- Role of Leadership: Active and visible sponsorship, effective communication, and manager involvement are critical to building support and overcoming resistance.
4. What is the ADKAR model as defined in Jeffrey M. Hiatt’s book?
- Acronym Explained: ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement—the five outcomes required for successful change.
- Awareness: Understanding the need for change and the risks of not changing.
- Desire: The personal choice and motivation to support and participate in the change.
- Knowledge: Knowing how to change, including skills, behaviors, and processes.
- Ability: Demonstrated capability to implement the change at the required performance level.
- Reinforcement: Actions and mechanisms that sustain the change and prevent regression.
5. How does the ADKAR model help diagnose and address failed change initiatives?
- Identifies Barrier Points: The model pinpoints which element (e.g., lack of awareness or desire) is weak or missing, causing the change to stall.
- Targeted Interventions: By assessing each ADKAR element, leaders can focus their efforts on the specific area that needs improvement.
- Prevents Common Pitfalls: It helps avoid the mistake of assuming that activities like training or communication alone will ensure change.
- Enables Course Correction: Ongoing assessment using ADKAR allows for real-time adjustments to change management strategies.
6. What are the main factors influencing each element of the ADKAR model in Jeffrey M. Hiatt’s approach?
- Awareness: Influenced by personal views of the current state, credibility of the sender, presence of rumors, and whether reasons for change are contestable.
- Desire: Shaped by the nature of the change, organizational context, personal situation, and intrinsic motivators.
- Knowledge: Dependent on current knowledge base, learning capacity, available resources, and access to required information.
- Ability: Affected by psychological and physical barriers, intellectual capability, time, and support resources.
- Reinforcement: Driven by meaningful recognition, association with accomplishment, absence of negative consequences, and accountability systems.
7. How can leaders and managers use the ADKAR model to lead successful change, according to Jeffrey M. Hiatt?
- Active Sponsorship: Leaders must be visible, engaged, and communicate the need for change consistently.
- Manager Involvement: Managers and supervisors play a key role in coaching, addressing resistance, and translating change into personal terms for employees.
- Tailored Communication: Messages should be audience-specific, using preferred senders and multiple channels.
- Ongoing Assessment: Regularly use ADKAR assessments to gauge progress and adjust tactics as needed.
8. What practical tactics does "ADKAR" by Jeffrey M. Hiatt recommend for building each element of the model?
- Awareness: Use targeted communications, executive sponsorship, manager coaching, and provide access to business information.
- Desire: Foster sponsorship coalitions, equip managers to manage resistance, engage employees early, and align incentives.
- Knowledge: Implement effective training, provide job aides, offer one-on-one coaching, and create user forums.
- Ability: Ensure supervisor involvement, access to experts, performance monitoring, and hands-on practice.
- Reinforcement: Celebrate successes, give meaningful rewards, gather feedback, conduct audits, and build accountability into operations.
9. How does "ADKAR" by Jeffrey M. Hiatt address resistance to change?
- Proactive Approach: Emphasizes anticipating and planning for resistance rather than reacting to it.
- Manager’s Role: Managers should listen to objections, remove obstacles, make personal appeals, and hold employees accountable.
- Assessment Tools: Use change and readiness assessments to identify potential resistance points before they become issues.
- Engagement and Ownership: Involving employees in the change process increases their desire to support and reduces resistance.
10. In what ways can the ADKAR model be applied beyond business, according to Jeffrey M. Hiatt?
- Government and Community Change: The model is used in public sector initiatives, such as environmental campaigns and disaster preparedness.
- Personal Change: Individuals can use ADKAR to guide personal development or life changes.
- Education and Training: Serves as a teaching tool for analyzing case studies and understanding the dynamics of change.
- Assessment and Planning: Functions as a diagnostic and planning tool for any change initiative, regardless of context.
11. What are some real-world case studies or examples used in "ADKAR" by Jeffrey M. Hiatt to illustrate the model?
- Hotel Towel Reuse Program: Demonstrates how awareness, desire, and knowledge were built to change guest behavior, leading to industry-wide adoption.
- Pineapple Growers in Ghana: Showcases the importance of awareness campaigns in driving agricultural change.
- Call Center Process Redesign: Contrasts two teams’ approaches, highlighting the necessity of addressing awareness and desire before training.
- Large-Scale Issues: Examines challenges in energy policy, Social Security reform, and health care reform through the ADKAR lens to identify why changes succeed or fail.
12. What are the best quotes from "ADKAR" by Jeffrey M. Hiatt and what do they mean?
- “The secret to successful change lies beyond the visible and busy activities that surround change. Successful change, at its core, is rooted in something much simpler: How to facilitate change with one person.”
- Emphasizes that real change happens at the individual level, not just through organizational activities.
- “Awareness is not achieved based on the messages sent, but rather how the messages are received and internalized by each person.”
- Highlights the importance of understanding the audience’s perspective in communication.
- “ADKAR is a results-oriented model that provides a framework for how change management tactics and techniques come together to produce change.”
- Underlines the model’s practical, outcome-focused nature.
- “Each element is a building block. All of the building blocks need to remain present in order for the change to be sustained.”
- Stresses the necessity of achieving all five ADKAR elements for lasting change.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.