What is Kaizen?

Discover why Kaizen is a multi-decade commitment, not a quick fix. Learn how incremental improvements build an unassailable competitive advantage.

A staircase spiralling upwards as a metaphor on kaizen, or continuous improvement

Kaizen (改善) is the Japanese word for continuous improvement, and it's the foundation of the Toyota Production System. The basic idea is simple: small changes, applied consistently over years, compound into something far larger than any single project could ever deliver. The hard part isn't understanding the concept – it's staying with it long enough for the compounding to actually happen, which is where most companies quietly give up.

I worked inside Toyota for several years, and what struck me was that Kaizen wasn't a slogan or an initiative anyone talked about as a thing – it was just how the place ran. People on the factory floor and in the offices spent part of every day looking at their own work, identifying small improvements, making the change, checking whether it worked, and standardising the result if it did. There was no programme office, no consultant, and no kick-off event. It was simply part of the job.

A practical example helps here. On Toyota's assembly lines, the workers themselves design their own tool carts – each cart holds every tool needed for the specific job that worker is doing, nothing more, arranged in the order they'll reach for them. The worker designing the cart knows the job better than any engineer or manager possibly could, because they're the one doing it 200 times a day. Each cart cuts a few seconds off every car. Toyota builds around 10 million cars a year, and the arithmetic is generous.

That, in practice, is Kaizen. Not a revolution. A single cart.

Why Kaizen Looks Slow Until It Doesn't

The hardest thing to communicate about Kaizen, especially to leaders raised on transformation projects and quarterly KPIs, is that nothing dramatic happens for a long time. When Toyota started exporting cars in the 1950s, "Made in Japan" was not yet a mark of quality. It took roughly forty years for that to fully reverse, and by 2008 Toyota had become the largest car manufacturer in the world.

Forty years is not a strategy most boards will sign off on. It is, however, what actually happened, and the climb was not the result of a few brilliant initiatives. It was the cumulative effect of millions of tiny improvements, each one unremarkable on its own.

The mathematics is straightforward. A 1% weekly improvement compounds to 67% after a year, and roughly twelve‑fold after five years. The numbers themselves aren't the point – the point is that small changes compound the same way savings do, and an organisation that makes small improvements relentlessly will eventually find itself at a level its competitors cannot reach without a much larger and more disruptive intervention.

This is why Kaizen is the pursuit of perfection. Perfection is, by definition, unattainable, but that is the point. Each improvement is one step on a stairway that never ends. The stairway is what keeps people climbing.

The Four Tools

Kaizen is not a single tool. It is a system of four tools operating together inside a culture that supports them. Removing any one of the tools, or attempting to use them outside that culture, is where most adoption attempts fail.

The four tools are:

PDCA (Plan-Do-Check-Act) is the project management discipline at the centre. Plan a change, run it, check what actually happened, act on what you learned. Then repeat. PDCA exists to stop people from operating in what Toyota calls the Do-Do-Do-Do cycle, applying fixes without first examining whether they address the actual problem.

Horenso (報連相) is the communication discipline. It's a compound of three Japanese abbreviations: report, update, and consult. The original concept was developed for hierarchical factory environments, but the version used today operates in three directions – up to supervisors, across to teammates, outward to stakeholders. It's what keeps the other tools connected.

The 5-Whys is how Toyota finds root causes. The method is exactly what it sounds like: state the problem, ask why it happened, ask why about the answer, repeat five times. Five iterations is usually enough to reach a structural cause rather than a surface symptom. Solutions applied at the surface tend to fail: the problem returns in a slightly different form. Solutions applied at the root tend to stick.

Mieruka (見える化) is visual control. Its purpose is to make the state of work visible at a glance. In a Toyota factory this means whiteboards showing daily progress, colour-coded floor markings, magnetic Gantt charts, labels on every shelf. The principle is that information which has to be looked up gets ignored, while information which is unavoidable gets used.

Two supporting principles sit alongside the four tools: Genchi Genbutsu (go and see for yourself), and 5S (workplace organisation). Both feature heavily in factories. Both require significant adaptation when used in a service or knowledge-work context.

Why Most Kaizen Programmes Fail

The tools themselves are not difficult to teach. The cultural conditions under which they actually work are harder to build, which is why so many adoption attempts produce paperwork rather than improvement.

The pattern I see most often is the suggestion box. A company decides to "do Kaizen", installs a box on the wall, runs no training on root-cause analysis or the four tools, and waits. Suggestions trickle in. Management reviews them slowly, ridicules a few of them, and eventually stops reviewing them at all. The box becomes a piece of office furniture. The programme is declared a failure six months later, and Kaizen joins the long list of management fads that didn't work for that particular organisation.

What actually went wrong is rarely the suggestion box itself. The deeper problems are structural. There are six failure modes I see repeatedly, and each one is the mirror image of a cultural condition under which Kaizen succeeds. Briefly:

  1. The organisation treats Kaizen as a short-term project rather than a multi-decade commitment.
  2. Leaders over-emphasise tying improvements to KPIs, ignoring the incremental nature of compounding gains.
  3. The organisational culture punishes change rather than rewarding it.
  4. Senior management endorses Kaizen but does not visibly practise it.
  5. Staff are expected to use the tools without proper training in any of them.
  6. Improvement ideas are required to flow top-down rather than bottom-up.

Any one of these is enough to stall a programme. Most failed Kaizen efforts have three or four of them simultaneously.

How To Actually Start

If you want to introduce Kaizen into an organisation that doesn't yet support it, the path is not a launch event. It is a small experiment, run by a small team, on a real problem, using the four tools properly.

A useful starting point is to pick a recurring annoyance and run a single PDCA cycle on it – something that frustrates the team weekly but isn't life-threatening. Identify the problem. Plan a small change. Make the change. Check whether it worked. Run a 5-Whys analysis on whatever didn't work as expected. Standardise the result. Then move to the next problem.

The first cycle will be awkward. The second will be slightly better. By the fifth, the team will be running them without thinking about it, and at that point the practice has started to embed. This is how Kaizen actually takes root – not through a launch, but through the quiet accumulation of cycles that worked.

If, in forty years, the organisation looks back and sees a stairway, the climb will have been worthwhile. If it looks back and sees a suggestion box gathering dust on a wall, the diagnostic isn't that Kaizen failed. It's that nothing was ever really tried.

Related
The Toyota Production System Series
This article is part of a 40+ article series on the Toyota Production System, drawn from years working inside Toyota. For the distilled version of the whole system, see The Kaizen Roadmap, a free briefing covering Kaizen, PDCA, Horenso, the 5-Whys, Mieruka, Genchi Genbutsu, and 5S, with case studies and a diagnostic.

Comments

All posts loaded No posts found VIEW ALL Read more Reply Cancel reply Delete By Home PAGES POSTS View All RECOMMENDED FOR YOU LABEL ARCHIVE SEARCH ALL POSTS No posts found Home Sunday Monday Tuesday Wednesday Thursday Friday Saturday Sun Mon Tue Wed Thu Fri Sat January February March April May June July August September October November December Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Just now 1 minute ago $$1$$ minutes ago 1 hour ago $$1$$ hours ago Yesterday $$1$$ days ago $$1$$ weeks ago more than 5 weeks ago Followers Follow THIS CONTENT IS LOCKED STEP 1: Share to a social network STEP 2: Click the link on your social network Copy All Code Select All Code All codes were copied to your clipboard Can not copy the codes / texts, please press [CTRL]+[C] (or CMD+C with Mac) to copy Table of Content