Follow one piece of work from start to finish and record where it moves and where it waits. Almost every first map shows hours of actual work spread across weeks of elapsed time. Lean goes after that gap: queues, handoffs, batching, rework, and the approvals nobody can justify.
L6S explained
L6S: what it stands for, and what it actually does
L6S is shorthand for Lean Six Sigma. Here is what the abbreviation means, where each half came from, what the number six is doing in it, and the tests that tell you whether it is the right tool for the problem in front of you.
Chapter 1
What L6S stands for
L6S stands for Lean Six Sigma. It is the abbreviation practitioners write once they have typed the full phrase enough times, and it turns up in job adverts, project charters and belt certificates alongside two other spellings of the same thing: LSS, and Lean 6 Sigma. Nothing changes between them. If one role asks for an L6S Black Belt and another asks for a Lean Six Sigma Black Belt, they are asking for the same person.
The full phrase is a compound of two movements that spent twenty years apart before anyone bolted them together. Lean came out of Toyota and asks one blunt question of every step in a process: would the customer pay for this? Six Sigma came out of Motorola in the mid 1980s and asks a different blunt question: how much does this process vary, and how often does that variation reach the customer as a defect?
Put crudely, Lean makes work flow and Six Sigma makes it correct. L6S is the recognition, arrived at in the late 1990s, that an organisation almost never has only one of those two problems.
Chapter 2
Two halves, two different arguments
Measure the same step many times and it gives you a distribution, not a number. Six Sigma treats that spread as the enemy, finds which inputs drive it, and proves the link with data rather than opinion. Its discipline is that a cause is not a cause until the numbers say so.
Six Sigma alone perfects steps that should not exist, at great expense and over many months. Lean alone speeds up a process that still produces the wrong answer, then wonders why the complaints did not fall. Running both is not a compromise. It is the minimum honest response to a real operation.
The value of L6S is less in the individual tools, most of which predate it, than in the order it insists on: define the problem before measuring it, measure before analysing, analyse before changing anything, and control the change before calling it a win.
Chapter 3
Where the number six comes from
Sigma, written , is the statistical symbol for standard deviation: the ordinary spread of a process around its own average. Every real process has one. The question Six Sigma asks is how that spread compares with what the customer will tolerate.
If the tolerance is six standard deviations wide on each side of the target, ordinary variation almost never reaches the edge. That is the whole of the idea. The number attached to it is 3.4 defects per million opportunities, usually written 3.4 DPMO, and it is worth knowing where that figure comes from, because it is not the textbook probability of a six sigma breach.
A perfectly centred normal process at six sigma would produce roughly two defects per billion, not 3.4 per million. The published figure carries a deliberate allowance of 1.5 sigma for the way real process averages drift over months, an assumption introduced at Motorola and inherited by everyone since. It is a convention, not a law of nature, and a practitioner who cannot tell you that is repeating a slogan.
The useful version of the number, for most organisations, is simpler. Almost nobody arrives at the first meeting knowing their defect rate at all. Measuring it honestly, once, is usually worth more than the entire argument about which sigma level to aim for.
Chapter 4
DMAIC: the five steps an L6S project walks
Improvement projects fail in predictable places, and DMAIC is the sequence built to block each one. Define states the problem, the customer and the boundary, and it is where most projects are quietly lost, because a problem defined as "the department is underperforming" can be neither measured nor finished. Measure establishes the baseline, and the rule is that the baseline is collected before anything changes, not reconstructed afterwards from memory.
Analyse looks for the causes and tests them. This is the phase people skip, because by then everyone in the room already believes they know the answer, and it is also the phase that decides whether the project produces a genuine gain or an expensive coincidence. Improve designs the change, pilots it, and measures it against the baseline. Control is the phase that separates L6S from a workshop: the new way is documented, the measurement continues, and somebody owns the chart that will show if it slips back.
There is a sister sequence, DMADV, for when the process does not exist yet or is beyond repair: Define, Measure, Analyse, Design, Verify. Choosing between them is an early decision with real consequences, and the tell is simple. If the current process could meet the requirement when it behaves, improve it. If it could not meet the requirement even on its best day, design a new one.
Chapter 5
Belts, and what they are actually worth
Understands the vocabulary, can contribute to a mapping session and collect data without corrupting it. A few days of training. Genuinely useful across a whole workforce.
Leads improvement work inside their own area alongside the day job, usually a project of three to six months. The workhorse of most L6S programmes.
Handles cross functional problems and the statistics that come with them, and coaches green belts. The step up is as much political as technical, because these projects cross departments that do not report to each other.
Designs the improvement system, coaches the black belts, and answers for whether the method is being applied honestly. Rare, and the level at which the awkward question, whether a project should exist at all, is supposed to be asked.
Chapter 6
When L6S is the wrong tool
A method is only trustworthy when its limits are stated by the people selling it. L6S has four worth naming.
The first is novelty. DMAIC improves a process that already runs. If the thing does not exist yet, if the market is unknown, or if the answer is a genuine invention, the measure phase has nothing to measure and the rigour becomes theatre. Design work needs design methods.
The second is speed. If the building is on fire, stabilise it first. A structured project running in parallel is fine. A structured project instead of the fire extinguisher is negligence.
The third is the variation worth keeping. Not every difference in how people work is waste. Judgement at a hospital bedside, care in a difficult conversation, craft in a piece of design: standardise those into a script and you get compliant, hollow work. The test is never whether a thing can be standardised, but whether the variation in it harms the customer or serves them.
The fourth is not a limit of the method but of how it gets bought. An organisation that trains three hundred people, certifies them, and then frees nobody to finish a project has bought certificates. It is the most common way L6S fails in Britain, and it has nothing to do with the statistics.
Chapter 7
L6S questions people actually ask
Yes. L6S is written shorthand for Lean Six Sigma, the same method under a shorter name. You will also see it written LSS and Lean 6 Sigma. They all mean the discipline that fuses Lean, which attacks waste and delay, with Six Sigma, which attacks variation and defects.
No. Six Sigma on its own is the statistical half: reduce variation until defects are rare. Lean on its own is the flow half: remove everything the customer would not pay for. L6S is the combination, and the combination exists because each half fails at what the other is good at. Six Sigma can perfect a step nobody should be doing. Lean can speed up a process that is still producing the wrong answer.
Sigma is the statistical symbol for standard deviation, the ordinary spread of a process. A six sigma process is one where the customer tolerance is six standard deviations wide on each side of the target, so ordinary variation almost never breaches it. The familiar figure of 3.4 defects per million opportunities comes from that idea with a 1.5 sigma allowance for long term drift built in.
No. The belts are a training ladder, not a licence. A team leader who can walk a process, count the waiting time and plot a run chart is already doing useful L6S. The belt matters when an organisation needs to know who can lead a project, coach others and be trusted with the statistics.
A focused kaizen event runs in a week. A green belt project usually runs three to six months, because the measure phase has to wait for real data to accumulate. A black belt project on a cross functional problem can take longer. Anyone promising a structural improvement in a fortnight is selling a workshop, not a project.
The branding dated badly. The mechanics did not. Every claim L6S makes about queues, variation and measurement is still true, and the newer disciplines that replaced it in fashion, agile delivery and operational analytics among them, rediscovered most of it. The honest position is that L6S is a toolkit with a reputation earned by bad practitioners, and the tools themselves are sound.
Chapter 8
Where to go next
The practice in full
Lean Six Sigma: what it is, what it fixes, what it takes
The pillar page for the term written out: what an engagement involves, what it takes in time and people, and where it earns its keep.
The longer argument What is Lean Six Sigma, and when is it the wrong tool?The essay version of this page, with the cases where the method should be turned down.
Start further back What are processes?The plain language guide to the thing L6S operates on, including the queueing maths behind most delay.
The method under load Meridian Hospital GroupA full case study: the problems stated in the open, and each solution graded rather than sold.
The core chart Statistical Process ControlThe chart everyone draws and half misuse, which is where the Control phase either holds or fails.
The small version KaizenSmall improvements compounded, and the two ways organisations get them wrong.
The practitioner About Vincent Chido KingMaster Black Belt, and what that level is actually accountable for.
Put L6S to work on a real process
A discovery call is free, and the first useful thing usually comes out of it: the number nobody in the organisation currently knows.
Book a discovery call