Change management / transformation
Kotter's 8-Step Change Model
John Kotter’s sequence for leading large-scale change: build urgency, form a guiding coalition, create and communicate a vision, empower action, generate short-term wins, consolidate, and anchor the change in culture.
Its core claim: transformations fail not from bad strategy but from skipped steps.
- Problem
- Change management / transformation
- Altitude
- Enterprise
- Effort to run
- Moderate
- Evidence base
- Established
Theory & origin
Kotter published the model in Leading Change (1996), distilled from a study of over 100 transformation efforts — most of which failed. His diagnosis was sequence errors: declaring victory early, communicating the vision once instead of hundredfold, or launching change without real urgency. The eight steps are deliberately ordered; each builds the condition the next one assumes. Critics note it is top-down and linear where real change loops, and Kotter himself later reframed it as concurrent "accelerators" — but as a diagnostic for why a change is stalling, the original sequence remains the sharpest tool in the drawer.
Explore the model
How a consultant runs it
- 01 Diagnose before prescribing: score the change against all eight steps and find the earliest one that was skipped — that is usually where the stall lives.
- 02 Test urgency honestly: count what leaders do differently, not what the kickoff deck said.
- 03 Audit the coalition for real power — a steering committee of delegates is step 2 failed.
- 04 Engineer a visible win inside 90 days and spend it publicly; wins are the fuel for the long middle.
- 05 Do not close the programme until the behaviour survives without it — anchoring (step 8) is where most "successful" changes quietly die.
When to use
- 01 Diagnosing why a large transformation is stalling — locate the skipped step
- 02 Planning a change with real behavioural stakes: ERP, operating model, merger integration
- 03 Coaching a sponsor who thinks a kickoff and a comms plan constitute change management
When not to use
- 01 Small, reversible changes where the ceremony outweighs the risk
- 02 As a strictly linear checklist — real change loops between steps; use it as a diagnostic, not a Gantt chart
- 03 Bottom-up or emergent change, where imposing a top-down sequence smothers what is already working
Worked example
An ERP rollout is 9 months in and stalling: training complete, adoption at 30%. Scoring the eight steps finds step 1 and step 5 failed — no one below director level believes the old system is going away, and warehouse incentives still reward throughput measured in the legacy tool. The fix is not more training: the CFO announces a legacy shutdown date (urgency), incentives are re-based on the new system’s numbers (empowerment), and one distribution centre goes fully live as the engineered win. Adoption hits 85% in two quarters.
Common pitfalls
- 01 Declaring victory at go-live — Kotter’s original failure case — and watching the change roll back within a year
- 02 Vision by committee: a paragraph of abstractions nobody can repeat, let alone act on
- 03 Skipping urgency because the executive team feels it — the shop floor does not
- 04 Running all eight steps as a communications campaign while systems and incentives still reward the old behaviour
Sample deliverable
One real engagement, end to end — watch the numbers travel from raw input, onto the chart, into the artifact.
Input — raw data
- Urgency (felt below director)1.8 / 5
- Coalition power3.6 / 5
- Vision clarity3.1 / 5
- Empowerment (incentives)1.6 / 5
- Short-term wins2.2 / 5
Process — mapped
Interviews score each step 1-5; the earliest weak step is where the change is stalling
Change-readiness scan — core-banking migration
- Stallsteps 1 & 5, not training
- Fixshutdown date + re-based incentives
- Engineered winone DC live in 90 days