Who created the Theory of Constraints?

Eliyahu Goldratt, a physicist and business consultant, created the Theory of Constraints and popularized it in his 1984 business novel The Goal: A Process of Ongoing Improvement. The book uses a story about a struggling plant manager to teach the constraint concept, the five focusing steps, and the idea that the goal of a business is to make money, measured through throughput, inventory, and operating expense.

Why do constraints migrate?

When you improve a bottleneck enough, it stops being the slowest necessary step and some other resource takes over as the constraint. Elevate a packing line and the filler upstream may become the limit; keep going and demand itself may become a market constraint. The bottleneck moves rather than disappears, which is why the fifth focusing step sends you back to identify the new one.

How is the Theory of Constraints different from lean?

Lean attacks waste everywhere in the process, while TOC says to focus improvement only on the constraint because gains elsewhere do not raise throughput until the bottleneck moves. They chase the same goal of better flow and are largely complementary: TOC decides where to improve, and lean tools do the improving at that spot. They mainly disagree on priority order, not on the destination.

How do you find the constraint in a plant?

Look for the signs: work-in-process piles up in front of the constraint, the steps after it are frequently starved and idle, and it is the resource everyone blames for late orders. On paper, compare each resource's load to its capacity; the one running closest to or over 100 percent is the bottleneck. Reliable identification depends on true cycle times and actual downtime rather than nameplate estimates.

Theory of Constraints: Find the Bottleneck, Then Exploit It

Q: What is the Theory of Constraints?

The Theory of Constraints is a management approach holding that the output of any system is governed by its single most limiting resource, the constraint, and that overall performance improves only by improving that constraint. It was introduced by Eliyahu Goldratt in his 1984 book The Goal. The constraint sets the plant's pace, so effort spent anywhere else does not raise throughput; it just moves inventory around.

Q: What are the five focusing steps?

They are Goldratt's repeatable cycle: identify the constraint, exploit it by getting maximum output without spending money, subordinate everything else to serve it, elevate it by adding capacity if needed, and then go back to step one because a new constraint appears once the first is broken. The steps run in order and loop, making constraint management an ongoing practice.

Q: What is drum-buffer-rope?

Drum-buffer-rope is the TOC scheduling method that paces the plant to the constraint. The drum is the constraint, whose rate sets the beat for everyone. The buffer is a small amount of protective inventory or time placed just ahead of the constraint so an upstream hiccup does not starve it. The rope ties material release to the drum's pace, so new work enters only as fast as the constraint can consume it.

Goldratt's five focusing steps, drum-buffer-rope, and why the fastest way to speed up a whole plant is to manage its single slowest step.

The Theory of Constraints (TOC) is a management approach that says every system is limited by a small number of constraints, usually one bottleneck, and the fastest way to improve the whole system is to find that constraint and manage it. It was introduced by Eliyahu Goldratt in his 1984 business novel The Goal. Improve the bottleneck and the whole system speeds up; improve anything else and you often just pile up inventory.

The idea is counterintuitive on a busy floor, where the instinct is to keep every machine running. TOC says a machine that is not the constraint should sometimes sit idle, because running it only builds work-in-process the bottleneck cannot absorb. This post covers the five focusing steps that put TOC into practice, drum-buffer-rope for scheduling around a constraint, and how constraints migrate once you fix one.

What is the Theory of Constraints?

The Theory of Constraints holds that the output of any system is governed by its single most limiting resource, the constraint, and that overall performance can only improve by improving that constraint. Everything else is subordinate. The constraint sets the pace, the plant can only ship as fast as its slowest necessary step, so effort spent anywhere else does not raise throughput, it just moves the pile of inventory around.

TOC reframes the goal. Goldratt argued the goal of a manufacturing business is to make money, and he measured progress with three operational terms: throughput (the rate the system generates money through sales), inventory (money tied up in things it intends to sell), and operating expense (money spent turning inventory into throughput). The constraint is where you push on all three at once, raising throughput without inflating inventory or expense.

By the numbers. The Theory of Constraints was introduced by Eliyahu Goldratt in his 1984 business novel The Goal which has since sold millions of copies and become a standard operations-management text (Theory of constraints). Its central claim has held up for four decades: a system improves only as fast as its constraint.

What are the five focusing steps?

The five focusing steps are Goldratt's repeatable cycle for improving a system through its constraint. They run in order and then loop, because fixing one constraint reveals the next. This is the practical heart of TOC.

Identify the constraint. Find the resource that limits the whole system. On a floor it is usually where work piles up in front and starves behind, the step everything waits on.
Exploit the constraint. Get the most out of it without spending money. Keep it running through breaks and changeovers, stop feeding it defective work, make sure it never waits on a missing tool or operator. Every minute the constraint is idle is throughput the whole plant loses.
Subordinate everything else. Make every other resource serve the constraint. Non-constraint machines run at the constraint's pace, not their own maximum, so they feed it steadily instead of burying it in work-in-process. This is the step that feels wrong and matters most.
Elevate the constraint. If exploiting and subordinating are not enough, add capacity: another shift on that step, a second machine, offloaded work, a capital investment. You only spend money here, after you have wrung out the free gains.
Go back to step one. Once the constraint is broken, a new one appears somewhere else. Repeat the cycle, and never let inertia make yesterday's fix into today's policy constraint.

The five focusing steps run as a cycle: once you break one constraint, a new one appears and you start again.

What is drum-buffer-rope?

Drum-buffer-rope (DBR) is the TOC scheduling method that paces the whole plant to the constraint. The drum is the constraint, whose rate sets the beat for everyone else, you schedule the drum to run flat out and never starve. The buffer is a small amount of protective inventory or time placed just ahead of the constraint, so a hiccup upstream does not stop the drum. The rope is the signal that ties material release to the drum's pace, so new work only enters the system as fast as the constraint can consume it.

The rope is the discipline that stops the floor from over-producing. Without it, upstream stations run at their own top speed and bury the constraint in work-in-process, which lengthens lead times and hides problems. With it, material is released to match the drum, work-in-process stays low, and the plant flows. DBR is essentially the five focusing steps' "subordinate" step turned into a scheduling rule.

The drum sets the pace, the buffer protects it, and the rope releases material only as fast as the constraint can use it.

How do constraints migrate?

When you break a constraint, the bottleneck moves, it does not disappear. Elevate the packing line that was limiting the plant, and now the filler upstream becomes the slowest necessary step. That is why the fifth focusing step sends you back to the start: constraint management is a permanent practice, not a one-time project. A plant that runs TOC well is always chasing the current bottleneck, because there always is one.

Constraints also move between kinds. A physical constraint (a machine, a line) can become a policy constraint (a rule that says "run every machine at full speed") or a market constraint (demand, not capacity, is now the limit). Goldratt warned that the hardest constraints to see are the policy ones, the habits and metrics that keep a plant optimizing the wrong thing long after the physical bottleneck has moved.

Break one constraint and the next appears, first upstream, eventually in the market. There is always a bottleneck to manage.

How does TOC relate to lean and line balancing?

TOC and lean chase the same enemy, wasted flow, from different angles. Lean attacks waste everywhere; TOC says focus only on the constraint, because improvement anywhere else is wasted effort until the bottleneck moves. In practice the two are complementary: use TOC to decide where to improve, then use lean tools to do the improving at that spot. They disagree mainly on the priority order, not the destination.

TOC also sharpens how you think about line balancing. Classic balancing tries to make every station's cycle time equal; TOC says a perfectly balanced line is fragile, because any station's variability can become the constraint and there is no protective capacity anywhere. TOC deliberately unbalances: it protects the drum with a buffer and lets non-constraint stations have spare capacity, trading perfect utilization for reliable throughput. That is why a TOC plant can look "inefficient" station by station while shipping more overall.

How do you find the constraint in a real plant?

The constraint announces itself if you know the signs: work-in-process piles up in front of it, the steps after it are frequently starved and idle, and it is the resource everyone blames for late orders. On paper you find it by comparing each resource's load to its capacity, the one running closest to or over 100% is your bottleneck. But loads and true rates are exactly the numbers that are hard to trust when they live in spreadsheets and nameplate assumptions.

Seeing the real constraint takes real data: true cycle times, actual downtime, and where inventory actually accumulates between steps. When that information is captured live from the floor rather than estimated, the bottleneck stops being a matter of opinion and becomes visible, and you can watch it migrate as you improve. That kind of live, plant-wide visibility is exactly what a manufacturing operating system is built to give, and it is what Harmony's connected data model puts in front of a planner, so constraint management can run continuously instead of as an annual study. Pair it with disciplined scheduling around the drum and TOC stops being a book and starts being how the plant runs.