HealthITPrep
CPHIMS guide Concepts Features Pricing FAQ
Sign in Start free
العربية

Lewin vs Kotter: models for leading change

By Adel Moustafa, CPHIMS® · Updated 22 October 2026

How a hospital moves people to a new system or a new way of working: Lewin's three stages, Kotter's eight steps, ADKAR for the individual, and the adoption curve that says who follows when.

In short: Lewin describes change in three stages: unfreeze (create the readiness to change), change (move to the new way) and refreeze (make it the norm). Kotter breaks the same journey into eight steps for leaders, starting with a sense of urgency and a guiding coalition and ending with anchoring the change in the culture. Both are about people, not technology: a new EHR succeeds when clinicians change how they work, not when the software is installed.
Why a model Lewin Kotter Side by side ADKAR Adoption curve Common mistakes Summary Sources

Why do health IT projects need a change model?

Many failed system projects did not fail on the technology. They failed because people kept the old workarounds, did not trust the new screens, or were never told why the change mattered. A change model gives leaders an order of work: what must happen before go-live, at go-live and after it, so that the new way is still used a year later. In this sense, organisational change management is about people; the change enablement of IT service management, which controls changes to systems, is a different subject.

What are Lewin's three stages?

  1. Unfreeze: loosen the current habits by showing why they cannot stay: data on errors or delays, a regulation, a patient story. People need a reason before they accept the cost of learning something new.
  2. Change (moving): the transition itself: training, support at the elbow, new procedures, help with problems as they appear. Productivity often drops for a while in this stage.
  3. Refreeze: make the new way stable: update policies and job descriptions, remove the old forms and the old system's access, measure and recognise use, so people do not slide back.

Lewin also gave force field analysis: list the driving forces that push towards the change and the restraining forces that hold it back. Change happens when the drivers are stronger, and reducing a restraining force (for example fear of slower documentation, answered with extra support) often works better than pushing harder.

What are Kotter's eight steps?

  1. Create a sense of urgency: help people see why change is needed now.
  2. Build a guiding coalition: a group with enough authority, expertise and credibility to lead it, including respected clinicians.
  3. Form a strategic vision (1996: develop a vision and strategy): a clear picture of the future that people can explain in a few sentences.
  4. Communicate the vision, and in the later version of the model, enlist a volunteer army: many people who want to help, not only a project team.
  5. Enable action by removing barriers (1996: empower broad-based action): systems, structures or habits that stop people acting on the vision.
  6. Generate short-term wins: visible results early, such as one unit live and showing fewer errors, to keep support.
  7. Sustain acceleration (1996: consolidate gains and produce more change): use the credibility of the wins to change more, and do not declare victory too soon.
  8. Institute change (1996: anchor new approaches in the culture): anchor the new way in the culture, so it no longer depends on the people who led it.

Kotter first set out the steps in Leading Change (1996). In 2014 he renamed several of them and presented them as "accelerators" that run at the same time and keep going, alongside the normal hierarchy, rather than strictly one after another; the order of the list is the same.

Lewin and Kotter side by side

Lewin's stageKotter's stepsIn a new EHR project
Unfreeze1. Urgency, 2. Guiding coalition, 3. Vision, 4. Communicate and enlistShow the errors and delays of the paper process; a physician and nurse champion lead with the CIO
Change5. Remove barriers, 6. Short-term wins, 7. Sustain accelerationTraining and support at go-live, fixing order sets that slow clinicians, a pilot unit's results shared, then roll-out to the other units
Refreeze8. Institute changeRetire paper forms, build use into policies and performance reviews

The mapping is approximate, but it helps: Lewin says what has to happen, Kotter gives leaders a more detailed order of work.

How does ADKAR differ?

ADKAR, from the company Prosci, looks at change one person at a time: Awareness of the need, Desire to take part, Knowledge of how, Ability to do it in practice, and Reinforcement to keep it. It is useful for finding where a particular person or group is stuck: training (knowledge) does not help someone who still sees no reason for the change (awareness and desire).

What is the technology adoption curve?

Everett Rogers' diffusion of innovations divides the people who take up something new into five groups, in the order they adopt it:

  • Innovators (about 2.5%): try new things first, willing to take risks.
  • Early adopters (about 13.5%): respected opinion leaders; others watch them.
  • Early majority (about 34%): adopt once they see it works.
  • Late majority (about 34%): sceptical, adopt when most others already have.
  • Laggards (about 16%): the last, often tied to the old way.

In practice, early adopters make good super users and champions, because the majority follows people it respects more than it follows the project team.

What do candidates get wrong?

  • Starting with training. In Kotter the first step is urgency, and in Lewin unfreezing: people need a reason before they learn.
  • Building the coalition from IT only. A guiding coalition for a clinical change needs respected clinicians with authority.
  • Declaring victory at go-live. Go-live is the middle of the change, not the end; refreezing and anchoring come after.
  • Confusing organisational change management with ITIL change enablement. The first is about people adopting a new way of working; the second controls changes to IT services.
  • Treating resistance as stubbornness. In force field analysis it is a restraining force with causes, often fixable ones such as missing support or a slower screen.
  • Swapping early adopters and innovators. Early adopters are the opinion leaders others follow; innovators are the few who try anything first.

Summary for revision

  • Lewin: unfreeze, change, refreeze; force field analysis of driving and restraining forces.
  • Kotter: urgency, coalition, vision, communicate and enlist, remove barriers, short-term wins, sustain, institute.
  • ADKAR: awareness, desire, knowledge, ability, reinforcement, for each person.
  • Adoption curve: innovators, early adopters (opinion leaders, good super users), early majority, late majority, laggards.
  • People, not software: go-live is the middle of the change; anchoring comes after.

Sources

  • Lewin K., "Frontiers in Group Dynamics", Human Relations (1947): the three stages and force field analysis.
  • Kotter J.P., Leading Change (1996), and Accelerate (2014): the eight steps and their later wording.
  • Rogers E.M., Diffusion of Innovations, 5th edition (2003): the adopter categories.
  • Prosci: the ADKAR model.

Related free practice questions

  • Kotter’s model for leading change
  • The segments of the adoption curve and their nicknames

The site files this concept under the domain Management and Leadership.

Try exam-style questions

A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.

Start the trial exam

Questions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?

Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance

The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership

Written by Adel Moustafa, About us

Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.

CPHIMS guide Compare certifications Free practice questions Concepts explained About us Terms of Use Privacy Policy Refund Policy Contact us

© 2026 HealthITPrep. This site is not affiliated with or endorsed by HIMSS. CPHIMS is a registered trademark of HIMSS.