The Theory of Constraints in Operational Excellence: Why Leaders Work the Bottleneck First
Summarize this article with:
TL;DR
- The Theory of Constraints says your slowest step sets total output. In a connected system, throughput is capped by the constraint, not the busiest step and not the department with the best slides.
- Improving a non-constraint feels productive and changes nothing. Speeding up a step that already outruns the bottleneck just stacks WIP, inventory, expediting, and quality escapes in front of the real limit.
- You cannot apply the Theory of Constraints from a dashboard. Finding the true constraint takes presence. Reports tell you a step backed up, not why, and usually too late to act.
- Operational excellence leadership is working the constraint from the floor. The discipline is to fix the step that caps throughput, on the concrete, not from the carpet.
Questions This Blog Answers
- What is the Theory of Constraints in a manufacturing operation?
- Why does the slowest step set total output instead of the busiest one?
- Why does improving a non-constraint fail to increase throughput?
- What does optimizing the wrong step actually cost you?
- What is gemba leadership, and how does it help you find the constraint?
- Why can’t you apply the Theory of Constraints from a dashboard?
This is Part 2 of a four-part series. In Part 1, Bob Morin made the case that operational excellence is leadership behavior, not a toolkit. Here he turns to what that behavior looks like in practice.
One of the most powerful reminders I heard at the AME conference came from a session on the Theory of Constraints.
The premise is simple and brutally honest:
In a connected system, the output is determined by the slowest step.
Not the busiest step. Not the loudest problem. Not the department with the best PowerPoint slides.
The constraint.
And yet, organizations routinely spend time improving non-constraints because those problems feel easier. They’re safer. They’re cleaner. They’re closer to what people already know how to fix.
How the Theory of Constraints plays out on the floor
- A downstream operation can only process two units per hour.
- An upstream operation can process five units per hour.
If you optimize the five to make eight, what do you get?
Nothing.
You don’t get more shipments. You don’t get better delivery. You get more WIP piled up in front of the constraint.
And then you pay for it:
- In inventory
- In floor space
- In expediting
- In quality escapes
- In operator frustration
This is the trap: people feel uncomfortable not being “productive.” So they keep producing, even when producing only creates more problems.
Operational excellence is the discipline to stop doing that.
Gemba Leadership: You can’t see the constraint from the carpet
“90% of troubleshooting is observation.” So why aren’t leaders on the floor?
Gemba is the Japanese word for the place where the real work happens.
Gemba leadership means leading from there, on the floor, not from a conference room. And it’s the only way to actually find the constraint: you have to stand at the line and watch where the work backs up.
If you can’t see the work, you can’t understand the work.
And if you don’t understand the work, you’re left trying to lead from dashboards, meetings, spreadsheets, and weekly reviews. Those tools matter but they are not a substitute for presence.
I’ve said this for years, and I’ll keep saying it: You cannot solve the problem from the carpet. You have to get on the concrete.
Since the pandemic, distance has become normal. Meetings multiplied. And the floor became “less important.” The floor was usually the essential workforce that continued to come in when many others stayed home. This sent a message that broke trust, and once that starts it’s difficult to mend. So the floor, left to fend for itself, created its own leadership process which a lot of businesses are still struggling to overcome.
But operational excellence doesn’t happen in conference rooms. It happens where the value is created: inside real constraints, defects, and handoffs, and in real time.
Leaders have to meet people where they’re at, and that means showing up where the work is.
FAQ’s on Theory of Constraints as applied to operational excellence
The Theory of Constraints holds that any connected system can only move as fast as its slowest step, called the constraint. Total throughput is set by that one step, so improvements anywhere else don’t raise output until the constraint itself is addressed.
Because work has to pass through every step in sequence. A step that runs faster than the constraint just produces inventory that waits. The busiest or loudest area often isn’t the constraint at all, which is why activity and throughput get confused.
The constraint still caps the line. If a downstream step handles two units an hour and you push an upstream step from five to eight, you ship the same number of units. The extra speed becomes WIP, not output.
It shows up as inventory, floor space, expediting, quality escapes, and operator frustration. You spend effort and capital building work that piles up in front of the bottleneck instead of leaving as finished product.
You go look. The constraint is the step everything else waits on, and it’s visible in real time on the floor through where WIP collects and handoffs stall. A dashboard reports the symptom after the fact; presence shows you the cause.
Dashboards, meetings, and weekly reviews summarize the work but don’t show it. Constraints, defects, and handoffs surface in real time on the floor, where a report either misses them or arrives too late to act. That’s why this discipline is led on the concrete, not the carpet.
Gemba leadership means leading from the floor, where work actually happens, instead of from dashboards and meetings. It’s how you find the real constraint, because the bottleneck shows up in real time through where WIP collects and handoffs stall. A report tells you a step backed up after the fact; presence shows you which step and why.
Where this series goes next
Working the constraint and getting on the floor are leadership disciplines. But they only hold when the culture around them holds. In Part 3, we’ll look at how culture, purpose, and learning either reinforce operational excellence leadership or quietly erode it.
Want to talk about what operational excellence should look like in your operation? Let’s connect.
Latest Insights
-
Continuous Improvement Should Be Boring. Here’s Why That’s the Point.
If your continuous improvement program requires constant heroics, it isn’t working. Learn what a sustainable daily management system actually looks like.
-
Operational Excellence Leadership Means Building a Continuous Improvement Culture
Culture isn’t a generational problem — it’s shaped by what leaders tolerate, reinforce, and ignore. In Part 3 of his Operational Excellence series, Bob…
Sign up to receive our latest insights!
"*" indicates required fields