Theory of Constraints
The Theory of Constraints (TOC) is a management philosophy by Eli Goldratt that focuses on identifying and managing bottlenecks to improve system performance, using the Five Focusing Steps and Throughput Accounting.
THE IDEA
A brief overview of the Theory of Constraints
Eli Goldratt created the Theory of Constraints specifically to help improve the flow in production systems. Goldratt had earned a PhD in Nuclear Physics and was asked by a friend, who was having trouble meeting his production rate, to help a small manufacturing business. Goldratt realized that many of the concepts of flow he had studied academically applied to the flow of a factory, including the impact of features like bottlenecks. He started a production planning software company and wrote a book to market the software, knowing that his approach was counter-intuitive and not taught in business schools. His book, The Goal, was Goldratt’s way to have potential customers conclude that the method would work for them. It is also how most people first encounter TOC.
The account describes repeated publisher rejections of its “business novel” format. Since its first printing in 1984, the book has appeared in multiple editions and languages.
Goldratt proposed that every system with a goal has a bottleneck, or constraint, that determines its output of “goal units.” Therefore, improvements in the productivity of the constraint benefit the system. In contrast, “improvements” at non-constraint areas can be harmful for the system if they result in more work than the constraint can handle. Another frequent response to a bottleneck is to hire more people or buy more equipment at the bottleneck, but that can be expensive and time consuming and may not work.
Goldratt recommended a more effective approach to improve systems performance in the Five Focusing Steps. These provide a natural progression of improvements.
As written in the TOCICO Dictionary, V2 the Five Focusing Steps are:
- IDENTIFY the system’s constraint(s).
- Decide how to EXPLOIT the system’s constraint(s).
- SUBORDINATE everything else to the above decision.
- ELEVATE the system’s constraint(s).
- WARNING! If in the previous steps a constraint has been broken, go back to step 1, but do not allow INERTIA to cause a system’s constraint.
While a common non-TOC first step is to get more of the constraint, in the Five Focusing Steps this is the fourth step. Once you’ve identified the constraint, steps 2 and 3 typically yield significant improvements at far less cost and effort. The Five Focusing Steps can seem almost simplistic, but can be remarkably insightful.
Many businesses suffer from executives trying to optimize each part of a process, fueled by a fixation on cost-cutting. In traditional cost accounting both Work in Process and Finished Goods Inventory are counted as assets even though they may not be sales. That encourages managers to overproduce to make the numbers look good. Goldratt developed ‘Throughput Accounting’ to focus on revenue from sales as the key metric, not goods produced. TOC includes a generic solution for production planning (Drum-Buffer Rope) and finance and measures (Throughput Accounting). Over time, additional generic solutions have been added for analysis and problem solving (the Logical Thinking Process), project management (Critical Chain), supply chain (the Distribution Solution), and strategy (Ever Flourishing Company strategy).
Throughout this development, Goldratt followed an approach that he highlighted in one of his first books, What is This Thing Called Theory of Constraints? and in one of his last, The Choice. Goldratt’s approach was highly dependent on what he saw as the Scientific Method. It depended on using observation and intuition to be the source of hypotheses and then to derive experiments to test for predicted effects. These experiments either confirmed or disconfirmed the predicted effects, which determined whether the assumed cause existed and applied. Over time this creates not a sense of what is true but what is valid within a specific context. Goldratt made the point that truth is something you search for within a religion, while science searches for valid and useful things, even if they are not true.
Looking through a Cynefin lens, we would say that Goldratt used intuition and abductive reasoning to come up with coherent ideas to then test them with safe-to-fail probes. He started with observable negative effects – the UnDesirable Effects (UDEs) – and developed a hypothesis for what might cause them. When he felt confident in predicting what would happen, and why, the Logical Thinking Process logic trees would be used to describe the problem and the solution in terms of inductive and deductive logic. He hypothesized that the cause would also create other effects (inductive reasoning), and that starting with the cause and elements of reality, he could derive the effects (deductive reasoning). This led some to believe that the generic TOC solutions were developed from the logic trees. It’s more likely, however, that the logic trees were created after the fact to document the approach and the assumptions behind why they worked.
Nevertheless, this has set up a lingering misperception among people who see the logic trees and assume that TOC is a means of defining the world in terms of linear, deterministic logic. When you read Goldratt’s description of how he worked, it is clear that he followed a very Cynefin-like process; he started in the Confusion or Complex domains and ran a series of probes until he had a solid understanding of what was happening. He mostly started in Complex and moved into Complicated, at which point he shared what he had discovered in the form of Complicated domain artifacts.
When to use it
Improving production throughput in a manufacturing plant by identifying and managing bottlenecks.
Managing project timelines with Critical Chain methodology to reduce delays and overallocation.
Optimizing supply chain distribution to reduce inventory and improve delivery performance.
Increasing efficiency in a service industry (e.g., healthcare, IT) by focusing on the constraint that limits the number of patients or tickets processed.
FROM THEORY TO EVERYDAY LIFE
In practice
Factory Bottleneck Optimization
A factory produces widgets and identifies that the painting station is the bottleneck. Instead of immediately buying a new painting machine, they apply TOC by ensuring the painting station never runs out of parts, scheduling worker breaks to minimize downtime, and adjusting the production rate of earlier steps to match the painting station's capacity. This exploits the constraint and increases overall throughput with minimal cost.
Software Development Constraint
A software team finds that work queues up for code review and that the review capacity limits completed releases. The team reserves time for reviews, trains additional reviewers through pairing, and limits incoming work so the queue does not keep growing. It then checks whether these changes improve release throughput.
A MOMENT TO REFLECT
Put it to work.
Identify a bottleneck in your daily workflow. How could you exploit it without adding resources?
How might overproduction be encouraged by traditional cost accounting in your organization? What would Throughput Accounting suggest instead?
Consider a system you are part of (e.g., a team, a project, a process). What is its goal and what is its primary constraint?
Often confused with
References
- The Goal — Eliyahu M. Goldratt (1984)
- What is This Thing Called Theory of Constraints? — Eliyahu M. Goldratt
- The Choice — Eliyahu M. Goldratt
- TOCICO Dictionary, V2 — TOCICO
CONTINUE THE CONVERSATION
Source texts
- Cynefin - Weaving Sense-Making into the Fabric of Our World ED02 (Dave Snowden Sonja Blignaut Zhen Goh)