7 Critical Flaws: Why Kotter’s 8-Step Model Fails Modern Digital Transformation

Kotter's 8-step model is probably the most quoted change model in management. It began as a list of mistakes: in a 1995 Harvard Business Review article, John Kotter described eight errors he had seen while watching more than 100 companies try to transform themselves over a decade. His 1996 book, Leading Change, turned each error into a step.

The model has real flaws for digital transformation in a mid-sized European company. Some of the criticisms usually aimed at it are unfair, though, and Kotter answered several of them himself in 2012. This article separates the two.

Kotter's 8-step model: what it actually says

In its 1996 form, the model runs in sequence:

1. Establish a sense of urgency.
2. Create a guiding coalition.
3. Develop a vision and strategy.
4. Communicate the change vision.
5. Empower broad-based action.
6. Generate short-term wins.
7. Consolidate gains and produce more change.
8. Anchor new approaches in the culture.

Kotter's own verdict on the companies he studied was measured. A few succeeded, a few failed outright, and most landed somewhere in between, leaning towards the disappointing end. He did not claim that 70% of change efforts fail. That figure, often attributed to him, was traced by Mark Hughes in a 2011 paper in the Journal of Change Management, which found no valid empirical evidence behind it.

What Kotter changed in 2012

Three of the most common criticisms say the model is linear, run by a small elite, and built for stable times. In a November 2012 Harvard Business Review article, Accelerate!, followed by a book in 2014, Kotter made the same points about his own model. He replaced the eight steps with eight "accelerators" that run concurrently, rely on a "volunteer army" drawn from across the organisation rather than a small core group, and operate in an agile network alongside the hierarchy, which he called a dual operating system. Urgency is now built around a "big opportunity" rather than a threat.

Any honest critique has to start there. Attacking the 1996 sequence while ignoring the 2012 revision is attacking a model its author has already rewritten.

The critical flaws that remain

The first is the evidence base. In 2012, Appelbaum and colleagues published the first formal review of the model in the Journal of Management Development. They found support in the literature for most individual steps, no study testing the eight steps as a whole, and concluded that the model owes its popularity more to its usable format than to scientific consensus. They also found no evidence against it. That is a fair summary: plausible, practical, unproven as a system.

The second is where urgency comes from. Even in its opportunity-based version, urgency is something leaders create and transmit. The 1995 article quotes a former CEO whose aim was to make the status quo look more dangerous than the unknown. That is persuasion before diagnosis. It works when leadership has read the situation correctly, and amplifies the error when it has not.

The third is the order of the vision. In both versions, the vision and strategy are formed by the guiding coalition, then communicated, then supported by volunteers. The volunteer army enlists in a direction it did not shape.

The fourth is culture's place in the sequence. In 1996, culture arrives last, as the place where change is anchored. In my reading, culture is the material change is built from, which means it has to be understood first, not secured at the end.

The fifth is self-examination. Neither version contains a step in which the organisation looks at how it thinks: which assumptions go unquestioned, how decisions are really prepared, what it failed to learn last time. That capacity is what I call organisational metacognition.

The sixth is institutional. Kotter's organisation has a hierarchy and, since 2012, a network. It has no employee representatives. In much of continental Europe, works councils have a formal say on new technologies before decisions are taken, and a volunteer army does not replace that dialogue. This point comes from my field experience in European organisations rather than from published studies.

The seventh is scope. Appelbaum and colleagues conclude that the model is most useful as an implementation planning tool, and that complementary tools are needed during implementation to adapt to contextual factors and obstacles. The eight steps say what to plan. They say little about how to respond when the organisation pushes back in ways the plan did not foresee, and in my experience that is where a digital programme spends most of its time.

A human-centric alternative: reverse the opening

A human-centric approach keeps much of what Kotter got right: coalitions, visible wins, the need to change systems as well as minds. What it changes is the opening move.

The RESONANCE™ framework starts with an audit of how the organisation thinks and decides, then scopes the ambition to what teams can absorb, then sets the boundaries of the change with the people who will carry it. A network of internal change agents comes after that, so the coalition is built around a direction people have helped define. The same logic runs through the reviews of McKinsey change management and Prosci ADKAR, and the full comparison is in 8 digital transformation frameworks ranked.

Three questions before running a Kotter-style programme

Which version are you using? If your consultants present the 1996 sequence, ask why they skipped the 2012 revision.

What is the urgency based on? If it rests on a leadership reading nobody has tested against the people doing the work, test it first.

When do employee representatives come in? Before the vision is fixed, they help shape it. After, they can only react to it.

Assess your transformation readiness