Organizations use continuous improvement because small changes are cheap, quick and low risk, and because people who do the work see problems that managers miss. Over time the gains compound, and improving becomes part of everyone's job.
Where it comes from
The idea draws on Walter Shewhart's and W. Edwards Deming's plan-do-check-act cycle and on kaizen at Toyota. Masaaki Imai's 1986 book Kaizen helped spread the term outside Japan.
At a glance
The continuous improvement loop
Swipe sideways to see the whole diagram.
How to apply Continuous improvement
- 1
Set a direction
Agree what matters most right now, such as safety, quality, lead time or cost, and make it visible. Improvement works better when everyone pulls the same way.
- 2
Make problems visible
Use standards, visual boards and daily huddles so gaps between the standard and actual results show up quickly.
- 3
Run small PDCA cycles
For each problem, plan a change, try it on a small scale, check the result against the target and act on what you learned.
- 4
Standardize what works
Update standard work, training and checklists when a change proves itself, so the gain holds and the next cycle starts from a higher base.
- 5
Track and share ideas
Keep a simple log of ideas and their status. Share finished improvements so other teams can copy them.
- 6
Coach the habit
Leaders ask questions rather than hand out answers, and make time each week for teams to improve their own work.
Worked example
A warehouse team adds a five-minute improvement slot to its daily huddle. One week a picker suggests moving the ten fastest-moving items to the front of the aisle. The team tries it for a week, sees shorter pick routes, and updates the slotting standard. The next idea builds on the new layout.
Common mistakes
- Launching a program with posters and targets but no time set aside for teams to improve their work.
- Collecting ideas faster than the team can test them, so the backlog grows and people stop suggesting.
- Making changes without updating the standard, so gains slide back within weeks.
When Continuous improvement is not the right tool
Continuous improvement assumes the basic process can meet demand. If it cannot, a redesign, sometimes called kaikaku, may come first.
Continuous improvement examples
In a plant, a team cuts a changeover from 40 to 25 minutes over several small trials. In an office, a team removes a duplicate approval from a purchase request. In a clinic, staff move the most-used supplies next to each exam room.
Each change is small, tested and then written into the standard. The continuous improvement in lean guide covers strategies for keeping the habit going across a whole organization.