What is Theory of Constraints and how does it integrate with Lean?

Last verified: 16 May 2026. Theory of Constraints (TOC) is a management methodology developed by Eliyahu M. Goldratt and introduced in The Goal: A Process of Ongoing Improvement (North River Press, 1984, ISBN 0-88427-061-0). The central premise: every system has at least one constraint, and system throughput is determined by that constraint. Improvement effort applied to non-constraints does not improve system performance; only improvement at the constraint does. Goldratt’s later book Theory of Constraints (North River Press, 1990, ISBN 0-88427-166-8) formalized the methodology.

“The throughput of a system is determined by the rate at which the constraint produces. An hour lost at the constraint is an hour lost for the entire system; an hour saved at a non-constraint is a mirage.” — Eliyahu M. Goldratt, The Goal, North River Press, 1984.

The framework is widely misunderstood as a bottleneck-elimination methodology. It is not — bottlenecks cannot be eliminated, only moved. TOC is a methodology for systematically managing the constraint to maximize system throughput, while simultaneously subordinating all other resources to the constraint’s pace. The distinction matters because plants that try to eliminate constraints invest in capital that does not improve throughput, while plants that manage constraints achieve throughput gains without capital expenditure.

The Five Focusing Steps

The canonical TOC process from Goldratt 1984 and 1990:

1. Identify the system’s constraint. What is the single resource or policy that limits throughput? Usually one bottleneck station, sometimes a market constraint (insufficient demand), sometimes a policy constraint.
2. Exploit the constraint. Ensure the constraint is producing at maximum capability. No lunch breaks at the constraint without coverage; no scrap parts processed at the constraint; no setup time without preparation. Every minute of constraint time is throughput.
3. Subordinate everything else to the constraint. Non-constraint resources run at the pace of the constraint, not faster. Faster non-constraints produce inventory between the constraint and them — overproduction without throughput gain.
4. Elevate the constraint. Only after exploit and subordinate are complete: add capacity to the constraint. Capital investment, additional shift, process redesign.
5. Repeat from step 1. Once the constraint is elevated sufficiently, a new constraint will emerge elsewhere. Prevent organizational inertia from continuing to invest in the former constraint.

The five steps are deceptively simple. The empirical evidence from Mabin and Balderstone’s 2003 review in International Journal of Operations and Production Management (DOI: 10.1108/01443570310476636) covering 100+ TOC implementations shows median throughput improvement of 63%, median inventory reduction of 49%, and median lead-time reduction of 70% — substantial returns from a methodology that requires no capital expenditure beyond step 4.

Drum-Buffer-Rope: TOC for production scheduling

Drum-Buffer-Rope (DBR) is TOC’s scheduling methodology, formalized in Goldratt 1990:

• Drum: the constraint sets the production beat. Schedule is built backward from the constraint’s capacity.
• Buffer: a time buffer ahead of the constraint ensures it never starves. Typically 25-50% of average lead time to the constraint.
• Rope: a signaling mechanism that releases material into the system at the constraint’s pace, preventing inventory buildup upstream.

DBR is operationally equivalent to a pull system, with the constraint as the pull point. The difference vs Toyota’s kanban-pull: kanban pulls from final assembly; DBR pulls from the constraint, which may be mid-process. For plants with a clear capacity bottleneck, DBR is typically more direct than kanban.

TOC vs Lean vs Six Sigma — complementary, not competing

A persistent confusion in operations management is whether TOC, Lean, and Six Sigma are competing methodologies. They are not — they address different aspects of operational excellence:

• TOC: where to focus improvement (at the constraint)
• Lean: what to eliminate (waste, in seven Ohno categories)
• Six Sigma: how to reduce variability (statistical process control)

The integrated approach — often called Velocity per Goldratt/Jacob/Bergland 2009 (Velocity: Combining Lean, Six Sigma and the Theory of Constraints, Free Press, ISBN 0-7432-9764-4) — applies TOC to identify the constraint, Lean to eliminate waste at the constraint, and Six Sigma to reduce constraint variability. This sequencing matters: applying Lean waste-elimination at non-constraints produces local efficiency without system throughput gain.

“Every improvement project should pass the test: does this increase throughput, reduce inventory, or reduce operating expense? Without one of these, it is local optimization without system benefit.” — Eliyahu M. Goldratt, Theory of Constraints, North River Press, 1990.

The Thinking Processes

TOC includes a set of cause-and-effect analysis tools called the Thinking Processes (Goldratt 1990, expanded in It’s Not Luck, 1994, ISBN 0-88427-115-3):

• Current Reality Tree — diagrams the root causes of undesirable effects
• Evaporating Cloud — identifies conflicts blocking change
• Future Reality Tree — projects effects of proposed changes
• Prerequisite Tree — sequences obstacles to implementation
• Transition Tree — actions to implement the change

The Thinking Processes are TOC’s contribution to problem structuring; they complement the Five Focusing Steps which provide the operational discipline.

TOC in OEE measurement

The Six Big Losses framework decomposes OEE into six loss categories at the individual equipment level; TOC asks the system-level question of which equipment is the constraint. A line with 90% OEE on the constraint and 70% OEE on a non-constraint has higher system throughput than the reverse, even though the average OEE is the same. Per Cox & Schleier’s Theory of Constraints Handbook (McGraw-Hill, 2010, ISBN 0-07-166554-3), TOC-aware OEE reporting weights the constraint station’s performance disproportionately because that is the only station whose OEE directly translates to throughput.

Frequently asked questions

Who developed Theory of Constraints?

Eliyahu M. Goldratt, introduced in The Goal (North River Press, 1984) and formalized in Theory of Constraints (North River Press, 1990).

What is the central premise of TOC?

Every system has at least one constraint that determines its throughput. Improvement effort applied to non-constraints does not improve system performance.

What are the Five Focusing Steps?

Identify the constraint; Exploit it; Subordinate everything else; Elevate the constraint; Repeat (avoid inertia).

What is Drum-Buffer-Rope?

TOC’s scheduling methodology. Drum = constraint sets the beat; Buffer = time buffer ahead of constraint; Rope = signal that releases material at constraint’s pace.

Is TOC compatible with Lean?

Yes, complementary. TOC identifies where to focus improvement; Lean identifies what to eliminate. Integrated approaches (Velocity, 2009) sequence them.

What throughput improvements have been observed from TOC?

Mabin and Balderstone 2003 review of 100+ implementations: median 63% throughput improvement, 49% inventory reduction, 70% lead-time reduction.

Can the constraint be a market rather than a machine?

Yes. Per Goldratt 1990, when production capacity exceeds demand the constraint is the market. Operational focus shifts to sales and marketing rather than the shop floor.

How does TOC differ from traditional cost accounting?

TOC uses Throughput Accounting: Throughput – Operating Expense = Net Profit. Inventory is treated as an investment, not an asset. Local efficiency metrics that drive overproduction are explicitly avoided.

What are the Thinking Processes?

Cause-and-effect analysis tools: Current Reality Tree, Evaporating Cloud, Future Reality Tree, Prerequisite Tree, Transition Tree.

How does TeepTrak support TOC implementations?

The measurement layer identifies the constraint station by throughput, monitors constraint OEE as a weighted metric, and reports buffer status for DBR scheduling.

References

1. Goldratt, E.M. and Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press. ISBN 0-88427-061-0.
2. Goldratt, E.M. (1990). Theory of Constraints. North River Press. ISBN 0-88427-166-8.
3. Goldratt, E.M. (1997). Critical Chain. North River Press. ISBN 0-88427-153-6.
4. Cox, J.F. III and Schleier, J.G. (2010). Theory of Constraints Handbook. McGraw-Hill. ISBN 0-07-166554-3.
5. Mabin, V.J. and Balderstone, S.J. (2003). The performance of the Theory of Constraints methodology. International Journal of Operations and Production Management, 23(6). DOI: 10.1108/01443570310476636.
6. Goldratt, E.M., Jacob, D., Bergland, S. (2009). Velocity: Combining Lean, Six Sigma and the Theory of Constraints. Free Press. ISBN 0-7432-9764-4.

Author: François Coulloudon, CEO, TeepTrak. Cross-references: OEE, Lean Manufacturing, Six Big Losses. Last verified 16 May 2026 against Goldratt 1984/1990 and Mabin & Balderstone 2003.