Spot the Real Bottleneck: Strong and Weak Approaches Compared
Eliyahu Goldratt's Theory of Constraints rests on a deceptively simple claim: in any process, one step limits the throughput of the whole. Add capacity anywhere else and nothing improves. Mid-2021, as teams rebuilt from pandemic disruption with fewer people, hybrid schedules, and supply lines that still skipped a beat, that idea carries weight. Effort is scarce. Spending it on the wrong step is a luxury no recovering operation can afford.
The trouble is that the constraint is rarely where people assume it is. The loudest complaint, the busiest-looking desk, and the step everyone already dislikes are all poor evidence. Finding the true bottleneck is a discipline, and the gap between doing it well and doing it badly decides whether your improvement work pays off or just rearranges the queue.
What weak constraint-finding looks like
A weak approach starts from opinion and ends in motion that feels like progress. It usually shows up like this:
The team improves the step with the angriest stakeholder, not the slowest one.
Capacity is added to a station that already has work waiting in front of it, so the new capacity sits idle.
Local efficiency targets push every station to stay 'busy', which buries the real constraint under piles of work-in-progress.
Nobody measures throughput before and after, so a change gets declared a success because people are tired and the dashboard looks greener.
The tell is that overall output does not move. You relieved a step that was never the limit, and the queue simply re-formed somewhere upstream. Worse, in a hybrid setup the bottleneck is often a handoff — an approval waiting on one reviewer, a shared file that only one person updates — and a busyness-based view never even looks there.
What strong constraint-finding looks like
A strong approach treats the constraint as a fact to be located, then exploited before it is enlarged. Goldratt's five focusing steps give the order:
Identify the constraint. Walk the process and find where work piles up in front of a step and starves the step after it. Inventory accumulating before a station, and idle time after it, is the physical signature of the bottleneck.
Exploit the constraint. Wring every unit of capacity from it before spending a dollar. Stop it from working on defects, give it priority on inputs, and never let it sit idle waiting on a setup or a missing approval.
Subordinate everything else. Pace the rest of the system to the constraint. Running upstream stations flat out only grows the pile and hides the problem; they should produce at the bottleneck's rhythm.
Elevate the constraint. Only now add real capacity — a second reviewer, another machine, an extra shift — because you have proven this is the step that limits throughput.
Repeat. Once the constraint moves, a new step becomes the limit. Go back to step one, and guard against inertia keeping old rules in place.
Notice the order. Exploit and subordinate come before you spend money to elevate, which is the opposite of the reflex to throw resources at the problem. Much of the time a constraint can be relieved for free, simply by stopping it from doing work that something else should do.
How to tell which one you are doing
Two questions separate the strong approach from the weak one. First: where does work wait? Track queue length and waiting time across the steps, not how occupied each person looks. The constraint is the step with a growing line in front and starvation behind, full stop. Second: did total throughput change? Measure output for the whole system before and after, not the speed of the single step you touched. If end-to-end throughput did not rise, you did not improve the constraint, whatever the local numbers say.
This is also where Lean Six Sigma and the Theory of Constraints reinforce each other. The constraint tells you where to aim; DMAIC gives you the rigour to confirm the cause and prove the gain. Define the throughput problem, measure the queues, analyze why the bottleneck step stalls, improve it in the right order, and control it so the gain holds and the next constraint is caught early.
If your recovery plan depends on getting more out of the same people and the same lines, finding the real constraint first is the difference between effort and results — and XNM's strategic advisory can help you locate it and act in the right order.