What Subordination Actually Means
The Theory of Constraints (TOC) five focusing steps are: identify the constraint, exploit it, subordinate everything else, elevate it, and repeat. Subordination is Step 3 — and it's where most implementations fail.
Subordination means: every non-constraint resource aligns its behaviour to serve the constraint's needs, even when this makes those resources appear inefficient by traditional measures.
The Counterintuitive Part
Local inefficiency can be globally optimal. This is the insight that most managers find hardest to accept, because it runs directly against decades of management accounting and performance metric design.
A non-constraint resource running below full capacity is not waste — it may be exactly what the system needs. Forcing it to run at higher utilisation will either:
- Create WIP piles upstream of the constraint, increasing lead time and working capital
- Starve the constraint of its feeding requirements (if it's upstream)
- Create overproduction that masks the constraint's actual performance
What Subordination Requires From Each Resource
| Resource | Subordination Requirement |
|---|---|
| Upstream processes | Maintain constraint buffer without overproduction. Release to schedule, not to capacity. |
| Downstream processes | Maintain buffers and sprint capacity. Be able to absorb constraint output variations without losing throughput. |
| Maintenance | Prioritise constraint availability above all else. A non-constraint machine waiting is a minor inconvenience; a constraint machine waiting is a system loss. |
| Quality | Inspect before the constraint; protect after. Never let defects consume constraint capacity. |
| Scheduling | Minimise constraint changeovers. Sequence production to maximise the constraint's productive time. |
Why Subordination Fails
- Local performance metrics: When non-constraint managers are measured on their own utilisation or efficiency, they will optimise for it — even at the expense of the constraint.
- Cultural resistance: "My department is being asked to run slowly so the bottleneck looks good" feels deeply unfair without a shared understanding of system thinking.
- Lack of constraint visibility: If operators don't know which resource is the constraint, they cannot make subordination decisions in real time.
- Metric confusion: OEE scores, efficiency reports, and utilisation dashboards that don't distinguish constraint from non-constraint resources actively undermine subordination.
Making Subordination Work: Drum-Buffer-Rope
Drum-Buffer-Rope (DBR) is the operational mechanism for implementing subordination in practice:
The Drum
The constraint sets the pace for the entire system. Its schedule is the master schedule. Everything else aligns to it.
The Buffer
Time buffers protect the constraint from upstream variation. They are not physical stock targets — they are time targets. If material is not at the constraint buffer location by a certain time, an expediting signal is triggered.
The Rope
Material release into the system is tied directly to constraint consumption. The rope prevents overproduction by ensuring the system never puts in more material than the constraint can process within the buffer horizon.
The Mathematical Justification
For a system with constraint rate R and n non-constraints:
This means: once the constraint is fully fed, additional utilisation of any non-constraint resource adds zero throughput. It only adds operating expense and WIP.
The corollary: investing in non-constraint improvement when the constraint is not fully utilised produces zero throughput improvement. Every pound invested in non-constraint improvement (when the constraint is not fully protected) is wasted.
Implement TOC in your facility
majaco has implemented TOC and Drum-Buffer-Rope in manufacturing environments across the UK. Start with a conversation.
Talk to majaco