Kotter’s 8-Step Change Model

Kotter’s model organizes large-scale change around eight recurring tasks, arguing from practitioner observation that neglecting foundational work, like building real urgency or a genuine guiding coalition, makes later activity much less likely to stick.

3 min read

What Is It?

Harvard Business School professor John Kotter proposed the model in a 1995 Harvard Business Review article and later expanded it into the book Leading Change (1996), building on his observation of change efforts in more than 100 companies over the preceding decade. The eight steps, establishing a sense of urgency, forming a powerful guiding coalition, creating a vision, communicating that vision, empowering others to act on it, planning for and creating short-term wins, consolidating improvements and producing still more change, and institutionalizing new approaches in the culture, were framed as a sequence in which skipping or rushing an early step creates problems that resurface later, even if the effort appears to be moving forward. The model is drawn primarily from Kotter’s own consulting observation and case-based reasoning rather than from controlled research, it’s best treated as a structured, experience-based framework and widely used practitioner heuristic rather than an empirically validated causal theory, its wide adoption reflects its practical resonance with change practitioners more than a settled evidence base establishing that following all eight steps in order reliably produces successful change.

Why Does It Matter?

Kotter’s framework particularly highlights the risk of underinvesting in the earliest steps, especially establishing genuine urgency and building a guiding coalition with real cross-functional authority, since they’re the least visible and the least satisfying to complete relative to steps like announcing a new vision or celebrating an early win. A change initiative can move straight to communicating a vision without ever having built the urgency or coalition the vision depends on. The framework asks whether visible activity is being mistaken for readiness, whether communication has raced ahead of the coalition, authority, or urgency needed to support it.

The model also draws attention to a specific, common failure: declaring victory too soon. An early win gets celebrated, attention and resources shift elsewhere, and the deeper cultural and structural changes that would have made the improvement durable never get consolidated, leaving the organization vulnerable to reverting once the initial push fades.

What Changes Once You See It?

You start treating a change effort’s early stages, urgency and coalition-building specifically, as work that has to be genuinely completed rather than gestured at before moving to the more visible, satisfying stages of communicating a vision or celebrating a win.

You start watching for premature declarations of success, a single early win treated as proof the change has taken hold, rather than as one data point in a longer consolidation process that still has real work ahead of it.

You also get more attentive to whether “institutionalizing” a change has actually happened, whether the new way of doing things has become genuinely embedded in how people are hired, evaluated, and promoted, rather than just formally announced and then left to persist or fade on its own.

The framework becomes most useful when its eight steps are treated as conditions to establish rather than activities to complete. Holding a town hall isn’t the same as people actually perceiving urgency, naming a coalition isn’t the same as having a coalition with real influence, and publishing a vision isn’t the same as people understanding the direction. A step can be checked off on a project plan without the underlying condition existing.

Common Misunderstandings

  • It isn’t an empirically validated causal model in the way a controlled experiment would establish. It’s a structured framework built from Kotter’s own consulting experience and case observation, useful as an organizing heuristic for what commonly goes wrong, not as proof that following all eight steps in order guarantees success.
  • Kotter is best read as a process checklist derived from practitioner observation, not as a general theory of why social systems change. Lewin gives a way of understanding change; Kotter gives a way of organizing a transformation effort, and the two serve different purposes.
  • It isn’t a claim that change must proceed in strict, rigid sequence with no overlap. In practice, later steps often begin before earlier ones are fully complete, the value of the sequence is mainly in flagging which foundational work tends to get skipped, not in enforcing a strict order.
  • It doesn’t mean every failed change effort skipped one of these eight steps. Change can fail for reasons the model doesn’t address, external market shifts, resource constraints, factors entirely outside the organization’s control, the model describes a common internal failure pattern, not an exhaustive account of why change efforts fail.
  • It isn’t the same as Lewin’s unfreeze-change-refreeze model, though the two are often taught together and share a family resemblance. Kotter’s model is a more granular, practitioner-oriented sequence aimed specifically at large organizational transformations, Lewin’s is a more general theory about the forces holding any social equilibrium in place.

Diagnostic Question

Which of Kotter’s eight tasks are actually functioning in this change effort, and which exist mainly as completed activities on the project plan?

Explore Further

Field Notes

  • None yet.

Related Field Guide

Origin

John P. Kotter, “Leading Change: Why Transformation Efforts Fail,” Harvard Business Review (1995), later expanded into Leading Change (1996), drawing on Kotter’s observation of change efforts in more than 100 companies over the preceding decade.

Know someone who’d enjoy this?