Kaizen versus Kaikaku: the power of the small step
In brief
Kaikaku changes a value stream from the ground up; Kaizen takes one step every day. They are not rivals, but it is the small step that builds a company's culture. The difference, and how to use both.
17 October 2026 · 4 min read
Sample company · demo dataNew Kaizen form
The Lean Enterprise Institute lexicon defines the two side by side: Kaizen is continuous, small-step improvement; Kaikaku is radical, breakthrough improvement of a value stream. Building a new line, redesigning the layout or replacing a process entirely is Kaikaku. Moving a fixture ten centimetres closer, enlarging a label or bringing a check forward is Kaizen.
Why both are needed
Kaikaku brings big gains, but it happens rarely, needs investment and usually comes from the top. Kaizen brings small gains, but it happens every day, needs no investment and comes from below. Toyota's own production system page describes how daily improvements made the system what it is today. A big leap changes a moment; a small step changes a habit.
Kaikaku: a project team, a budget, months; a big result and a high risk.
Kaizen: the person doing the job, near-zero cost, days; a small result and a low risk.
Kaizen after Kaikaku: when the new line is built, the real work begins; the people on the floor do the fine-tuning.
The small step and respect for people
The power of Kaizen lies not in its arithmetic but in its owner. An engineer runs the big project and the employee adapts to it. The employee thinks of the small step, tries it and sees it in their own job. That is why Kaizen is also the daily form of respect for people: “You do this job, you know best how to do it better.” The manager's job is as much to allow the trial and measure the result together as it is to evaluate the idea.
A common mistake is to restrict Kaizen to ideas with large gains. Rejecting an idea because its gain is small means the next big idea never gets written. The small step is cheap; because it is cheap it can be tried; because it can be tried, it teaches.
Before and after
Every Kaizen should have a “before”, an “after” and a measurement. A photo is the simplest evidence. The measurement says not how large the gain is but whether the change worked; a Kaizen that did not work is still valuable because it taught something.
An example from the floor (fictional)
On an assembly line the screw bin sat behind the operator's left shoulder; every part needed a half-step turn. The operator suggested moving the bin to the front at waist height. The change was made during a lunch break and its cost was moving one shelf. The gain was a few seconds per part; the real gain was that the operator's back no longer hurt at the end of the shift. That is Kaizen. Converting the whole line to a U shape would be a Kaikaku lasting months, and the first person to ask in that project is the same operator.
The manager's trap: putting the small on hold
While a big project is being planned, small ideas are postponed because “the line is changing anyway”. That postponement loses two things: today's gain and the employee's interest. Kaizen does not stop until Kaikaku is done; on the contrary, the best data on what the new line should be like is the record of small improvements made on the old one. The manager's job is to run two speeds at once: protect the project calendar and answer daily ideas the same day.
Sample company · demo dataKaizen record
How it is done in Gemy
Kaizen is a record type; the ready-made template has fields for the problem, the root cause (with 5 Whys), a before photo, the change made and an after photo. The form belongs to the company, which adds and removes fields.
When the company switches on verified value, the estimate and the validated amount stay apart; cash gain, time gain and avoided cost sit on separate cards and are never merged into one total.
Large team efforts have Kobetsu Kaizen projects: the loss, the team, steps, target and minutes. They feed the same action list as daily Kaizen.
Where the company turns on roll-out (Yokoten), a successful Kaizen can be suggested to similar areas; each applies, adapts or declines with a reason.
The system does not decide which idea is Kaizen and which is Kaikaku; it records both with the same discipline.
In short
Kaikaku changes a value stream from the ground up and happens rarely; Kaizen takes one step every day and is everyone's job. They are not rivals, but the small step builds the company's culture, because the small step is in the hands of the person doing the work. The manager's job is not to keep small ideas waiting while the big project is planned, to make sure every Kaizen closes with a before, an after and a measurement, and to record a failed trial as learning too. The small step is cheap, so it is tried; it is tried, so it teaches.
Every solved problem is a piece of knowledge; in most companies it leaves with the person who solved it. The four places where knowledge is lost, the view of ISO 30401 and ISO 9001, and five habits that make knowledge independent of people.
Takt time is the customer's pace; Yamazumi stacks each station's load against that pace. Calculating takt, reading the chart, the balancing sequence and how to explain balancing to the operator.
Autonomous maintenance means the person who knows the machine best, the operator, takes over its daily care. The content of the first three steps, the abnormality tag, the CIL standard and the division of work between operator and maintenance.
7 November 2026 · 5 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.