How I Turned an $800,000 Capex Request Into an $87,000 Solution Using Goldratt’s Sequence
Quick Answer: Every bottleneck in your operation can be broken in a specific three-step sequence — Exploit, Subordinate, Elevate — and you are almost certainly running it backwards. Most leaders skip straight to Elevate (write a check, buy more equipment, add a station) because that feels like decisive action. The Stagnation Assassin protocol forces you through Exploit and Subordinate first, and in five Fortune 500 turnarounds, that sequence has reduced capital requests by an average of 89% while delivering greater throughput gains than the original capex proposal.
The Day I Learned Why Engineers Reach for the Checkbook First
The Station 3 situation sits on the wall of my office. Not as a trophy — as a warning.
When I walked into the industrial equipment division, the engineering team handed me a capital request. Eight hundred thousand dollars for a second assembly station. Six-month lead time. The business case was tight, the ROI calculation was clean, and the operations director had already pre-sold it to two board members. Station 3 was the constraint. Station 3 needed more capacity. The answer was obvious.
The answer was wrong.
Not because the math was flawed — the math was fine. It was wrong because it was the third answer in a three-step sequence, and the team had skipped the first two steps entirely. They had not exploited the bottleneck. They had not subordinated the surrounding process to it. They had jumped directly to elevation because that is what engineers do when capital is available and the pressure is on. It is the expensive reflex, and it kills more capacity budgets than any other single behavior I have seen across five turnarounds.
Two weeks later, we had Station 3 running at 108% of original throughput with zero capital investment. Six weeks after that, we had it at 142% with $87,000 in surgical automation. The $800,000 request was canceled. The capital funded three other initiatives that generated more shareholder value than the expansion would have delivered in its entire useful life.
The Origin of This Framework in My Work
I did not invent the Theory of Constraints. Eliyahu Goldratt did, and his book The Goal is required reading for anyone I trust with a P&L. What I did was take his academic framework and rebuild it into an execution protocol that operators can deploy in two weeks instead of two quarters.
The version you see in the infographic above is the one I have run five times across Fortune 500 and Fortune 1000 turnarounds. The language is deliberately operational. The sequence is non-negotiable. And the core discipline — exhaust free solutions before writing checks — is the single highest-leverage habit a transformation leader can build.
The Blitz: Why Speed Is the Weapon
This is where The Blitz lives. Not in aggression for its own sake, but in the refusal to let the organization drift into six-month deliberation cycles when the constraint is sitting in front of the team begging to be broken. The Blitz is the conviction that two weeks of focused exploitation will outperform six months of capital project planning, every single time.
The Station 3 Blitz ran like this:
Day 1: The bottleneck was identified with stopwatch data. Not opinion. Not debate. Data.
Days 2–5: The Exploit phase launched. The team rearranged the station layout to eliminate reach-and-retrieve motion. Materials were kitted at point-of-use instead of being pulled from central storage. Work instructions were converted to visual standards posted at the station. Every second of operator time that was not adding value was hunted and eliminated.
Days 6–10: The Subordinate phase began in parallel. Upstream batch sizes were recalibrated to Station 3’s actual consumption rate, not to arbitrary batch economics. Quality checks that had been performed at the end of the line were moved upstream, so defects never reached the bottleneck. Material staging was timed to the constraint, not to shift schedules.
Day 14: Station 3 throughput measured at 108% of its original nameplate rate. No capital had been spent.
Weeks 3–6: The Elevate phase was evaluated — not assumed. With Station 3 already exceeding its prior output, the question became: is further investment warranted, and if so, at what minimum viable scope? The answer was $87,000 in automated fastening equipment that reduced assembly time by 23%. Surgical. Targeted. One-tenth the cost of the original capex request.
That is The Blitz. Speed is not a style choice. It is the mechanism that prevents the organization from defaulting to expensive answers.
The Deep Framework: Why the Sequence Is Not Negotiable
The axes of this framework — Exploit, Subordinate, Elevate — are ordered the way they are for a specific mathematical reason. Each step reveals information that changes the economics of the next step.
Exploit answers the question: “What is the actual capacity of the constraint when we stop wasting it?” In the Station 3 case, the answer was 108% of the nameplate rate. That number was previously invisible because the constraint had never been worked hard. Wasted motion, poor material flow, and inconsistent work methods were consuming 8% of the station’s true capacity without anyone knowing.
Subordinate answers the question: “How much of our perceived capacity problem is actually an alignment problem?” When upstream processes dump batches at the wrong size, wrong time, or with defects that only reveal themselves at the constraint, the constraint absorbs waste that was created elsewhere. Subordination is how you stop exporting upstream dysfunction to the bottleneck. It often delivers another 10–20% throughput gain at zero capital cost.
Elevate is where capital finally earns the right to be spent — and only after Exploit and Subordinate have established a new baseline. Because the bottleneck is now operating at its true exploited capacity with a subordinated support system, any capital investment applied here delivers leveraged returns. The $87,000 in automation at Station 3 produced more throughput gain than the original $800,000 proposal would have, because it was applied to a constraint that had already been optimized before the capital arrived.
Run the sequence out of order and you waste capital. Run it in order and you convert capital into compounding returns.
The Sacred Terms: “Constraint” Is Not a Problem. It Is an Asset.
In the theology of the Theory of Constraints, the word “constraint” is not pejorative. The constraint is the most important station in your entire operation, because every unit of output you produce passes through it. It is the single point of leverage that determines the financial performance of the whole system. Treating it as a problem to be eliminated is how organizations miss the real opportunity, which is to make the constraint the most productive, most protected, most precisely-supported resource in the building.
This is the language shift that matters: the constraint is not an enemy. It is the asset you have been under-exploiting.
The Critical Insight: The Constraint Always Moves
After we cleared Station 3, the constraint migrated to Station 5 — a quality check station that had been adequate under the old throughput rate but became the new bottleneck once Station 3 was producing 42% more units. Most leaders interpret this as failure. It is not. It is exactly what success looks like in a constraint-based system.
The framework is recursive. You run Exploit–Subordinate–Elevate on the new constraint, and then on the one after that, and the one after that. Each cycle lifts total system throughput. Each cycle reveals where capital should flow and, more importantly, where it should not. In the industrial equipment turnaround, we ran the sequence on four constraints over eighteen months. Revenue moved from below $50 million to over $60 million using the same equipment, same facility, and same headcount. The facility expansion was canceled permanently.
The Uncomfortable Truth
Traditional thinking would have added a second assembly station, an $800,000 investment and a six-month lead time. Instead, we rearranged station layout, implemented point-of-use material kitting, and created visual work instructions. Station 3 throughput increased to 108% of previous capacity with no capital investment and two weeks for implementation. Then we subordinated upstream processes to the bottleneck’s rhythm. Then — and only then — did we add $87,000 in targeted automation. Total result: 142% throughput, one-tenth the capital, and a constraint that had migrated to its next location, ready for the next cycle. That is not a lean project. That is how transformation actually works.
About the Author
Todd Hagopian is the architect of the Hypomanic Operational Turnaround (HOT) System and the author of Stagnation Assassin: The Anti-Consultant Manifesto. He has led five Fortune 500 and Fortune 1000 transformations, including turnarounds at Berkshire Hathaway, Illinois Tool Works, and Whirlpool Corporation, generating over $3 billion in documented shareholder value. His frameworks — including the 80/20 Matrix, the Karelin Method, the 3-A Method, the Four-Dimension Capacity Assessment, and the operational deployment of the Theory of Constraints — have been featured across Forbes, Fox Business, NPR, and The Washington Post. He holds an MBA from Michigan State University and writes from his desk in Solon, Ohio.
Join the Stagnation Assassin Circle
If this framework resonated, the full arsenal — including the Corporate Implementation Guide, the HOT System video course, the framework summaries library, and monthly office hours with me — is waiting inside the Stagnation Assassin Circle. It is a private community for leaders actively waging war on stagnation, and your membership is free.
Claim your membership and continue the conversation at toddhagopian.com.