Lean attacks waste and slow flow; Six Sigma attacks variation and defects. How to tell which problem you have, why most operations have both, and how to combine the two without creating competing programs.
Two plants in the same group started improvement programs in the same year. One chose Lean: it reorganised into cells, cut inventory by half and halved lead time, but its scrap rate barely moved because the moulding process itself was unstable. The other chose Six Sigma: it ran excellent statistical projects that cut defects on its worst products, but its lead time stayed at five weeks, because nobody looked at the queues between departments. Each plant fixed exactly half of its problem.
The choice between Lean and Six Sigma is usually a false one.
What each is built to do
- Lean focuses on flow and waste. It asks: where is time being lost between value-adding steps, and how do we make work flow to customer demand? Its tools include value stream mapping, 5S, standard work, SMED, cells and pull systems.
- Six Sigma focuses on variation and defects. It asks: why does this process sometimes produce bad output, and how do we make it consistently good? Its backbone is the DMAIC method, supported by measurement system analysis, statistics and designed experiments.
How to tell which problem you have
Look at the symptom:
- Long lead times, high inventory, lots of waiting and handling, frequent expediting: a flow problem. Start with Lean.
- Scrap, rework, customer complaints, a process that behaves differently from day to day: a variation problem. Start with Six Sigma.
- Simple, obvious problems with an obvious fix: neither. Just fix them.
Why most operations need both
In practice, the two problems feed each other. Unstable processes force buffers of inventory and long lead times, which is a Lean problem caused by variation. Long batches and queues hide defects for days before anyone notices, which is a quality problem made worse by poor flow. Fixing one exposes the other.
There is also a sequencing logic. Lean often goes first because it is faster, visible and engages people quickly: 5S, standard work and better flow stabilise the environment. Six Sigma then tackles the chronic variation that remains, using data the now-stable process makes trustworthy.
Combining them without creating two programs
- One program, one governance structure, one project pipeline. Avoid separate Lean and Six Sigma teams competing for the same people and credit.
- Choose the tool to fit the problem, not the problem to fit the tool. A well-run program has kaizen events, DMAIC projects and simple just-do-it fixes side by side.
- Train people in both toolkits, at the right depth for their role.
- Measure outcomes the business cares about: lead time, cost, quality, delivery and safety, not the number of projects completed.
A practical starting point
Map one value stream. The map will show both kinds of problem: kaizen bursts for flow, and quality issues that need data. Prioritise by business impact, assign each to the right method and start.
The question is never "Lean or Six Sigma?" It is "what is really stopping this process from delivering, and which tool will fix that fastest?"
