CLEAN · Constraint-led LEAN
ToC leads the system.
LEAN follows inside it.
For LEAN practitioners who sense a ceiling: put Goldratt’s Theory of Constraints first — then deploy LEAN where it multiplies the bottleneck. Projects use the same logic via Critical Chain (CCPM).
The problem CLEAN addresses
LEAN is powerful. Local optima are not.
LEAN and Six Sigma dominate process improvement. They remove waste and variation with discipline. Yet many organisations still plateau: every station looks efficient, inventory and lead times stay stubborn, and cash does not move.
CLEAN keeps your LEAN toolkit. It changes the sequence: Theory of Constraints rules for the whole system first; LEAN methodologies and tools inside subsystems — only after that.
Theory of Constraints
The power of focusing on the weakest link
Eliyahu Goldratt’s Theory of Constraints starts from a mathematical law: in a system of dependent steps, one constraint sets the rate of the whole. Improving everything else does not raise throughput. A system of local optima is not an optimum system.
The goal shifts from “cut costs everywhere” to maximise throughput — the rate at which the system generates money or mission result — while reducing inventory and controlling operating expense.
- Often large gains without new investment, reorganisation, or headcount cuts — for profit and non-profit alike
- A ~10% improvement at the constraint can lift total output by 10–30% or more, often visible in days
- A stable organisation is deliberately unbalanced: spare capacity on non-constraints absorbs variability and protects flow
- Three core measures: Throughput (T), Inventory (I), Operating Expense (OE) — decide with the system, not with local cost accounting alone
Source essays (Dutch): Doubling results without investment · Measuring performance with T, I, OE
The marching column
Same soldiers. Different command.
Picture your process as a column of soldiers marching through a forest. The front soldier starts work (materials enter). The rear soldier delivers output to the customer. Column length is work-in-process (WIP). Each soldier has a different maximum speed.
LEAN’s instinct: smooth single-piece flow; the customer (the sergeant) sets the pace; waste and buffers are driven down. Elegant — and fragile when someone stumbles (Murphy).
ToC’s Drum-Buffer-Rope: the slowest soldier drums the pace of the whole column. First free him of ballast — pack, path, interruptions — so he reaches his true maximum. Place a small buffer of space ahead of him so upstream stumbles do not stop him. Tie a rope to the front so the lead soldier cannot race ahead and stretch the column. Soldiers behind the drum naturally have spare capacity and catch up. Result: a compact column that marches steadily and maximises output.
CLEAN’s point: after the drum, buffer, and rope govern the system, LEAN tools belong where they free or protect the slowest soldier — not as a campaign to make every soldier “efficient” in isolation.
Full metaphor (Dutch): LEAN vs. ToC — more output, less lead time
The CLEAN sequence
System rules first. Subsystem tools second.
-
01
Identify the system constraint
Find the resource or policy that limits total throughput — not the loudest complaint, the true rate-limiter.
-
02
Exploit and subordinate
Get every usable minute from the constraint. Align every other process to protect and feed it — even if that means deliberate spare capacity elsewhere.
-
03
Place LEAN inside subsystems
Once flow is governed by ToC (Drum-Buffer-Rope, buffers, subordination), apply LEAN and Six Sigma where they raise constraint output or remove waste that starves or blocks it.
-
04
Elevate, then repeat
If the constraint still limits the goal, elevate it. The bottleneck moves. Start again — holistically, every time.
Projects · Critical Chain
CCPM: ToC for project work
Operations use Drum-Buffer-Rope. Projects use Critical Chain Project Management (CCPM) — the same constraint logic applied to tasks, dependencies, and scarce people.
Critical Path Method (CPM) tracks the longest dependency chain and ignores resource contention. Safety is buried in every task estimate; Parkinson’s Law and Student’s Syndrome consume it; multitasking stretches everything. Deadlines slip anyway.
- Critical chain = longest path of dependent tasks and resource limits — the real project constraint
- Estimate tasks at ~50% confidence; pool safety into a shared project buffer (plus feeding buffers where needed)
- Eliminate bad multitasking: finish focused work so successors can start early
- Manage by buffer consumption (fever chart), not by fake task deadlines
Reported outcomes in industry cases often include 25–50% shorter project durations and more reliable due dates — without heroic overtime as the default. For product development, shorter time-to-market can make or break the business case.
Source essays (Dutch): Critical Chain vs Critical Path · Goldratt’s project insights · Time-to-market & the business case
Where LEAN still belongs
Not instead of LEAN — after ToC.
Taiichi Ohno built extraordinary flow. Goldratt stood on those shoulders and made the bottleneck explicit. CLEAN is that integration for practitioners who already speak LEAN:
- Value-stream mapping and waste walks — focused on what feeds or protects the constraint
- Standard work and 5S — at and around the constraint first
- Pull and kanban — subordinated to buffer policy, not as a substitute for it
- Six Sigma — on variation that threatens constraint availability or quality of its output
Dutch source material
Deeper reading on frissebronnen.nl
Briefing
CLEAN method for LEAN practitioners
English brochure: ToC power and measures, the marching-column metaphor, the CLEAN sequence, where LEAN fits, and a full page on Critical Chain Project Management (CCPM).
Conversation
Test readers welcome.
CLEAN is in early English release. If you work with LEAN or project delivery and want a sharper system lens, ask for a walkthrough of the brochure.
Bernard de Groot
Frisse Bronnen
bernard@frissebronnen.nl
frissebronnen.nl