Free interactive simulator

Skip a Step

Skipping a step in a change program never feels like a mistake at the time. It feels like focus. John Kotter studied more than a hundred transformations and found the same thing every time: they don't fail at random, and they don't fail when you skip. They fail months later, at the exact place the skipped step was supposed to be holding the weight — by which point nobody connects the two.

Guess first — commit before you look

A program that does everything right, then stops

Eighteen months. For the first year you run it by the book: you build urgency, assemble a real coalition, set a clear vision, communicate it relentlessly, clear the blocking process, and land a visible win. Adoption climbs past half the organisation. At month 13 you declare victory — banner, thank-you email, team reassigned to the next priority. Where is adoption at month 18?

Higher than the peak — around 65% The hard part is done. Momentum carries it the rest of the way. Holds at the peak — around 55% It plateaus where you left it. What's adopted stays adopted. Slides back to around 40% You give back a big share of the gain you spent a year buying. Collapses to near zero Without the program, the whole thing unwinds completely.

Skip one step

Your budget doesn't shrink when you skip. The tokens you free up are spent on the other seven steps, so the skipped step is the only difference between your run and the textbook run. Skipping never saved money — it moved it.

Fine-tune the allocation — 12 tokens, eight steps, three each if you could afford it

Workshop mode. A step on 0 tokens fires its canonical Kotter failure; 1 token keeps it alive but strained; 2–3 and it pays off. Eight steps want 24 tokens and you have 12 — that shortfall is the exercise.

Pick a step to skip, then run. You can change it and re-run freely.

Textbook run — every step funded Your run

Event feed — what happened, month by month

No events yet. The feed narrates each month as the run plays out.

Final adoption

—

At month 18

Cost of the skip

—

Against the textbook run

Gains given back

—

Peak minus final

Errors triggered

—

Of Kotter's eight

What you observed, mapped back to Kotter's eight errors

The model

Eight steps, because eight ways to fail

Kotter's model wasn't derived from watching transformations succeed. It came from watching more than a hundred of them fail — first in the 1995 Harvard Business Review article "Leading Change: Why Transformation Efforts Fail," then in the book Leading Change. Each step exists because he kept finding its absence in the wreckage. That's why the steps are sequential: each failure mode is the absence of a step, and each step builds the platform the next one stands on. Skip one and the program doesn't fail immediately — it fails later, at the month where that step's work was supposed to be holding the weight.

Create urgency

Make the case for change vivid enough that people clear their calendars. Kotter's bar: about 75% of management genuinely convinced the status quo is more dangerous than the change.

Error #1: allowing too much complacency.

Build a guiding coalition

Assemble a group with enough position power, expertise, and credibility to lead the change — and get them working as a team, not a committee.

Error #2: failing to create a powerful enough guiding coalition.

Form a vision & strategy

A picture of the future clear enough to direct a thousand small decisions. Kotter's test: if you can't communicate it in five minutes and get a reaction, you're not done.

Error #3: underestimating the power of vision.

Communicate the vision (×10)

Use every channel, constantly — and behave consistently with the message. What leaders do is the loudest channel of all.

Error #4: undercommunicating the vision by a factor of ten.

Remove obstacles

Change the structures, systems, and incentives that still reward the old way — and confront the managers who undercut the change. Empowerment is mostly subtraction.

Error #5: permitting obstacles to block the new vision.

Generate short-term wins

Plan for visible wins in the first year — don't just hope for them. Wins are the evidence that keeps sponsors funded and skeptics quiet.

Error #6: failing to create short-term wins.

Consolidate gains

Use the credibility of early wins to tackle the bigger, structural changes. Resistance doesn't disappear when you celebrate — it waits.

Error #7: declaring victory too soon.

Anchor changes in culture

Show people how the new behaviours produced the results, and make sure hiring, promotion, and succession carry the change forward. Culture comes last, not first.

Error #8: neglecting to anchor changes in the culture.

Why "communicate ×10"

Of all eight errors, Kotter put a number on exactly one. Studying failed transformations, he found the vision was routinely undercommunicated by a factor of ten — and in Leading Change he sharpened it further: often by a factor of 100, even 1,000. The arithmetic is brutal. In three months, an employee might receive millions of words of corporate communication — emails, meetings, dashboards, hallway chatter. The transformation typically gets a kickoff, a few emails, and a slide at the town hall: a rounding error of the total. Everything else the company says is, implicitly, a message that nothing has changed.

That's why one great speech does nothing, and why in the simulator a weak step 4 hands the narrative to the grapevine. The vacuum always gets filled — the only question is by whom. Kotter's fix isn't louder announcements; it's every channel, every week, and leaders whose behaviour matches the words. Repetition isn't nagging. Repetition is the message.

Where this bites

The same delayed bill, in four different programs

The pattern the simulator draws isn't about software, or culture, or any one kind of change. It's about the lag between skipping a step and paying for it — long enough that the two never get filed under the same heading. Here it is wearing four different sets of clothes. In each one, the post-mortem blames the thing that broke, not the step that was skipped a year earlier.

The ERP rollout

Go-live is on time and under budget — a genuine win. Nobody retired the old spreadsheets or changed what finance is measured on (step 5, obstacles). A year later the system holds the official numbers and the spreadsheets hold the real ones. The post-mortem says "poor user adoption." It was an incentives decision made twelve months earlier.

The safety program

Incidents drop hard in year one — new procedures, visible leadership attention, a real result. Then the campaign ends and the improvement is declared permanent (step 7, consolidate). It never reached hiring, supervision, or promotion (step 8, anchor). Year three looks like year zero, and it reads as bad luck rather than a withdrawal.

The post-merger integration

Day one is flawless: systems cut over, org chart published, town hall done. What never happened was a coalition with real standing on the acquired side (step 2). For six months everything looks fine, because compliance looks exactly like commitment. It stops looking fine at the first hard trade-off, when nobody with credibility will carry it.

The AI mandate

Licences bought, training booked, an all-hands with a genuinely inspiring demo — then silence (step 4, communicate ×10). The vacuum fills itself: "this is really about headcount." Usage numbers stay flat and get read as a tooling problem, so the answer is a different tool. The tool was never the problem.

Honest caveats

What this model is — and isn't

Kotter's eight steps are the most useful checklist ever written for leaders driving change. They are not the whole story, and the simulator inherits their blind spots. Use the model with its limits in view:

It's a top-down model

The eight steps describe change as something leadership does to an organisation. That's often true — and it systematically underweights change that bubbles up from teams, customers, and the people closest to the work.

Pair it with a person-level model

Kotter tracks the program; models like ADKAR (awareness, desire, knowledge, ability, reinforcement) track each individual. An organisation "at step 6" still contains people at every stage — both lenses, or you're flying half-blind.

Expect a loop, not a line

Real change iterates: steps overlap, urgency needs re-creating, visions get revised mid-flight. Kotter himself later reframed the steps as continuous "accelerators" run by a volunteer army, not a one-pass sequence. The order still matters — as dependencies, not as a calendar.

The simulator is a caricature

Real organisations are noisier, slower, and more surprising than any deterministic curve. What the simulator preserves is the part Kotter's evidence supports: skipped steps send a bill, and the bill arrives late. Treat the numbers as story, not forecast.

Here's the uncomfortable version of the exercise you just ran: your organisation already has an allocation. It's visible in the last three change programs — the step that never gets funded, the failure mode that keeps showing up with different project names on it.

Which step does your organisation habitually skip? If you can name it — and most leaders can, instantly — you already know where the next transformation will bite. Fund that step first. Skipping it was never faster.