Kaizen

Thinking Tools6.4 Conducting Follow-Up and Taking FeedbackAlso known as Continuous improvement

Set out and carried abroad by Masaaki Imai (Kaizen, 1986) from Toyota's production system and the postwar Japanese quality movement.

Commits everyone in an organization to small, daily improvements in their own work, with time and recognition for making them, so gains compound between big change programs.

Small improvements every week against one big program in the middle of the year

The black line is a large program, a new scheduling system that goes live in month seven and saves 40 hours a week from then on. The bars are the warehouse team's small improvements: each one saves a few minutes a week, and the ones that stick keep saving, so the bars climb every month. Set the pace, the size, and the share that stick, and compare the hours each saves over the year. Illustrative.

4
15 minutes
70 percent
Small improvements: hours a week saved by the end of the year
36.4
Small improvements: hours saved over the year
965
The program: hours saved over the year
1,040
The program: hours saved in the second year
2,080
Small improvements: hours saved in the second year, if they keep the pace
2,857

Small improvements: hours saved a week, by monthThe program

02550751003691215182124273033361234567891011120255075100369121518212427303336123456789101112

An example

A parts distributor's warehouse was losing hours to walking, searching, and rework, and the leadership team had approved a new scheduling system that would go live in July and save about 40 hours a week. The site manager added something alongside it. Each shift would spend fifteen minutes a day on one change to its own work, with a board to log it and a supervisor who could approve anything under $500 on the spot.

The first changes were small: tape outlines for the pallet jacks, a second label printer at packing, fast movers at waist height. The team logged about four a week, each saving around fifteen minutes a week, and about 70 percent were still in use three months later.

By December the small changes were saving 36 hours a week, close to what the system saved, and about 965 hours over the year against the system's 1,040. Because they kept accumulating, the second year was on track for nearly 2,900 hours. Leadership kept both, and made the daily fifteen minutes part of every shift's standard work.

Why it works

Big improvement programs come in steps: a long wait, a jump, then a plateau until the next program. Small improvements made by the people doing the work arrive continuously, and each one that sticks keeps paying every week after it is made, so the savings pile up month on month instead of arriving once. Over a year or two the accumulation can match or pass the big step, at far lower cost and risk.

The second reason is who sees the waste. People doing the work notice the small losses that no program team will ever spot, such as a printer in the wrong place or a bin at the wrong height. Giving them time, a small budget, and quick approval turns that knowledge into changes. The habit also makes the big programs land better, because the people affected are already used to changing their own work.

The thinking behind it

Masaaki Imai Masaaki Imai, a Japanese management consultant, set out kaizen for Western managers in Kaizen: The Key to Japan's Competitive Success (1986), the year after he founded the Kaizen Institute. He drew it from Toyota's production system and the postwar Japanese quality movement and described it as continuous improvement through many small changes involving everyone, from managers to workers on the floor, as a complement to the occasional large innovation. The book is a practitioner's synthesis of Japanese practice, not research.

How to run it

  1. Give the time. Set a fixed slot, ten or fifteen minutes a day or an hour a week, that each team spends on improving its own work.
  2. Start where the work happens. Have each team pick a loss it sees every day: walking, waiting, searching, rework.
  3. Keep changes small. Favor changes a team can try this week with what it has, over proposals that need a project.
  4. Approve on the spot. Let a supervisor approve small spending and changes immediately, so ideas do not die in a queue.
  5. Make it visible. Log each change on a board with its owner, date, and estimated saving.
  6. Check what sticks. Revisit changes after a few months and keep the ones still in use as standard work.
  7. Recognize the people. Thank and credit the people behind changes publicly, and count participation as well as savings.

Where it goes wrong

It turns into a suggestion box. Ideas go up to managers and wait for approval, and people stop offering them; spot it when the log shows proposals but few changes made. Push approval for small changes down to the floor.

It becomes a quota. Teams told to log five improvements a week log five trivial ones. Count only the changes still in use months later.

Leaders treat it as the workers' job. When managers never take part and cancel the slot whenever the week is busy, the habit fades within a quarter. Protect the time in the busiest weeks, and have leaders run their own improvements on their own work.

When to use something else

  • PDCA Cycle. When one specific improvement needs a careful test of a prediction before it becomes standard.
  • Toyota Kata. When a team needs a coached daily routine for moving toward a defined target condition.
  • Value Stream Mapping. When the waste sits between teams and has to be seen across the whole flow first.

Where it sits in SOLVE eX

Go to the source

  • Kaizen: The Key to Japan's Competitive Success, 1986

Back to the catalog