What it means
The idea came out of Japanese manufacturing and is now applied across services, healthcare and office work. The core belief is that the person operating a process sees waste a manager never will, so improvement should be constant and driven from the bottom up.
A change that saves two minutes counts, provided it actually sticks. The business case is compounding.
One improvement rarely shows up in the accounts, but hundreds of them across a year move cycle times, scrap rates and labour hours in a way competitors find hard to copy. It is also cheap, because most accepted suggestions cost very little to implement.
In practice teams run short structured cycles: observe the current process, measure it, propose a small change, test it, then either standardise it or discard it. Many organisations use a formal improvement event, a focused few days where a cross-functional group reworks one process end to end.
Others simply hold a fifteen-minute daily huddle in front of a board of open ideas. Measurement is what separates this from a suggestion box.
Each change needs a before figure and an after figure, whether that is minutes per unit, defects per thousand or steps walked per shift. Without numbers, teams argue about opinions and improvements quietly disappear.
The usual failure is cultural rather than technical. If suggestions are ignored, if improvement is treated as a project with an end date, or if every saving is immediately converted into headcount cuts, people stop contributing.
Programmes that last protect time for improvement work and make results visible to everyone.
In practice
Real-world examples.
Example
A hospital pharmacy team notices that nurses walk to a central store six times a shift for routine items. They move the twenty most-used products into a cabinet on the ward, freeing roughly forty minutes of nursing time per shift for patient care.
Example
A call centre agent suggests reordering three questions in the account verification script so customers stop being asked for information the system already displays. Average handling time falls by eighteen seconds, which across 400,000 calls a year is a substantial capacity gain at no cost.
Example
A bakery runs a two-day improvement event on the morning changeover between bread and pastry production. By preparing trays the night before and relabelling the oven controls, the team cuts changeover from 55 minutes to 20 minutes and gains an extra production run each day.
Think of it
“Kaizen is the Japanese word for continuous improvement-making things better bit by bit.
Formula
Calculation
Formula: annual saving = time saved per unit x units produced per year x fully loaded labour cost per hour.
Worked example. A packing line takes 30 minutes of labour per pallet. An improvement team repositions the label printer and the shrink wrapper so the operator stops walking between them, cutting the task to 27 minutes. That is a saving of 3 minutes, or 0.05 hours, per pallet.
The site packs 120,000 pallets a year, so the change saves 120,000 x 0.05 = 6,000 labour hours annually. At a fully loaded cost of $25 per hour, that is 6,000 x $25 = $150,000 a year from moving two machines. The change cost about $4,000 in fitting and cabling, so it repaid its cost within the first month of operation.Case study
Seen in the real world.
Larkspur Ceramics is an illustrative tableware manufacturer invented for this entry. Its kiln loading process had barely changed in fifteen years, and breakage during loading ran at about 6% of output. Rather than commissioning a consultancy, the plant manager gave each shift thirty minutes a week to test one idea, plus a board on which to record the before and after numbers.
Over eleven months the three shifts trialled forty-one changes, of which nineteen were kept: a redesigned trolley, softer stacking spacers, a revised loading sequence and a pre-kiln inspection among them. Breakage fell from 6% to 2.4%, worth roughly $310,000 a year on the fictional company's output, and no individual change cost more than $2,000.
The point of the illustration is that not one of those ideas would have justified a project on its own, yet the accumulation clearly did. The manager's main job turned out to be protecting the thirty minutes rather than generating ideas.
Watch out
Common mistakes.
- Treating improvement as a one-off programme with a launch event and a closing report. It is a routine, and it stops producing results the moment it stops being routine.
- Only counting large savings. Filtering out the small ideas removes most of the value and discourages the people closest to the work.
- Improving a step that is not the constraint, which produces a tidier process and no extra output at all.
Questions
People also ask.
How is this different from lean management?
Kaizen is the continuous improvement habit, while lean is the wider system of principles and tools that the habit sits inside.
Who should run improvement sessions?
The team doing the work, with a facilitator to keep the numbers honest and to remove obstacles the team cannot clear itself.
How do we stop improvements slipping back?
Standardise the new method in writing, train everyone to it, and re-measure a few weeks later to confirm the gain has held.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%