Org, people & execution

Kotter's 8-Step Change Model

An eight-step sequence for leading major change, distilled from Kotter's study of why transformations fail: build urgency and a coalition, form and communicate a vision, empower action, generate short-term wins, consolidate gains and anchor the change in culture.

Also known as Kotter's eight-stage process, 8-Step Process for Leading Change, Kotter's change model. First set out by John P. Kotter in 1995; the primary source is cited in full below.

Format: Process / loop
Level: Corporate · Business unit
Best for: Plan execution
Decision stage: Plan · Execute
Difficulty: Intermediate
Time to apply: A day to assess a change effort against the eight steps; the programme the model structures runs for years, and Kotter's own cases span three to ten.

Plate · The model

The 8 steps of Kotter's 8-Step Change Model, worked in sequence.

The components

Establishing a sense of urgency

Examine market and competitive realities and confront complacency, until a critical mass of the organisation believes the status quo is more dangerous than the change. Kotter's rule of thumb is that roughly 75% of management must be genuinely convinced.

Signals of strength
Uncomfortable market and financial evidence is discussed candidly, not managed · A large majority of managers privately agree change is necessary · Urgency rests on facts people can check rather than on exhortation

Creating the guiding coalition

Assemble a group with enough position power, expertise, credibility and leadership to drive the change, and get it working as a team outside the normal hierarchy.

Signals of strength
The coalition includes respected sceptics, not only enthusiasts · Key line leaders are members, so the hierarchy cannot quietly block it · The group works as a team with shared commitment rather than as a steering committee

Developing a vision and strategy

Create a picture of the future that is imaginable, desirable and feasible, plus the strategy for getting there. Kotter's test: if you cannot communicate the vision in five minutes and get a reaction that signifies understanding and interest, this step is not finished.

Signals of strength
The vision survives the five-minute test · It guides real trade-offs, so people can use it to say no to things · Strategy connects the picture to concrete first moves

Communicating the change vision

Use every channel available, repeatedly, and have the coalition model the behaviour the vision requires. Kotter found most efforts under-communicate the vision by a factor of ten.

Signals of strength
The vision appears in routine forums, not only set-piece events · Leaders' visible behaviour is consistent with the message · People several layers down can restate the vision in their own words

Empowering employees for broad-based action

Remove the obstacles that stop people acting on the vision: blocking structures, misaligned systems and incentives, skill gaps, and managers who undercut the change.

Signals of strength
Systems and reward structures that contradict the vision are being changed · Training arrives before people are asked to work the new way · Obstructive managers are confronted rather than worked around

Generating short-term wins

Plan and create visible, unambiguous performance improvements within 12 to 24 months, and recognise the people who deliver them. Wins buy the credibility the longer haul requires.

Signals of strength
Wins are scheduled into plans rather than awaited · Improvements are measurable and clearly linked to the change effort · People who deliver wins are visibly rewarded

Consolidating gains and producing more change

Use the credibility from early wins to tackle the bigger systems, structures and policies that do not fit the vision, bringing in more people and keeping urgency up rather than declaring victory.

Signals of strength
Momentum is spent on harder problems, not celebrations · New projects and change agents are being added, not wound down · Nobody senior has announced that the transformation is complete

Anchoring new approaches in the culture

Root the new behaviours in shared norms and values: articulate how they produce success, and ensure recruitment, promotion and succession carry them forward. Change that lives only in one leadership generation dies with it.

Signals of strength
The link between new behaviours and better results is stated explicitly and often · Promotion criteria and succession plans reflect the new way of working · New joiners absorb the changed behaviour as simply how things are done

When it earns its keep

You are planning a transformation that will take years and touch how large numbers of people work, and you need a roadmap that can be communicated as easily as it can be followed.
A previous change effort stalled and you want to diagnose where. Kotter built the model from eight recurring failure points, so it doubles as a post-mortem instrument.
The change requires people to behave differently, and past experience says new systems and structures alone will not shift behaviour.
Senior leadership is genuinely committed and visible. The model is explicitly leadership-driven and assumes sponsors who will spend personal capital on it.

And when it doesn't

The change is small and contained. Running eight stages to move a team onto new expenses software is ceremony; a plan and some communication will do.
The organisation works through continuous, emergent change, for instance product teams iterating weekly. A linear programme model fits episodic transformation, and Kotter himself repositioned the steps for this reason in 2014.
There is no committed sponsor. Without leaders prepared to model the change, the first four steps cannot be done honestly, and starting anyway produces cynicism.
You need the change to land this month. The sequence front-loads coalition-building and communication that take real calendar time; a genuine emergency needs directive crisis management first.

III

How to run it

Before starting, gather the inputs the analysis depends on:

Honest evidence for the case for change: market, competitive and financial data strong enough to make urgency real rather than rhetorical.
A map of who holds power, expertise and credibility in the organisation, from which to build the guiding coalition.
Capacity to communicate repeatedly through many channels over months, including leaders willing to model the change visibly.
Authority to alter the systems, structures and incentives that will otherwise block action.
Baseline performance measures from which short-term wins can be demonstrated rather than asserted.

1
Diagnose against the eight errors
Kotter derived each step from a corresponding failure mode he observed across more than 100 transformations. Before designing the programme, assess which errors your organisation is most likely to commit; that is where the effort should concentrate.
2
Sequence deliberately
Kotter is explicit that skipping steps creates only an illusion of speed and that critical mistakes in any phase can have devastating impact. The early steps build the authority and energy the later steps spend.
3
Resource the first four steps properly
Most failed transformations underinvest in urgency, coalition, vision and communication because they feel like preamble. In Kotter's account they are half the work, and rushing them is the single most common cause of failure.
4
Engineer wins into the middle
Plan for visible, unambiguous performance improvements within 12 to 24 months. Wins are created, not hoped for, and without them the sceptics who joined reluctantly will drift back.
5
Guard against premature victory
Until new behaviours are rooted in shared norms and values, they are fragile. Kotter's cases suggest transformations take three to ten years; declaring victory at year two invites regression to exactly the state the effort began in.
6
Decide whether you need the 2014 restatement
In Accelerate (2014), Kotter reframed the eight steps as concurrent 'accelerators' run by a volunteer network operating alongside the management hierarchy, a dual operating system for organisations facing continuous strategic change. If your context is ongoing adaptation rather than a single transformation, run the steps that way rather than as a one-off sequence.

Reading the result

A staged change programme: an evidence-based case for urgency, a named coalition, a communicable vision, a barrier-removal plan, scheduled short-term wins, and an explicit path from early gains to cultural anchoring, plus a diagnosis of which failure mode most threatens this particular effort.

Progress at any step is capped by the weakest step before it. A communication problem at step four is usually a vision problem from step three wearing a disguise.
Treat the model as a diagnostic as much as a plan. When a live change effort stalls, walk backwards through the steps until you find the one that was skipped or faked.
If the organisation faces continuous rather than episodic change, read the steps through the 2014 Accelerate lens: concurrent accelerators run by a volunteer network alongside the hierarchy, not a one-way sequence.

A worked example

A regional building society moves branch services to digital

A UK mutual building society with around 40 branches has seen branch footfall fall by 60% in a decade while regulatory and property costs rise. The board wants the majority of routine transactions handled digitally within three years, without abandoning an ageing member base or triggering a staff revolt. The executive uses Kotter's eight steps to structure the programme.

Establishing a sense of urgency: The first attempt backfired: cost-per-transaction charts read to branch staff as a redundancy warning, and urgency curdled into fear. The effort was reframed around member-service evidence, including waiting-time data and defections of younger members to app-based competitors, presented branch by branch. Urgency became about protecting mutuality rather than cutting costs.
Creating the guiding coalition: The coalition paired the COO and IT director with the head of the branch network, a respected 30-year veteran and open sceptic, plus two admired branch managers and a member-panel representative. Recruiting the sceptic was the decisive move; his conversion carried more weight in branches than any executive communication.
Developing a vision and strategy: The vision settled as 'every member served in minutes, whichever door they choose': digital for the routine, branches refocused on advice and complex needs. It passed the five-minute test in staff pilots and, importantly, told branch staff what branches were for, which the cost story never had.
Communicating the change vision: Eighteen months of repetition: branch huddles, intranet, exec roadshows, and executives opening accounts through the app live on stage. The factor-of-ten rule proved real; surveys at month six showed most cashiers still believed the strategy was branch closure by stealth, and the drumbeat continued until that number moved.
Empowering employees for broad-based action: Cashier incentives that rewarded counter transactions were scrapped, since they directly punished the desired behaviour. Cashiers were retrained as digital coaches, and a mid-office system that made app registration take twenty minutes was replaced, an unglamorous fix that removed the biggest practical barrier.
Generating short-term wins: A five-branch pilot created digital coaching corners with dedicated staff time. Within six months, 40% of those branches' active members had adopted the app and satisfaction scores rose. The results, and the pilot staff, were showcased to the rest of the network, converting the wins into recruitment for the next wave.
Consolidating gains and producing more change: Pilot credibility funded the harder moves: full network rollout, renegotiated branch opening hours, and the start of a core-banking replacement nobody would have sanctioned in year one. Two branch consolidations were handled openly, using the service data, which spent some goodwill but preserved trust.
Anchoring new approaches in the culture: Job descriptions, induction and branch scorecards were rewritten around blended service, and digital adoption became a standing item at the AGM. The society treats this step as unfinished: under pressure, veteran staff still revert to doing the transaction for the member rather than coaching them through it.

The read. Three years on, 70% of routine transactions are digital and member satisfaction has held, and the honest reading is that the early steps did the work: reframing urgency and recruiting the sceptical branch head made everything downstream cheaper. The model's linearity was the main friction. When open banking shifted the target mid-programme, the society had to loop back to re-form the vision rather than proceed to the next step, which is precisely the adaptation Kotter's 2014 restatement concedes.

Pitfalls

Skipping or rushing the foundations. Kotter's central finding is that transformations fail early and quietly, in urgency, coalition and vision, long before the visible failure at execution.
Declaring victory too soon. Improvement at month eighteen is fragile; treating it as done invites the regression that erases the whole investment.
Treating communication as a launch event rather than a drumbeat. By Kotter's estimate the typical effort under-communicates by a factor of ten, and leaders' behaviour communicates louder than their slides.
Delegating the model to a programme office. The steps describe leadership behaviour; run as a project checklist without visible leaders, the same words produce none of the effect.
Reading the sequence as strictly linear. Steps overlap and loop in practice, and shocks mid-programme send you backwards; the numbering is a logic of dependence, not a promise you will visit each step once.

VII

What the critics say

The most thorough evidence review found support for most individual steps but no formal study validating the model as a whole, concluding that its popularity derives more from its direct, usable format than from scientific consensus. It is a plausible synthesis of consulting observation, not a tested theory.
Appelbaum, S. H., Habashy, S., Malo, J.-L. and Shafiq, H. (2012) 'Back to the future: revisiting Kotter's 1996 change model', Journal of Management Development, 31(8), pp. 764-782.

The model assumes change is episodic, planned and top-down: a programme with a beginning, middle and cultural end-state. Critics of n-step models argue organisational change is increasingly continuous and emergent, and that prescriptive sequences suit stable environments far better than the ones most organisations now face. Kotter's own 2014 dual-operating-system restatement is a partial concession to this critique.
By, R. T. (2005) 'Organisational change management: a critical review', Journal of Change Management, 5(4), pp. 369-380.

The model casts employees mainly as recipients of change whose resistance is to be overcome by urgency, communication and empowerment from above. Later change scholarship gives far more weight to bottom-up sensemaking, and warns that manufactured urgency and vilification of the status quo can produce the very resistance the model is designed to prevent.

The model's empirical footing includes the famous claim that some 70 per cent of change initiatives fail, a figure Kotter helped popularise. Hughes traced five published instances of the statistic and found no valid and reliable empirical evidence behind any of them: the burning platform on which the case for urgent, programmatic change is built is itself unevidenced folklore.
Hughes, M. (2011) 'Do 70 Per Cent of All Organizational Change Initiatives Really Fail?', Journal of Change Management, 11(4), pp. 451-464.

Hughes's later assessment of Leading Change itself concluded that the book endures as a landmark while its explanation of transformation failure does not stand up: the eight errors were never derived from systematic evidence, the model has remained essentially static across two decades in which Kotter himself describes accelerating instability, and a fixed sequence preserved unchanged since 1996 now paradoxically discourages the adaptiveness it claims to serve.
Hughes, M. (2016) 'Leading changes: Why transformation explanations fail', Leadership, 12(4), pp. 449-469.

VIII

Sources and further reading

Kotter, J. P. (1995) 'Leading Change: Why Transformation Efforts Fail', Harvard Business Review, 73(2), March–April 1995. ↗
Kotter, J. P. (1996) Leading Change. Boston, MA: Harvard Business School Press.
Kotter, J. P. (2014) Accelerate: Building Strategic Agility for a Faster-Moving World. Boston, MA: Harvard Business Review Press.
Appelbaum, S. H., Habashy, S., Malo, J.-L. and Shafiq, H. (2012) 'Back to the future: revisiting Kotter's 1996 change model', Journal of Management Development, 31(8), pp. 764-782. ↗

Pairs well with McKinsey 7S Framework·Objectives and Key Results (OKRs)·PDCA Cycle·RACI Matrix·compare side by side

Near neighbours (computed from shared tags)·ADKAR Model·Bridges' Transition Model·Hoshin Kanri