Lean Six Sigma
What is Lean Six Sigma — DMAIC methodology and when to use Lean vs. Six Sigma?
Definition
Lean Six Sigma (LSS) combines two complementary approaches: Lean (which eliminates waste and improves flow) and Six Sigma (which reduces variation and defects using statistical methods). The combined approach follows the DMAIC cycle — Define, Measure, Analyze, Improve, Control — to systematically identify root causes and implement data-driven solutions. [src1]
Key Properties
- DMAIC phases: Define, Measure, Analyze, Improve, Control
- Lean focus: 8 wastes (TIMWOODS) — Transportation, Inventory, Motion, Waiting, Overproduction, Over-processing, Defects, Skills underutilization
- Six Sigma target: 3.4 defects per million opportunities at 6-sigma level
- Belt system: Yellow, Green, Black, Master Black Belt certification levels
- Typical ROI: 3-5x project cost within first year
Constraints
- Requires sufficient process data — minimum 30 data points for valid analysis [src4]
- Not suited for creative or one-time work — assumes stable, repeatable process [src3]
- Green Belt requires 2-3 weeks training; Black Belt requires 4-6 weeks plus project [src5]
- Diminishing returns beyond 4-5 sigma [src1]
- Cultural resistance is the #1 failure mode [src4]
Framework Selection Decision Tree
START — User needs to improve a business process
├── What type of problem?
│ ├── Waste, slow throughput, lead times → Lean ← START HERE
│ ├── Defects, high variation, quality → Six Sigma
│ ├── Both waste AND quality → Lean Six Sigma ← YOU ARE HERE
│ └── Innovation needed → Design Thinking (not LSS)
├── Is there data available?
│ ├── YES (≥30 data points) → Full DMAIC with statistics
│ └── NO → Start with Lean tools (VSM, 5S)
├── Process maturity?
│ ├── Chaotic → Lean first (standardize before optimizing)
│ ├── Defined but wasteful → Lean
│ ├── Stable but high defects → Six Sigma
│ └── Mature → LSS (combined)
└── Resources available?
├── Belt-certified team → Formal DMAIC project
└── No trained staff → A3 problem solving or Kaizen
Application Checklist
Step 1: Define — Scope the project
- Inputs needed: Problem statement, business case, CTQs, project charter
- Output: SIPOC diagram and project charter
- Constraint: If you cannot define the customer and CTQs, stop — not ready for DMAIC [src2]
Step 2: Measure — Quantify current performance
- Inputs needed: Process data, measurement system validation
- Output: Baseline metrics (capability, sigma level, yield)
- Constraint: Validate measurement system first (Gauge R&R) [src4]
Step 3: Analyze — Find root causes
- Inputs needed: Baseline data, process map, potential causes
- Output: Validated root causes through hypothesis testing
- Constraint: Do not skip to solutions — gut-feel causes are wrong 60-70% of the time [src2]
Step 4: Improve — Implement solutions
- Inputs needed: Validated root causes, solution alternatives, pilot plan
- Output: Pilot results showing improvement
- Constraint: Pilot before full rollout [src4]
Step 5: Control — Sustain the gains
- Inputs needed: Improved process, control plan, SPC charts
- Output: Control plan with response procedures
- Constraint: Without control, 70% of improvements revert within 18 months [src2]
Anti-Patterns
Wrong: Applying Six Sigma to an unstandardized process
Trying to reduce variation in a chaotic process is futile — no baseline to improve from. [src3]
Correct: Standardize with Lean first, then optimize with Six Sigma
Use 5S, standard work, and value stream mapping to create stability. Then apply statistical tools. [src5]
Wrong: Skipping the Control phase
Teams celebrate Improve results then move on. Without controls, processes drift back within 12-18 months. [src2]
Correct: Build control plans with SPC and response procedures
Define control limits, assign process owners, create response procedures, schedule quarterly audits. [src2]
Wrong: Using DMAIC for every problem
A broken light switch does not need a 6-month DMAIC project. Methodology fatigue wastes resources. [src4]
Correct: Match method to problem complexity
Kaizen events for simple problems, A3 for medium, full DMAIC for complex data-rich problems. [src3]
Common Misconceptions
Misconception: Lean and Six Sigma are the same thing with different names.
Reality: Lean focuses on speed and waste elimination; Six Sigma focuses on quality and variation reduction using statistics. They are complementary. [src3]
Misconception: Six Sigma means zero defects.
Reality: Six Sigma targets 3.4 defects per million — not zero. True zero is statistically impractical and economically irrational. [src1]
Misconception: Only manufacturing benefits from LSS.
Reality: LSS is applied in healthcare, financial services, software development, and any organization with repeatable processes. [src4]
Comparison with Similar Concepts
| Concept | Key Difference | When to Use |
|---|---|---|
| Lean Six Sigma | Combines waste elimination + variation reduction | Complex process problems with data |
| Lean (standalone) | Waste elimination and flow | Speed and throughput problems |
| Six Sigma (standalone) | Statistical variation reduction | Quality defects with sufficient data |
| Kaizen | Rapid team-based improvement (1-5 days) | Quick wins on simple problems |
| TQM | Organization-wide quality culture | Broad quality transformation |
When This Matters
Fetch this when a user asks about process improvement methodology, DMAIC phases, choosing between Lean and Six Sigma, continuous improvement frameworks, or reducing defects and waste in business processes.