Lean & Six Sigma

Lean and Six Sigma get bundled together so routinely that the distinction gets lost — and the distinction is the useful part.

Lean attacks waste. Work that consumes time, space, material or attention without adding value the customer would pay for: overproduction, waiting, unnecessary transport, overprocessing, excess inventory, unnecessary motion, defects, and unused talent. Lean asks why are we doing this at all?

Six Sigma attacks variation. Output that is inconsistent even when nothing has obviously gone wrong. Six Sigma asks why is this not the same every time? and answers with data.

They matter because the diagnosis determines the treatment. A process producing consistently poor output has a capability problem — Six Sigma work. A process producing acceptable output through excessive effort has a waste problem — Lean work. Applying the wrong toolkit is one of the most common ways improvement programmes consume budget without moving the numbers.

• Value stream mapping — seeing the whole flow, including the waiting time between steps where most of the lead time usually hides
• Waste identification across the eight categories
• Statistical process control (SPC) — control charts that distinguish normal process variation from a genuine signal
• Process capability analysis — whether the process can actually meet the specification, which is a different question from whether it did today
• Error-proofing (poka-yoke) — designing the mistake out rather than training people to avoid it
• KAIZEN events — focused, time-boxed improvement with the people who do the work
• Overall Equipment Effectiveness (OEE) — availability, performance and quality in one measure
• 5S and workplace organization, where it serves a purpose rather than as an end in itself
• Setup and changeover reduction, which is often the cheapest route to capacity
• Root cause tools — Pareto, Ishikawa, 5 Why, hypothesis testing

The SPC point deserves emphasis because misreading variation is so common. Reacting to every fluctuation as though it were a problem — tampering — actively increases variation. Learning which movements are signal and which are noise is frequently the single most valuable thing a production team takes from this work.

Training on your processes, not on case studies. Generic Six Sigma training produces people who can pass an exam and cannot start a project. We teach the tools against your parts, your lines and your data, so the training output is a live project rather than a certificate.

We work through cross-functional teams including the operators, because they hold information no dataset contains. We insist on a measured baseline before changes are made, and on verification against that baseline afterwards — otherwise everyone leaves believing it worked and nobody can prove it.

Then we document and proceduralize the improved process. This is where most Lean Six Sigma work quietly fails: the project closes, the team disperses, the old method reasserts itself because it is still the path of least resistance, and within a year the gain is gone. Locking it into the documented system is the difference between an improvement and an anecdote.

This capability is also the engine inside our guaranteed bottom-line improvement programme, and it draws on the same core tools automotive clients need for IATF 16949.

• Waste removed from the value stream — shorter lead times, less inventory, less handling
• Variation reduced and held, with capability demonstrated rather than asserted
• Fewer defects, and defects caught by design rather than by inspection
• Capacity released — usually from changeover reduction and downtime, without capital spend
• A team that can run the tools without us
• Decisions settled by data rather than by whoever argues most forcefully

That final point is culturally the most significant. In operations without this capability, process arguments are resolved by seniority and confidence. Once teams can measure, the arguments end faster and land in better places.

We bring 30+ years and 900+ organizations to this work.

• Applying Lean to a variation problem or Six Sigma to a waste problem — diagnose before treating
• Tampering — adjusting the process in response to normal variation, which increases variation
• Training that uses generic case studies, producing certified people who cannot start a real project
• No measured baseline, so results cannot be demonstrated
• Improvements never documented, so they decay within a year
• 5S treated as the goal rather than as support for flow — a tidy plant that still cannot deliver
• Excluding operators from teams, then wondering why the analysis missed the obvious
• Belt certification as the objective instead of results — counting trained people rather than money saved
• Chasing statistical sophistication when the problem is visible on the floor