Small Steps vs. Big Leaps: Why Incremental Change Works

Why kaizen favors small, frequent improvements over occasional overhauls, when a bigger leap makes sense, and how to keep small changes adding up instead of fading.

Gidoka · Last reviewed October 24, 2026 · 5 min read

When a process is clearly broken, the instinct is to fix it all at once: a new system, a reorganization, a launch date. Big changes feel decisive. They are also slow to plan, expensive to get wrong and hard to learn from, because so many things change at the same time.

Kaizen takes the opposite default. It favors small changes, made often, by the people who do the work. That is not because big changes are never needed, but because small steps are easier to test, easier to undo and easier to build into habits. This guide explains the reasoning, where it comes from, and when a bigger leap is the right call.

Two ways to improve

Lean thinkers have names for both approaches. The Lean Enterprise Institute (LEI) describes kaizen as making "small, incremental improvements in processes and systems," and contrasts it with kaikaku, which it defines as "radical, revolutionary improvement of a value stream to quickly create more value with less waste." LEI notes that kaikaku is also called breakthrough kaizen, in comparison with more gradual, step-by-step kaizen.

The two are not enemies. LEI's examples of kaikaku include moving equipment over a weekend to switch from batch production in separate departments to single-piece flow in a compact cell. Improvement-minded organizations use both. The question is which one should be your everyday default.

Why small steps teach you more

Every change is a bet that it will make things better. Small changes let you check that bet quickly and cheaply.

The Institute for Healthcare Improvement (IHI) builds its improvement method around this idea. It describes the Plan-Do-Study-Act cycle as a method for learning how a change works in the local environment, and advises that early cycles "should be scoped as small as possible." Among IHI's reasons for testing before implementing: to increase your belief that the change will result in improvement, to evaluate costs and side effects, and to minimize resistance upon implementation.

Small tests also make it easier to tell what caused what. If you change one thing for one week in one place, you have a fair chance of seeing its effect. If you change ten things across a whole organization at once, the results are much harder to read.

IHI also points out that most changes require many cycles, run in sequence, to develop a change, test it under varying conditions and eventually implement it. Small steps are not a detour. They are how you find out what works before you commit to it.

Why small steps build capability

There is a second reason kaizen favors small steps: they develop people. LEI says kaizen events can be excellent for building capability and making substantial changes rapidly, but warns that leaders should not rely on them alone, because steady daily kaizen is what forces management to develop frontline problem-solving capability.

Toyota describes the same habit in its official account of the Toyota Production System, where "all employees implement daily incremental kaizen." Toyota calls the result of these "incremental efforts" a production line that is high-quality, low-cost, flexible and easy to maintain.

W. Edwards Deming made a related point in the fifth of his 14 Points for Management, as presented by the Deming Institute: "Improve constantly and forever the system of production and service." The word that matters there is "constantly": improvement as a normal part of the work, not an occasional project.

Small steps need a standard to stick

Small gains are easy to lose. LEI quotes Taiichi Ohno: "There can be no kaizen without a standard." LEI explains that teams should first establish a stable operating condition and a standardized way of working, then set targets against that baseline. When a team achieves a measurable gain, it updates the standard, which ensures the gain does not disappear. Without that step, LEI warns, teams perform kaizen on top of chaos and the gains rapidly vanish.

In practice, that means every small improvement should end with a small update: a revised checklist, a new label, a changed template, an updated training note. The standard is how one person's good idea becomes everyone's normal way of working.

When a bigger leap is the right call

Incremental change has limits. Jim Womack, who says he and Dan Jones first used the term gemba walk in the early 1990s, writes in an LEI article that he often tries to help managers see that the "point kaizen" they have settled for "is merely the low-hanging fruit" compared with the much bigger improvements possible through total process kaizen. Small fixes at one step can leave the larger flow untouched.

A bigger leap may make sense when:

The whole flow is the problem, not one step in it, and small changes keep running into the same structural limit.
The current setup cannot be stabilized, so there is no reliable standard to improve from.
An outside change, such as a new product line or a move to a new space, forces a redesign anyway.

Even then, kaizen thinking still helps. Break the big change into parts you can test, use a pilot area first, and keep checking results against your predictions.

How to keep steps small

IHI's tips for testing changes work well for any team. A few that translate directly:

Ask, as IHI suggests, "What change can we test by next Tuesday?"
Scale down the test: sample the next 10 cases instead of 200, or try it in one room for one week.
Test with willing volunteers. IHI notes that consensus and buy-in are necessary for implementation, but not for testing.
Avoid technical slowdowns. Track results with paper and pencil instead of waiting for new software.
Reflect on every test: what you expected, what happened, and what surprised you. IHI notes that teams often learn very important lessons from failed tests.

For example, imagine a three-person bookkeeping office where month-end closing always runs late. Instead of buying new software, the team tries one change for one month: clients get a reminder five days before their documents are due. If late documents drop, the reminder joins the month-end checklist. Next month, they test the next idea.

Pitfalls to avoid

LEI lists several ways kaizen events go wrong, and they are good warnings for small steps too:

Counting the number of improvement activities instead of tracking meaningful results such as safety, cost, quality and delivery.
Losing gains as people return to the previous way of working.
Leaving frontline workers out, so specialists far from daily operations lead the improvement.

Key takeaways

Kaizen favors small, frequent improvements; kaikaku, or breakthrough kaizen, is the radical alternative.
Small tests teach you faster, cost less when they fail and make cause and effect easier to see.
Daily kaizen builds frontline problem-solving capability in a way occasional projects cannot.
Every gain should update the standard, or it will fade.
Use bigger leaps when the whole flow needs redesign, but test them in parts where you can.

Sources

Spotted something out of date? Let us know.