Topic
Kotter 8-step change model
Weak Weak
John Kotter's eight steps, from Leading Change (1996), derived from studying change efforts that failed. Each step corresponds to a common failure.
Evidence: Weak. Derived from practitioner observation of roughly 100 change efforts, with no control group, no published method, and no subsequent test of the model as a whole. Individual steps have independent support — short-term wins map onto goal setting and progress research, and removing barriers maps onto force field logic — but the sequence, the count, and the causal claims are assertions. Use it as a completeness checklist.
Use when: leading a large, top-down, organization-wide change with executive sponsorship.
Do not use when: the change is local, emergent, or bottom-up, or when the organization is in the Complex domain and the answer is genuinely unknown. See cynefin-framework.
The eight steps
Create a sense of urgency. Not anxiety, and not a manufactured crisis — a genuine, evidenced case that the status quo is riskier than change. Kotter's claim: over half of transformations fail here.
Build a guiding coalition. A group with position power, expertise, credibility, and leadership. Not a steering committee of delegates. If the people on it send substitutes, you do not have a coalition.
Form a strategic vision and initiatives. A picture of the future that can be explained in five minutes and provokes interest, plus the concrete moves that get there.
Enlist a volunteer army. Communicate relentlessly and enable people to opt in. Kotter's later work emphasizes volunteers over conscripts.
Enable action by removing barriers. Structures, skills, systems, and managers that block the vision. This is where most programs quietly stop, because the barriers are usually owned by senior people.
Generate short-term wins. Visible, unambiguous, clearly related to the change, within 6–18 months. Wins convert skeptics and starve the "this too shall pass" narrative.
Sustain acceleration. Use credibility from wins to tackle bigger structures. Kotter's most-cited warning: do not declare victory early.
Institute change. Anchor the new approaches in culture, hiring, promotion, and succession — otherwise the next leader reverses it.
Later refinements
- Dual operating system: Kotter's Accelerate (2014) argues the hierarchy is good at running things and bad at changing things, so a second, network- like structure of volunteers should run in parallel, with people in both.
- Steps are increasingly presented as concurrent rather than strictly sequential.
Examples by audience
Health care: step 5 is the crux. Clinicians usually agree with the vision and are blocked by rotas, estate, IT access, and job planning. Removing those barriers is unglamorous and is the whole job.
Software: step 6 maps naturally to shipping something real. Pick a win the engineers themselves would brag about, not a milestone that only appears in a program report.
Executive: steps 1 and 8 are the executive's non-delegable work. Urgency cannot be delegated to a communications team, and anchoring cannot be delegated to HR — it happens through who gets promoted.
Limitations
- Evidence base is weak: derived from practitioner observation, rarely tested as a whole. See evidence-based-practice.
- Strongly top-down; treats employees as an audience to be enlisted rather than co-designers. Contrast action-research.
- Assumes the leadership knows the right answer, which is false in complex domains.
- Encourages "we did step 4" theater. The steps are outcomes, not activities: urgency is a state of the organization, not a launch event.