Theory of Constraints (TOC)
Also known as: TOC, Constraint Management, Bottleneck Theory, Kısıtlar Teorisi
The Theory of Constraints (TOC) is a management philosophy and continuous improvement framework introduced by Eliyahu Goldratt in his 1984 novel The Goal and formalized in his 1990 book. TOC holds that every system has at least one constraint — a bottleneck that limits the system's overall throughput — and that systematically identifying and addressing that constraint is the most effective lever for improving performance. It is widely applied in manufacturing, project management, supply chains, and service operations.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
TOC is most appropriate when an organization needs to increase throughput without large capital investment and can pinpoint a single dominant bottleneck. It assumes that one constraint drives system performance at any given time and that non-constraint capacity is not critically scarce. It is less suited to highly parallel or simultaneous-constraint systems. When multiple bottlenecks coexist or demand is highly variable, complementary tools such as Value Stream Mapping or Six Sigma DMAIC may be needed alongside TOC.
Strengths & limitations
- Provides a clear, prioritized focus that prevents wasteful improvement efforts at non-bottleneck steps
- Typically delivers rapid throughput gains with minimal capital expenditure
- Offers an integrated set of thinking tools (Current Reality Tree, Future Reality Tree, Evaporating Cloud) for diagnosing root causes
- Applicable across manufacturing, project management, supply chain, healthcare, and service industries
- Assumes a single dominant constraint at a time, which may not hold in complex, highly parallel systems
- Does not directly address demand variability or stochastic arrival patterns
- Identifying the true constraint can be difficult when bottlenecks are policy-based or hidden in organizational structures
- Subordinating non-constraints to protect the bottleneck can create idle capacity that is politically difficult to sustain
Frequently asked
What is the difference between TOC and Lean?
Lean focuses on eliminating all forms of waste across the entire value stream to reduce lead time, whereas TOC concentrates improvement effort exclusively on the current system constraint to maximize throughput. The two approaches are complementary: Lean tools can be applied at the constraint to exploit it more fully, while TOC focus prevents Lean projects from being spread too thinly across non-bottleneck steps.
Can TOC and Six Sigma be used together?
Yes. A widely recognized integration called TLS (TOC, Lean, Six Sigma) uses TOC to identify where to focus, Lean to remove waste at that point, and Six Sigma's statistical tools to reduce variation within the constraint process. This sequencing ensures that rigorous data-driven improvement effort is directed at the step that most limits overall system performance.
How do you identify a constraint that is a policy rather than a physical resource?
Goldratt's Thinking Process tools — particularly the Current Reality Tree and the Evaporating Cloud — are designed for this purpose. They trace undesirable effects back through cause-and-effect chains to a core conflict or assumption, which often turns out to be a measurement, rule, or managerial belief rather than a machine or worker. Resolving the conflict typically requires changing the policy rather than adding capacity.
Sources
- Goldratt, E. M. (1990). Theory of Constraints. North River Press. ISBN: 978-0-88427-166-6
How to cite this page
ScholarGate. (2026, June 2). Theory of Constraints (TOC). ScholarGate. https://scholargate.app/en/quality-management/theory-of-constraints
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Little's LawOperations Research↔ compare
- Six Sigma DMAICQuality Management↔ compare
- Value Stream MappingQuality Management↔ compare