The Capacity You Already Paid For
- Vinny Monteiro

- Aug 3
- 5 min read
Hello TOC Flow Community!
There's a moment I've watched play out a few times:
A team finally identifies its constraint. Everyone agrees on it. The energy in the room is good. And then, within about ten minutes, someone says "we just need to [add/buy]…. "
The machine. The extra shift. The new hires. The software.
It's the most natural reaction in the world, and it's almost always premature.
Because in nearly every operation I walk into, the constraint is not running at anything close to its real capacity. The company is about to spend money solving a problem it already has the resources to solve.
Why Elevate Feels Like the Answer
If you recall from our Flow Solutions Training, the Five Focusing Steps run in a specific order. Identify. Exploit. Subordinate. Elevate. Then repeat, and don't let inertia become the constraint.
Elevate is fourth.
It's fourth on purpose. It's the step that costs money, takes time, commits you to some sort of effort.
But it's the step everyone wants to jump to, for a few reasons:
It's visible. A new machine on the floor is proof that leadership is doing something.
It's clean. Buying capacity is a decision you make once. Exploiting capacity is a discipline you maintain every day.
It doesn't require anyone to change how they work. That's the real appeal. Elevate lets you fix the problem without asking anyone to give anything up.
But Exploit asks harder questions.
What Exploit Really Means
Here's where I see the most confusion.
Exploit is not "work the constraint harder."
It's not a motivation exercise, and it's not about running people or equipment into the ground. Exploit is about the decisions the constraint makes regarding its own time.
What should it stop doing? What work is reaching it that someone else could do? What is it waiting on? What is it processing that will never ship? What setup, inspection, staging, or paperwork is eating hours that should be production hours?
That's the exploit conversation.
And it's uncomfortable, because the answers usually implicate policies somebody wrote and defended. Then subordinate follows. Everyone else adjusts to support those decisions. When you do this well, the capacity that shows up is capacity you already own.
You paid for it years ago. You just weren't getting it.
Southwest and the Plane They Sold
Here's a case that's worth studying, because it's the opposite of what most companies do under pressure.
In the spring of 1972, Southwest Airlines was in serious trouble. The company had $143 left in its bank account and losses running into the millions. It was flying four Boeing 737s between Dallas, Houston, and San Antonio. To survive, they needed cash. So they sold one of their four aircraft for $500,000.
Now think about the position that created.
They had a schedule built for four planes and only three planes to fly it. Every conventional instinct says cut the schedule. Instead, the VP of Operations, Bill Franklin, worked out what it would take to run the four-plane schedule with three.
The answer was to turn an aircraft in ten minutes. At the time, the industry was taking roughly an hour.
They did it.
Everyone on the ground and in the air took part. Pilots picked up trash. Flight attendants cleaned cabins. Gate agents had the next group of customers lined up before the last group finished deplaning.
More than a hundred tasks compressed into ten minutes. Same three aircraft. Same routes. The schedule of a four-plane fleet.
That is exploitation.
The constraint was aircraft time, and they went after every minute the plane spent sitting on the ground doing nothing that generated revenue. Southwest no longer turns aircraft in ten minutes, and the conditions of 1972 don't exist anymore. But the thinking never left the company.
At a recent investor day, Southwest said that reducing turn times by five minutes would free up the equivalent of roughly 16 aircraft.
Sixteen aircraft worth of capacity. Not by buying sixteen aircraft. By finding five minutes.
That's the difference between exploit and elevate stated in the plainest possible terms.
How to Know You Haven't Exploited Yet
Here's something worth paying attention to:
Before you approve any capacity investment, ask what percentage of the constraint's available time is spent producing throughput.
Most operations can't answer that question. They can tell you utilization, which is a different thing entirely. Utilization tells you the resource was busy. It doesn't tell you the resource was busy on the right work.
Three questions that get at it:
Does the constraint ever wait? For material, for a decision, for an operator, for a tool, for the previous step. Every minute of waiting is capacity you own and aren't collecting.
Is the constraint doing work that a non-constraint could do? Setup, staging, moving material, inspection, paperwork. If a $40 per hour resource is doing something a $20 per hour resource could do, you're buying capacity at a terrible price.
Is the constraint processing work that will not ship this quarter? Building ahead, running the wrong priority, making parts for an order that got pushed. That's capacity spent on nothing.
If you can't answer these, you are not ready to elevate.
You don't yet know how much capacity you need, because your number includes your own waste.
The Practical Argument
Set aside the TOC theory for a second and consider the business case.
If you elevate before you exploit, you size the investment based on today's performance, waste included. You will overbuy. You'll spend for capacity you already had and didn't know about.
If you exploit first, one of three things happens:
You discover you don't need to elevate at all. This happens more often than most leaders expect.
You discover you need to elevate, but far less than you thought. The investment gets smaller and the payback gets faster.
Or you confirm the constraint is genuinely maxed out, and now you elevate with real numbers behind the decision. Your business case is stronger, and the finance conversation is easier.
All three outcomes are better than signing the PO first.
Your August Challenge
This month, take your constraint and track one thing for two weeks. Not utilization. Track the minutes the constraint spends producing throughput, and the minutes it spends on everything else. Waiting. Setup. Rework. Moving material. Paperwork. Producing work that won't ship.
Then add up the second column.
That number is your first elevation, and it doesn't cost anything.
Only after you've collected it should you start the conversation about buying more.
Southwest found the equivalent of sixteen aircraft in five minutes.
What are you sitting on?




Comments