The types of kaizen in manufacturing are Kaizen Teian (daily individual improvements), kaizen events (focused team workshops), kaikaku (radical process transformation), and kakushin (breakthrough innovation), with point kaizen and system kaizen describing the scope dimension that applies across all four. Each type operates at a different scale of change, resource requirement, and implementation speed, and selecting the wrong type for the problem consistently produces wasted resources rather than measurable improvement. Manufacturing organizations that treat all improvement activity as requiring the same structure, whether scheduling a multi-day event for a minor process adjustment or attempting daily improvement for a problem requiring fundamental redesign, misallocate improvement capacity and erode confidence in the kaizen system.
Understanding the full kaizen type spectrum equips plant managers and production supervisors to diagnose improvement opportunities correctly and select the approach that matches the scale of the problem. The full kaizen philosophy, including the five elements and cultural requirements, is covered in [Kaizen: A Complete Guide to Continuous Improvement in Manufacturing]. This blog focuses specifically on the types, their defining characteristics, and the criteria that determine which to deploy.
The Kaizen Type Spectrum: How Improvement Scale Shapes the Approach
Kaizen types are best understood as a spectrum organized by scale of change, resource requirement, and implementation speed. Each type occupies a distinct position on that spectrum, and each has a specific domain of problems it is designed to address.
Four primary kaizen types structure the spectrum in manufacturing practice:
- Kaizen Teian: daily individual improvements, no formal process required
- Kaizen Events (Kaizen Blitz): focused team workshops, three to five days, defined scope
- Kaikaku: radical process transformation, significant resource investment
- Kakushin: breakthrough innovation, fundamental business model change
Two additional scale concepts appear frequently in lean literature and are worth understanding in relation to the four primary types:
- Point kaizen: improvement to a single workstation or process step, typically executed as daily kaizen or a short event
- System kaizen: improvement to an end-to-end value stream, typically requiring a kaizen event or kaikaku-level intervention
The critical operating principle is that kaizen must be the foundation before kaikaku or kakushin are attempted. Radical transformation on an unstable process baseline produces unstable transformation results. Organizations that have not built daily kaizen discipline first find that kaikaku improvements erode at the same rate as any other improvement initiative, because the cultural and operational foundation for sustaining change does not yet exist.
Key Insight: Selecting the wrong kaizen type for the problem scale is as damaging as not improving at all. It burns resources, misses the root condition, and erodes confidence in the improvement system.
Kaizen Teian: The Daily Improvement Foundation
Kaizen Teian (改善提案) is the individual suggestion and daily improvement system through which every employee contributes directly to continuous improvement as part of their normal work. Teian translates as "proposal" or "suggestion," and together with kaizen it describes the practice of every operator constantly observing their process and acting on small improvement opportunities within their own authority.
What Kaizen Teian Looks Like in Practice
Kaizen Teian operates at the smallest scale of the improvement spectrum. Improvements are typically same-day or within the current shift, require no capital expenditure, and need no formal approval. Observable examples in manufacturing include:
- Repositioning a tool or component to eliminate a reaching motion
- Marking a floor location to prevent incorrect material placement
- Updating a visual label that no longer reflects the current standard
- Adjusting a workstation height that had caused recurring operator strain
The defining criterion is that the improvement is within the operator's own authority to implement. Kaizen Teian does not require a supervisor sign-off, a team meeting, or a formal project charter. It requires observation, judgment, action, and documentation.
Why Kaizen Teian is the Most Neglected Kaizen Type
Most manufacturing organizations measure improvement activity by kaizen events completed rather than by total improvement contributions. This metric bias systematically undervalues Teian activity, which generates the highest volume of improvements across the facility but leaves the least visible footprint in tracking systems.
Toyota's production facilities have historically recorded over one million improvement suggestions per year across their workforce, with implementation rates above 90 percent. The competitive advantage this creates is not from individual improvements but from the compounding effect of thousands of small improvements applied continuously. [Kaizen Teian: Individual Improvement Suggestions] covers the submission-to-implementation process and recognition system design in full.
Key Insight: Kaizen Teian generates improvement volume that no event-based program can replicate. Organizations that measure only events are measuring the smallest fraction of their total improvement capacity.
Kaizen Events: Focused Team Improvement Within a Defined Window
A kaizen event, also called a kaizen blitz, is a structured improvement workshop in which a cross-functional team concentrates fully on a defined process problem for three to five days, with the goal of designing, testing, and implementing meaningful improvements before the event closes. Unlike Kaizen Teian, which is continuous and individual, a kaizen event is bounded, intensive, and team-based.
When to Deploy a Kaizen Event
Kaizen events are appropriate when the improvement opportunity meets several conditions:
- The problem scope is clearly defined and confined to a specific process area
- The root cause is understood well enough to make a solution achievable within the event window
- Cross-functional input is required, as the problem touches multiple roles, departments, or process steps
- The improvement requires coordination and testing that cannot happen within a single shift
- Measurable targets can be set before the event begins
Kaizen events are not appropriate for problems where the root cause is unknown, the scope is undefined, or the required change exceeds what a team can implement in five days. Deploying an event to a problem that belongs in a point kaizen or daily kaizen category wastes a cross-functional team on work an individual operator could address.
The Structure That Makes Kaizen Events Deliver
The three-to-five-day format is not arbitrary. Day one focuses on current state observation, data collection, and problem framing. Days two and three focus on improvement design, prototype testing, and iteration. Day four focuses on implementation of validated countermeasures. Day five closes with standard work documentation, results measurement, and sustainment planning. An event that ends without updated standard work and a defined sustainment check schedule has not completed the improvement cycle. It has completed the design phase only.
[Kaizen Events: Planning and Execution Guide] covers the full event structure including scope definition, team selection, facilitation techniques, and post-event sustainment.
Key Insight: A kaizen event that closes without updated standard work and a sustainment schedule has produced a prototype, not an improvement. The gain will revert within weeks.
Kaikaku: Radical Process Transformation
Kaikaku (改革) translates as "radical change" or "reform," and it describes improvement activity at a fundamentally different scale from daily kaizen or focused events. Where kaizen improves a process incrementally, kaikaku transforms it, changing the fundamental design, layout, technology, or workflow structure rather than refining what already exists.
What Kaikaku Addresses in Manufacturing
Kaikaku-level intervention is appropriate when incremental improvement has reached its ceiling. Common kaikaku scenarios in manufacturing include:
- Converting a functional batch production layout to cellular manufacturing flow
- Implementing a pull system and kanban replenishment where push scheduling previously operated
- Replacing manual inspection with automated detection systems at a quality control point
- Restructuring a value stream from end to end based on a future state value stream map
These changes cannot be achieved through daily kaizen or a single kaizen event. They require dedicated project planning, capital or significant resource allocation, and structured change management. The output of a successful kaikaku is a fundamentally different process that then becomes the new standard for daily kaizen and event-level improvement to build upon.
The Relationship Between Kaizen and Kaikaku
Hiroyuki Hirano, who formalized the 5S system and contributed extensively to lean production practice, articulated the operating principle clearly: kaikaku without a kaizen foundation produces transformation on an unstable base. The radical change arrives, but without the daily discipline and improvement culture that maintains it, the new process drifts toward the same waste conditions as the old one.
Kaikaku is most effective in organizations that have already built a functioning kaizen system, because those organizations have the improvement discipline to sustain what kaikaku creates.
Key Insight: Kaikaku is not an accelerated version of kaizen. It is a different intervention for a different problem scale, and it depends on an existing kaizen foundation to sustain its results.
Kakushin: Breakthrough Innovation Beyond Process Improvement
Kakushin (革新) occupies the far end of the improvement spectrum. It refers not to process transformation within an existing business model but to fundamental innovation that changes what the organization produces, how it competes, or how it creates value. In a manufacturing context, kakushin-level change might involve transitioning from mass production to mass customization, implementing a new production technology that makes existing process knowledge obsolete, or fundamentally repositioning the facility's product and market strategy.
Kakushin is rarely discussed in lean manufacturing operations because it operates at a strategic level beyond the scope of shop floor improvement programs. It is included here because understanding the full spectrum clarifies the boundaries of the kaizen system: kaizen, in all its forms from Teian to kaikaku, operates within the existing value creation model. Kakushin changes the model itself.
Key Insight: Kakushin changes what the organization does. Kaizen and kaikaku change how the organization does it. Confusing the two produces strategy deployed at operational scale or operations managed at strategic scale.
Point Kaizen vs System Kaizen: Scope Dimensions Across the Spectrum
Point kaizen and system kaizen are scope descriptors that apply across the primary kaizen types rather than representing separate types of their own. Understanding them helps improvement program managers avoid the common mistake of applying point-level tools to system-level problems.
Point Kaizen
Point kaizen addresses a single workstation, machine, or process step in isolation. It is fast, targeted, and highly executable. A Kaizen Teian improvement is almost always a point kaizen. A kaizen event targeting a specific assembly station is point kaizen at event scale.
Point kaizen is effective when the problem genuinely resides at a single point in the value stream. It produces misleading results when the problem is systemic, when the waste at one workstation is being generated by upstream conditions the point-level improvement cannot address.
System Kaizen
System kaizen addresses an end-to-end value stream or a significant portion of it. It requires understanding how processes connect, how information flows, and where systemic waste accumulates across multiple steps. Value stream mapping is the primary diagnostic tool for identifying where system kaizen is needed, and the improvement outputs from a system kaizen analysis typically initiate multiple point-level events or kaikaku projects.
[Kaizen Events: Planning and Execution Guide] covers how to scope events correctly so that point kaizen and system kaizen activity are distinguished before resources are committed.
Key Insight: Point kaizen applied to a system problem improves one node while the surrounding system continues generating the waste. The improvement disappears into the flow without changing the condition.
Selecting the Right Type: A Decision Framework
Matching improvement type to problem scale is the primary skill that separates effective improvement programs from activity-heavy programs with inconsistent results. The selection framework below organizes the decision by four criteria.
Problem scope:
- Single workstation, same-day fix → Kaizen Teian
- Defined process area, multi-role problem → Kaizen Event
- End-to-end value stream or layout redesign → Kaikaku
- Fundamental business model change → Kakushin
Resource requirement:
- No capital, operator authority → Kaizen Teian
- Cross-functional team, 3-5 days → Kaizen Event
- Capital investment, project planning → Kaikaku
Root cause clarity:
- Root cause known, solution obvious → Kaizen Teian or Event
- Root cause known, solution requires redesign → Kaikaku
- Root cause unknown → diagnose first using RCA before selecting improvement type
Urgency:
- Immediate safety or quality risk → point kaizen or rapid event
- Strategic performance gap → kaikaku with planned timeline
- Cultural and system-level improvement → sustained Kaizen Teian program
The [PDCA Cycle: The Foundation of Continuous Improvement] applies across all kaizen types. The cycle structure does not change. What changes is the scale at which it operates and the resources it requires.
Key Insight: Root cause clarity is the prerequisite for kaizen type selection. Committing to an event or kaikaku before the root cause is understood wastes the improvement resource and risks solving the wrong problem.
Within the Lean System
Connection to Lean Principles
The kaizen type spectrum directly operationalizes the fifth lean principle, pursuit of perfection, by providing a structured approach to improvement at every scale. Daily Kaizen Teian addresses perfection at the individual level. Kaizen events address it at the process level. Kaikaku addresses it at the value stream level. The [5 Core Principles of Lean Manufacturing] establish the goal; the kaizen types provide the implementation pathway at each level of the organization.
Connection to Lean Tools
Value stream mapping determines whether a problem requires point kaizen or system kaizen by making the full flow of waste and delay visible. [Value Stream Mapping: A Beginner's Complete Guide] is the primary diagnostic tool for identifying which kaizen type belongs at each point in the value stream. Standard work is the output that every kaizen type, from Teian to kaikaku, must produce to sustain its gains. Without updated standard work, improvements at any scale revert through normal operational variation.
Connection to Continuous Improvement
The [PDCA Cycle: The Foundation of Continuous Improvement] is the structural backbone that all kaizen types operate through, from the informal PDCA of a Kaizen Teian adjustment to the structured multi-week PDCA of a kaikaku project. [Kaizen Teian: Individual Improvement Suggestions] represents the daily execution layer of the kaizen type system, where the “continuous” in continuous improvement is most literally realized, not in events or transformation projects, but in the daily discipline of every operator improving their own work.
Frequently Asked Questions
What are the main types of kaizen in manufacturing? The main kaizen types are Kaizen Teian (daily individual improvements), kaizen events (focused three-to-five-day team workshops), kaikaku (radical process transformation), and kakushin (breakthrough innovation). Point kaizen and system kaizen describe the scope dimension that applies across these types. Each type is suited to a specific problem scale, and selecting the wrong type for the problem wastes resources without addressing the root condition.
What is the difference between kaizen and kaikaku? Kaizen refers to continuous incremental improvement within an existing process, small changes that compound over time. Kaikaku refers to radical transformation of the process itself, changing the fundamental design, layout, or technology rather than refining what exists. Kaizen is the foundation; kaikaku is the intervention for when incremental improvement has reached its ceiling. Kaikaku depends on an existing kaizen culture to sustain the transformation it creates.
When should a kaizen event be used instead of daily kaizen? A kaizen event is appropriate when the improvement requires cross-functional input, cannot be completed within a single shift, and has a defined scope with measurable targets. Daily kaizen handles problems within a single operator's authority with same-day resolution. When a problem touches multiple roles, process steps, or departments, and when coordination and testing are required, an event is the correct format.
What is the difference between point kaizen and system kaizen? Point kaizen addresses a single workstation or process step in isolation. System kaizen addresses an end-to-end value stream or a significant portion of the production system. Point kaizen is fast and targeted but produces misleading results when applied to problems generated by systemic upstream conditions. System kaizen requires value stream analysis to identify where waste is generated versus where it becomes visible.
How do you choose the right kaizen type for a manufacturing problem? Selection depends on four criteria: problem scope (single point vs. end-to-end), resource requirement (operator authority vs. capital investment), root cause clarity (known vs. requiring investigation), and urgency. Root cause clarity is the prerequisite. Committing to an event or kaikaku before the root cause is understood risks solving the wrong problem at significant resource cost.
LeanSuite: A complete lean manufacturing software
Schedule Demo
