Study guide
8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE
ASQ Certified Six Sigma Black Belt CSSBB
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CSSBB Exam Strategy
1.1 CSSBB Exam Format, Scoring, and Testing Windows 1.2 Eligibility, Project Affidavits, Application, and Recertification 1.3 Open-Book Strategy, Reference Materials, and a 16-Week Study Plan
2 Chapter 2: Organization-Wide Planning and Deployment
2.1 Fundamentals of Six Sigma and Lean Methodologies 2.2 Selecting the Right Methodology: DMAIC, DFSS, and Lean 2.3 Business Systems, Processes, and Stakeholder Relationships 2.4 Strategic Planning and Deployment of Six Sigma Initiatives 2.5 Six Sigma Roles and Responsibilities 2.6 Organizational Barriers and Common Causes of Six Sigma Failure 2.7 Change Management: Stakeholder Analysis, Readiness, and Communication
3 Chapter 3: Organizational Process Management and Measures
3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders 3.2 Benchmarking Types and Performance Goal Setting 3.3 Performance Measures: Balanced Scorecard, KPIs, KBIs, OKRs, and Line of Sight 3.4 Leading and Lagging Indicators and Performance Dashboards 3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis 3.6 Cost of Poor Quality and Hard versus Soft Savings
4 Chapter 4: Team Management
4.1 Team Types and Constraints 4.2 Team Roles, Responsibilities, and Member Selection 4.3 Team Success Factors and Ground Rules 4.4 Motivational Techniques and Overcoming Demotivators 4.5 Stages of Team Development and Conflict Resolution 4.6 Team Communication Plans 4.7 Team Leadership Models: Direct, Coach, Support, and Delegate 4.8 Group Behaviors, Conflict Resolution, and Meeting Management 4.9 Facilitation Techniques and Team Decision-Making Methods 4.10 Team Training: Needs Assessment, Delivery, and Evaluation
5 Chapter 5: Define Phase
5.1 Customer Identification and Segmentation 5.2 Customer Data Collection: Methods, Validity, and Reliability 5.3 Customer Requirements: CTX, CTQ Trees, and Operational Definitions 5.4 The Kano Model and Quality Function Deployment 5.5 SIPOC and Process Mapping 5.6 Business Case Justification 5.7 The Project Charter and the Problem Statement 5.8 Project Scope and Boundaries 5.9 SMART Goals and Project Performance Measurements 5.10 Project Charter Reviews and Toll-Gate Governance 5.11 Project Management Tools: Gantt Charts, Toll-Gate Reviews, WBS, and RACI 5.12 Analytical Tools Used Throughout the DMAIC Cycle
6 Chapter 6: Measure Phase
6.1 Process Flow Metrics and the Hidden Factory 6.2 Process Analysis Tools and Value Stream Mapping 6.3 Types of Data and Measurement Scales 6.4 Sampling Concepts, Methods, and Sample Size for Estimation 6.5 Data Collection Plans and Common Pitfalls 6.6 Gage R&R for Variable Measurement Systems 6.7 Attribute Agreement Analysis and Audit MSA 6.8 Measurement Systems Across the Organization, and Metrology 6.9 Population Parameters, Sample Statistics, and Valid Statistical Conclusions 6.10 Descriptive Statistics: Central Tendency, Dispersion, and Shape 6.11 Graphical Methods for Exploratory Data Analysis 6.12 Probability Concepts, Common Distributions, and the Central Limit Theorem 6.13 Additional Distributions: Hypergeometric, Exponential, Lognormal, Weibull, and Bivariate 6.14 Process Capability and Performance Indices 6.15 Capability Studies, Attributes Capability, Yield Metrics, and Long-Term Capability
7 Chapter 7: Analyze Phase
7.1 The Correlation Coefficient, Its Confidence Interval, and Causation 7.2 Linear Regression and Residual Analysis 7.3 Multivariate Tools: Factor Analysis, Discriminant Analysis, and MANOVA 7.4 Hypothesis Testing Terminology, Errors, and Single-Sample Tests 7.5 Statistical Versus Practical Significance 7.6 Sample Size for Hypothesis Tests 7.7 Point Estimates, Confidence, Prediction, and Tolerance Intervals 7.8 Tests for Means, Variances, and Proportions 7.9 Analysis of Variance 7.10 Chi-Square Goodness-of-Fit and Tests of Independence 7.11 Types of Risk and Failure Mode and Effects Analysis 7.12 Gap Analysis and Root Cause Analysis 7.13 Waste Analysis: The Seven Classic Wastes and Resource Under-Utilization
8 Chapter 8: Improve Phase
8.1 Design of Experiments: Objectives, Terminology, and Effects 8.2 DOE Design Principles: Randomization, Blocking, Replication, and Resolution 8.3 Planning and Evaluating Designed Experiments 8.4 One-Factor Experiments: Completely Randomized, Randomized Block, and Latin Square Designs 8.5 Full Factorial Experiments and Design Selection 8.6 Two-Level Fractional Factorial Experiments and Confounding 8.7 Response Surface Methodology and Optimization 8.8 Waste Elimination: Pull Systems, Kanban, 5S, and Poka-Yoke 8.9 Cycle-Time Reduction: Continuous Flow, SMED, and Heijunka 8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE 8.11 Implementation Planning, Piloting, and Solution Selection
9 Chapter 9: Control Phase
9.1 SPC Objectives, Variable Selection, and Rational Subgrouping 9.2 Control Charts for Variables Data 9.3 Control Charts for Attributes Data 9.4 Short-Run SPC and Moving Average Charts 9.5 Control Chart Analysis: Common Cause, Special Cause, and Run Rules 9.6 Total Productive Maintenance and Visual Controls 9.7 Measurement System Reanalysis 9.8 Control Plan Development and Process Owner Handoff 9.9 Lessons Learned, Documentation, and Training for Sustainment 9.10 Ongoing Evaluation of the Improved Process
10 Chapter 10: Design for Six Sigma (DFSS)
10.1 DFSS Frameworks: DMADV, DMADOV, and Design Transfer 10.2 Design for X (DFX) 10.3 Robust Design, Parameter Design, and Verification 10.4 Tolerance Design and Statistical Tolerancing
8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE
Key Takeaways Explain This Topic AI
Kaizen is continuous incremental improvement by everyone; a kaizen blitz is a focused three-to-five-day event with a dedicated team.
A kaizen blitz suits a bounded, well-understood problem where the solution is largely known and implementation is the constraint.
The theory of constraints five focusing steps are identify, exploit, subordinate, elevate, and repeat without letting inertia become the constraint.
OEE is availability times performance times quality, and world-class is conventionally 85%.
Improvement anywhere other than the constraint produces no increase in system throughput.
Last updated: August 2026
- Kaizen and kaizen blitz
- Kaizen means change for the better. As a management practice it is continuous, incremental
- improvement performed by everyone as part of normal work: small changes, suggested and implemented
locally, accumulating over years.
Kaizen blitz (also kaizen event or rapid improvement event) is a concentrated, time-boxed attack on
one bounded problem by a dedicated cross-functional team, typically over three to five consecutive days.
- Kaizen Kaizen blitz
- Duration Ongoing, permanent 3-5 days
- Participants Everyone, in their own work Dedicated team, released from normal duties
- Scope Small, local One bounded process or cell
- Investment Minimal Team time; small capital pre-approved
- Output Many small improvements over time Implemented change by the end of the week
- Best for Sustaining a culture of improvement Breaking through a known problem quickly
- When to use which
- Choose a blitz when the problem is bounded and physically visible, the solution is largely known or
- easily discoverable by observation, implementation rather than analysis is the constraint, and the
people who do the work can be released for a week.
Choose DMAIC instead when the cause is genuinely unknown, the answer requires statistical analysis of
data that must be collected over time, or the process spans several functions and sites.
Choose ongoing kaizen when the aim is a stream of small improvements and cultural change rather than
a step change.
- A typical blitz week: Monday train the team and map the current state at the gemba; Tuesday collect data
- and analyze waste; Wednesday design the future state and start physically changing the process; Thursday
- implement, trial, and adjust; Friday standardize, write the new standard work, train the shift, and
present results.
- Two failure modes are common. Blitzes are run on problems whose causes are unknown, and the team
- implements a plausible but wrong solution in a week. And gains are not sustained because the new standard
- work was never audited -- a blitz needs a 30-day follow-up with a named owner as part of its
definition of done.
- Theory of constraints
- Developed by Eliyahu Goldratt, TOC holds that every system has at least one constraint that limits
its throughput, and that improvement anywhere else produces no system gain.
- The five focusing steps
- Identify the constraint. Look for the step with the longest cycle time, the highest utilization,
and inventory accumulating immediately in front of it.
- Exploit the constraint. Get everything possible from it without capital spend: never let it idle,
- run it through breaks and shift changes, do not process defective material on it, move setup work off
it, and inspect before it so it never works on scrap.
- Subordinate everything else to the constraint. Non-constraint resources should run at the
- constraint's pace, not their own. This is counter-intuitive because it means deliberately leaving
non-constraint equipment idle, and it conflicts directly with local utilization metrics.
Elevate the constraint. Now spend money: add capacity, buy equipment, outsource, add a shift.
Repeat. Once the constraint is broken, another becomes binding. Go back to step 1, and do not
let inertia become the constraint -- policies written for the old constraint frequently outlive it.
- The key implications
- Throughput of the system equals throughput of the constraint. An hour lost at the constraint is an
hour lost by the whole system; an hour saved at a non-constraint is worth nothing.
Local efficiency metrics are actively harmful. Measuring non-constraint machines on utilization
drives overproduction, which creates inventory and hides problems.
- Buffer the constraint. A small protective inventory in front of the constraint prevents it from
- starving; this is the drum-buffer-rope scheduling mechanism, where the constraint is the drum that
sets the pace.
TOC and lean are complementary rather than competing. Lean seeks to eliminate waste everywhere; TOC says
sequence that work by starting where it changes throughput.
- Overall equipment effectiveness
- OEE is a single measure of how much of the theoretically available production time is genuinely
productive. O E E = Availability × Performance × Quality OEE = \text{Availability} \times \text{Performance} \times \text{Quality} OEE = Availability × Performance × Quality
- Component Formula Losses it captures
- Availability Run time / Planned production time Breakdowns, setup and changeover
- Performance (Ideal cycle time x Total count) / Run time Minor stops, reduced speed
- Quality Good count / Total count Scrap, rework, startup rejects
- These are the six big losses : breakdowns and setup (availability), minor stoppages and reduced speed
(performance), process defects and startup losses (quality).
Worked example. A shift has 480 planned minutes, 60 minutes of downtime, produces 900 units at an
ideal cycle time of 0.4 minutes per unit, with 45 rejects.
Run time = 480 − 60 = 420 = 480 - 60 = 420 = 480 − 60 = 420 min. Availability = 420 / 480 = 0.875 = 420 / 480 = 0.875 = 420/480 = 0.875 .
Performance = ( 0.4 × 900 ) / 420 = 360 / 420 = 0.857 = (0.4 \times 900) / 420 = 360 / 420 = 0.857 = ( 0.4 × 900 ) /420 = 360/420 = 0.857 .
Quality = ( 900 − 45 ) / 900 = 855 / 900 = 0.950 = (900 - 45) / 900 = 855 / 900 = 0.950 = ( 900 − 45 ) /900 = 855/900 = 0.950 . O E E = 0.875 × 0.857 × 0.950 = 0.712 OEE = 0.875 \times 0.857 \times 0.950 = 0.712 OEE = 0.875 × 0.857 × 0.950 = 0.712
An OEE of 71.2%. The convention is that 85% is world class (roughly 90% availability, 95%
performance, 99% quality), and that typical manufacturing runs around 60%.
- Reading OEE correctly
- Never report OEE as a single number without its three components. The same 71% can arise from
- chronic breakdowns or from a quality problem, and the actions are completely different. Here the
binding losses are availability and performance, not quality.
- The denominator matters. OEE is normally computed against planned production time, which
- excludes scheduled non-production such as unstaffed shifts. Computing against all 1,440 minutes in a
day gives Total Effective Equipment Performance (TEEP), a different and much lower measure.
- OEE is a loss-analysis tool, not a target. Chasing an OEE number on a non-constraint machine
- produces overproduction, which is exactly what TOC warns against. Measure OEE at the constraint ,
where every recovered minute becomes system throughput.
That last point is the connection between the two frameworks: TOC tells you where to improve, and OEE
tells you what the loss consists of once you are there.