Definition
Kaizen is the practice of continuous improvement — making processes better through the daily discipline of working from a standard, finding deviations and problems, and establishing a new, better standard. At Toyota, kaizen is not a special event or a program. It is the expectation that every person, from shop floor workers to executives, improves their own work every day.
The cycle is: standardize → follow the standard → find problems → improve → create new standard → repeat. Without a stable starting point (standardized work), kaizen cannot function. Without kaizen, standards stagnate.
Japanese Origin
The word kaizen (改善) is an ordinary Japanese term used in daily life. The character 改 (kai) means “change,” “reform,” or “renew” — it implies correction, fixing what is wrong. The character 善 (zen) means “good” or “virtue.” Together: “change for the better.”
This is not a Toyota invention — any Japanese person uses 改善 to mean improvement in any context. What Toyota did was build an organizational system around the concept, making it the responsibility of every employee rather than a management initiative imposed from above.
History at Toyota
Kaizen at Toyota has multiple roots, not a single origin:
Training Within Industry (TWI), 1950s — During the Allied occupation of Japan, the U.S. brought TWI programs to rebuild Japanese industry. The Job Methods (JM) module taught frontline supervisors a structured approach to improving their own work processes. Toyota officially started TWI programs in 1951. This influence is frequently overlooked but was foundational.
JUSE and the quality movement, 1950s-60s — The Japanese Union of Scientists and Engineers promoted statistical quality control, influenced by W. Edwards Deming and Joseph Juran. QC circles (品質管理サークル) — small groups of workers applying quality methods — emerged from this movement. The first QC circles were registered with JUSE in 1962.
Toyota’s Creative Idea Suggestion System, 1951 — Toyota established its individual suggestion system early. Any employee can submit improvement ideas. Toyota tracks these meticulously — by the 1980s-90s, they received hundreds of thousands of suggestions per year with implementation rates above 90%. The sheer volume and implementation rate distinguishes this from Western suggestion boxes, which typically have low participation and near-zero follow-through.
Taiichi Ohno’s production system, 1950s-70s — Ohno embedded kaizen into the structure of TPS itself. Reducing kanban quantities, shortening changeover times, solving problems surfaced by andon — all of these are kaizen activities driven by the system’s design, not by special programs.
How It Actually Works
Toyota’s kaizen operates on multiple levels simultaneously:
Daily kaizen — Small, incremental improvements made as part of normal work. A team leader notices a process problem and fixes it. A worker finds a better way to position a tool and updates the standardized work sheet. This is the most common form and the hardest for outsiders to replicate because it requires a culture where frontline workers are expected and enabled to improve their own processes continuously.
QC circles — Voluntary, small-group activities where teams study a problem using structured problem-solving methods (typically PDCA). These are ongoing, not time-boxed events.
Suggestion system — Individual ideas, often small, submitted formally, tracked, and implemented rapidly.
Project-level improvement — Larger-scale changes requiring cross-functional effort or capital investment, conducted within normal management structures.
The critical difference from Western practice: At Toyota, management’s primary role in kaizen is not to improve processes directly — it is to develop people’s problem-solving capability. A manager who fixes problems without building the team’s ability to find and fix problems themselves is not doing their job.
Implementation Guidance
Standards come first. You cannot improve a process that is not standardized. Every kaizen starts from a documented current standard and produces a new, better standard. Without this discipline, improvements are temporary — they regress within weeks.
Build problem-solving capability, not dependency on experts. Train frontline workers and supervisors in structured problem-solving (PDCA, 5-Why, A3). The goal is that the people closest to the work are the ones improving it.
Make problems visible. Kaizen depends on the ability to see abnormalities. This is why visual management, andon, and standardized work are prerequisites — they make it obvious when something deviates from the standard.
Start with a suggestion system. Even a simple one — index cards submitted to team leaders, reviewed weekly, with a commitment to implement or explain why not within a defined timeframe. The key is rapid response: if workers submit ideas and nothing happens, the system dies.
Track implementation, not just ideas. The metric that matters is implementation rate, not number of suggestions. Toyota’s 90%+ implementation rate is what makes their system work — workers submit ideas because they see them acted on.
Common Mistakes
Treating kaizen as an event. The Western “kaizen event” or “kaizen blitz” — a 3-5 day intensive workshop — has no real equivalent in Toyota’s traditional practice. These were popularized by consultants who needed a deliverable format. Toyota conducts focused improvement activities, but the backbone is daily, ongoing improvement by every person. Events can be a useful starting point for organizations new to improvement, but they are not kaizen.
Attempting kaizen without standardized work. Improving an unstandardized process is meaningless — there is no baseline to improve from, and no way to tell if the change made things better. The result is random oscillation, not improvement.
Separating kaizen from daily work. If improvement is something you do during special events, separate from your “real job,” you will never build a kaizen culture. At Toyota, kaizen is the job — working to standard and improving the standard are inseparable.
Focusing on cost reduction. Western companies often frame kaizen as a cost-cutting exercise. At Toyota, the focus is on eliminating waste, developing people, and building capability. Cost reduction is a byproduct, not the goal. When cost is the primary driver, workers correctly perceive kaizen as a threat to their jobs, and participation collapses.
Ignoring the respect for people pillar. Kaizen at Toyota is inseparable from the principle of respect for people (人間性尊重). The purpose is not to wring more productivity from workers but to develop every person’s problem-solving capability. When this is missing, kaizen becomes a tool of management control rather than worker empowerment.