Kaizen is a Japanese word usually translated as "change for the better" or "continuous improvement". In practice, it means many small improvements made by the people who do the work, rather than a few large projects handed down by management.
Why small improvements matter#
A single change that saves two seconds per garment looks minor. On a line making 1,000 garments a day, it saves more than half an hour of work every day, every day the style runs. Many such changes across a factory add up to large gains in output, quality and working conditions.
The PDCA cycle#
Kaizen follows the Plan-Do-Check-Act cycle:
- Plan: pick a problem, understand the current situation, find the cause, propose a change.
- Do: try the change on a small scale.
- Check: measure the result against the situation before.
- Act: if it works, make it the new standard; if not, learn and try again.
Finding problems to work on#
- Bottlenecks and stations with high WIP.
- Frequent defects from end-of-line data. See DHU.
- Machine stops and thread breaks.
- Awkward movements or uncomfortable workstations.
- Searching and waiting: for trims, tools, bundles, or instructions.
- Operator ideas: operators often know what slows them down.
Kaizen events#
A kaizen event (sometimes called a kaizen blitz) is a focused improvement session, usually a few days long, on one area. A small team including operators, a supervisor, an engineer and maintenance studies the area, makes changes, and measures the result before the event ends.
Suggestion systems#
A simple suggestion system lets operators and staff propose improvements:
- Keep the form short: problem, idea, expected benefit.
- Respond quickly, including to ideas that are not adopted.
- Recognise and share implemented ideas.
- Track the number of ideas received and implemented.
Examples#
| Area | Problem | Kaizen |
|---|---|---|
| Sewing | Operator reaches behind for bundles | Bundle stand moved to the left of the machine |
| Sewing | Frequent thread breaks on one overlock | Thread path cleaned, stand repositioned, tension checked |
| Cutting | Time lost finding markers | Marker storage labelled by style and size |
| Finishing | Searching for polybags in the right size | Polybags stored by size at each packing table |
| Quality | Same defect found every day at end of line | Inline check added after the operation that causes it |
Measuring results#
Record a before and after measure for each kaizen: cycle time, output per hour, DHU, WIP, or walking distance. Numbers keep the program honest and show which types of improvement pay best.
Common mistakes#
- Treating kaizen as a campaign that stops after a few weeks.
- Collecting ideas but not acting on them.
- Changing methods without updating standards and training, so the improvement fades.
Kaizen works best together with 5S, root cause analysis and wider lean manufacturing practice.
Related guides#
- Motion study: finding small method improvements at a workstation.
- 5 Why analysis: getting to the cause before choosing a kaizen action.
Frequently asked questions#
Who should lead kaizen? Line supervisors and operators, supported by industrial engineering, maintenance and quality. Management's role is to make time for it, remove obstacles and follow up.
How big should a kaizen be? Small enough to try within days with little or no cost. Larger changes need a project with a budget and a plan.
How do we keep ideas coming? Respond to every suggestion quickly, implement what works, and show results publicly at the line.