Lean Six Sigma (LSS) combines two distinct improvement traditions. Lean, derived from the Toyota Production System, focuses on waste elimination and value-stream flow. Six Sigma, originating at Motorola in the 1980s, focuses on statistical variation reduction and defect prevention. The combined methodology is most often associated with the DMAIC cycle: Define, Measure, Analyze, Improve, Control.
At enterprise scale, with formal Black Belt programs and full DMAIC projects, LSS produces measurable results. Inside a $10M to $100M operator without a dedicated continuous-improvement function, the formal methodology is overhead. The principles are valuable; the ceremony is not.
The principles that earn their cost.
- Value-stream mapping. Walk the actual process, end to end, on paper. Identify which steps add customer value and which don't. Most LMM operators have never seen their process drawn, and the act of drawing it surfaces 30% of the waste.
- Variation reduction at the hand-off. Apply Six Sigma's variation discipline only to the few processes where consistency matters most, typically anything customer-facing or compliance-related.
- Standard work documentation. The Toyota practice of writing down the current best-known way to perform a task. Not aspirational. Current.
- Visual management. Make the operating state visible in the workspace, kanban boards, daily metrics on the wall, andon-style alerts when something exceeds threshold.
- Pull, not push. Work flows when downstream is ready, not when upstream finishes. Eliminates the queue waste that compounds at hand-offs.
Where the methodology becomes overhead.
- Formal belt certifications. Time and money better spent on operating against the principles than on credentialing.
- Multi-month DMAIC projects with steering committees. Smaller teams move faster with shorter improvement cycles. Apply DMAIC as a private mental model, not a project structure.
- Heavy statistical tooling. Most LMM processes don't have enough volume for control charts to mean what they mean at scale. A run chart you actually look at beats an SPC chart nobody opens.
- Cross-functional kaizen events as standalone deliverables. The kaizen event becomes a deck. Embed the principles in daily operating cadence instead.
LSS as a private discipline, not a label.
Inside an Axis Method engagement we apply LSS principles without naming them, because naming them invites ceremony. The Stabilize phase is functionally a value-stream mapping exercise. The Document phase produces standard work. The Hand-off phase installs visual management and the cadence that produces continuous improvement after we leave. Toyota's distinction matters here: continuous, daily, small improvement (kaizen) beats episodic, large project-based change. LMM operators win on consistency, not on transformation.
See also.
- The Axis Method, where LSS principles are applied without the ceremony
- Lean Six Sigma for the LMM, without the BS, what to keep, what to drop
- Operational excellence, the broader discipline LSS supports
Talk through it.
If any of this is relevant to where you are, book a 30-minute scoping call. No pitch deck.