A machining plant in the Midwest found its constraint — the CNC cell that fed final assembly. Management had exploited it well: cleared the quality inspection backlog, pulled non-essential setups off the cell, confirmed the Drum was running at full capacity. Results were immediate. Lead times dropped. Late orders cleared. The VP of operations declared the TOC implementation a success.
Twelve months later, lead times were back where they started. The constraint cell was buried in WIP again. The investment in a second CNC cell — bought to "elevate" the constraint — had produced almost no improvement.
They had done Steps 1 and 2 correctly. They had never done Step 3.
The Step That Ends Most Implementations
The Five Focusing Steps are among the most practical improvement frameworks ever developed. Identify the constraint. Exploit it. Subordinate everything else. Elevate only then. Repeat. The logic is clean. The sequence is non-negotiable.
But Step 3 — Subordinate — is where most implementations collapse. Not because it is technically complex. Because it is organizationally painful.
Subordination means every non-constraint resource must operate at the pace the constraint demands — even when that means running below full utilization. A milling center upstream of the constraint should slow down, or stop, when the constraint buffer is healthy. This is exactly correct TOC behavior. It is also the opposite of what every local efficiency metric rewards.
The Measurement System Always Wins
In that Midwest plant, the machining supervisor upstream of the CNC cell had been measured for years on machine utilization. After the DBR implementation, his machines were occasionally idle — intentionally — to prevent flooding the constraint buffer with WIP. His quarterly review still measured utilization. He got a poor rating. His team reverted to running full. The WIP piled up. The constraint choked.
This is not a management failure. It is a measurement system failure. If your formal measurements reward local efficiency, your people will produce local efficiency — and the constraint will drown in the resulting WIP.
Goldratt's data is clear: of every ten TOC implementations that produce good early results, approximately one spreads. The others fade. The most consistent reason is measurement systems that were never changed.
A 2003 meta-analysis of 82 documented TOC applications (Mabin and Balderstone) found median throughput increases of 68% and lead time reductions of 70% in fully implemented cases. Companies that stall at Step 2 capture a fraction of that. The difference between a complete implementation and a stalled one — for a $50M revenue business — is often several million dollars in annual throughput sitting uncaptured because no one changed the measurement system.
The Skip From Step 2 to Step 4
There is a second pattern that kills the same implementations: jumping from Exploit directly to Elevate. The constraint is performing well. The easy wins are in. Leadership invests in additional capacity at the bottleneck — a second machine, more headcount, better equipment.
The investment is made. Throughput does not improve. A new constraint appears elsewhere — often at a resource that had been running at 100% utilization while everyone watched the original bottleneck. The organization is confused: they invested in exactly what the analysis said was the problem.
What they invested in was a Step 4 solution to a Step 3 problem.
What Leadership Must Do
Subordination requires something specific from the CEO or COO: they must personally and visibly protect the people who follow constraint-subordination logic when their local metrics look bad. A plant manager whose non-constraint resources run below utilization to feed the constraint correctly needs to see their leader publicly endorse that choice — not just in principle, but when the quarterly review happens and the utilization number is low.
Without that visible protection, middle managers cannot safely subordinate. They will optimize what they are measured on. The measurement system always wins over individual commitment.
The Competitive Consequence
A company that completes Subordination delivers something competitors cannot easily match: short, reliable lead times — consistently. Not fast sometimes and slow other times. Reliably short.
Customers who experience this restructure their supply chains around you. They reduce their own inventory because they can trust your delivery. They do not want to switch suppliers and lose that reliability. Competitors who have not subordinated their systems cannot replicate this without changing their management model — which is exactly what makes it a sustainable advantage.
What Complete Subordination Looks Like
Step 3 is complete when:
- Non-constraint resources are measured by whether the constraint is fed on time — not by their own utilization rates
- Work release into the system is governed by the Rope — tied to the constraint's pace, not to upstream resource availability
- Priority decisions at every resource follow buffer color (green/yellow/red), not managerial preference
- Leadership visibly accepts lower local metrics when they result from correct constraint-protection behavior
This Week's Action
If you have an active improvement program — TOC or otherwise — ask one question: what does your formal performance measurement system reward today? If the answer is local efficiency (machine utilization, labor productivity, departmental cost variance), you have a Step 3 problem. It is not in the operations. It is in the measurement system. Start there, before buying anything.