2.1 Fundamentals of Six Sigma and Lean Methodologies
Key Takeaways
- Six Sigma targets variation reduction and defect elimination; lean targets waste elimination and flow-time reduction, and the two are complementary rather than alternatives.
- Six sigma capability means a process mean six standard deviations from the nearest specification limit, equating to 3.4 defects per million opportunities after the conventional 1.5-sigma long-term shift.
- Lean's core measures are flow-based -- lead time, cycle time, takt time, and work in process -- while Six Sigma's are variation-based, such as Cpk, DPMO, and sigma level.
- Lean Six Sigma maturity models typically progress through five levels from ad hoc firefighting to an integrated, self-sustaining improvement culture.
- ASQ tests this topic at the Understand level, so the exam asks you to characterize and compare the methodologies rather than to compute anything.
Two different enemies
Six Sigma and lean are often bundled together, but they were built to attack different problems, and the CSSBB exam expects you to keep the distinction crisp.
Six Sigma is a disciplined, data-driven methodology for reducing variation and eliminating defects. Its intellectual foundation is statistical: characterize the process output $Y$ as a function of controllable inputs, $Y = f(X_1, X_2, \ldots, X_n)$, identify the vital few $X$s that drive variation in $Y$, and control them. Its signature deliverable is a process whose output distribution sits comfortably inside the customer's specification window.
Lean is a methodology for maximizing customer value by systematically eliminating waste and compressing flow time. Its intellectual foundation is operational: define value from the customer's perspective, map the value stream, make value flow without interruption, let the customer pull, and pursue perfection. Its signature deliverable is a shorter, smoother, less inventory-heavy process.
| Dimension | Six Sigma | Lean |
|---|---|---|
| Primary enemy | Variation and defects | Waste and delay |
| Primary question | Why is the output inconsistent? | Why does this take so long? |
| Core measures | Cpk, DPMO, sigma level, $p$-values | Lead time, cycle time, takt time, WIP, OEE |
| Typical tools | MSA, hypothesis testing, DOE, SPC | Value stream mapping, 5S, kanban, SMED, poka-yoke |
| Typical project length | 3-6 months, data-intensive | Days to weeks, often a kaizen event |
| Decision basis | Statistical significance | Direct observation at the gemba |
What "six sigma" means numerically
The name is a capability statement. A process operating at six sigma has its mean six standard deviations from the nearest specification limit. In the short term that corresponds to about 0.002 defects per million opportunities. The familiar 3.4 DPMO figure comes from the industry convention that a process mean drifts by up to $1.5\sigma$ over the long term:
so a $6\sigma$ short-term process behaves like a $4.5\sigma$ process in the long run, giving 3.4 DPMO. Candidates who cannot reconcile "six sigma" with 3.4 DPMO are almost always forgetting the shift.
Why they are complementary
Neither methodology can finish the job alone.
- A lean transformation that removes buffer inventory exposes variation. Without Six Sigma's variation reduction, a one-piece-flow cell with an unstable upstream step simply stops more often.
- A Six Sigma project that centers a process and halves its standard deviation does nothing about the three days the work spends sitting in a queue. Without lean, defect-free work can still be slow and expensive.
The integration point is practical: lean tools dominate the Improve phase (VII.B in the Body of Knowledge is entirely lean methods), lean flow metrics dominate the Measure phase's process characteristics (V.A.1), and waste analysis is an Analyze-phase method (VI.D.3). A Black Belt runs one methodology -- DMAIC -- with both toolkits available.
Value and goals
| Goal | How Six Sigma delivers it | How lean delivers it |
|---|---|---|
| Lower cost | Reduces cost of poor quality: scrap, rework, warranty | Reduces inventory carrying cost, floor space, overproduction |
| Faster delivery | Removes rework loops that inflate cycle time | Removes queues, batching, and transport |
| Higher customer satisfaction | Delivers to specification consistently | Delivers on time and responds to demand changes |
| Better capital use | Fewer capacity losses to defects | Less working capital tied up in WIP |
Both converge on the same financial claim: improvement funded by the cost of poor quality already being paid.
Lean Six Sigma maturity models
A maturity model describes where an organization sits on the road from ad hoc problem solving to a self-sustaining improvement culture. Models vary by publisher, but the five-level shape is conventional and the exam expects you to recognize it.
| Level | Name | Characteristics |
|---|---|---|
| 1 | Ad hoc / reactive | Firefighting, no common method, improvement depends on individuals |
| 2 | Initiating / defined | Belts trained, projects chartered, tools applied inconsistently |
| 3 | Managed / repeatable | Standard DMAIC governance, toll gates, project portfolio, financial validation |
| 4 | Integrated / strategic | Projects selected from strategic goals, process owners accountable for control plans |
| 5 | Optimizing / cultural | Continuous improvement is routine work, everyone participates, gains sustain without belt involvement |
Reading the model matters because it dictates project selection. In a Level 1 or 2 organization the binding constraint is usually data availability and management support, so early projects should be visible, fast, and easy to measure. In a Level 4 organization the binding constraint is usually cross-functional coordination, so projects should be scoped across the value stream rather than inside one department.
Exam framing
ASQ tags I.A.1 at the Understand level. Expect questions that ask you to identify which methodology owns a given goal, to recognize why lean and Six Sigma reinforce each other, or to place a described organization on a maturity model. You will not be asked to compute a sigma level here -- that lives in Measure (V.F).
A plant has stable, in-specification product quality but a 14-day order-to-delivery lead time driven by batching and queues between departments. Which methodology most directly addresses the problem?
Why does a process described as operating at six sigma capability conventionally correspond to 3.4 defects per million opportunities rather than roughly 0.002?
An organization has trained belts and charters projects, but tool use is inconsistent, there is no standard toll-gate governance, and financial benefits are not validated. Where does it sit on a typical five-level lean Six Sigma maturity model, and what does that imply for project selection?