Operations & execution systems · strategy atlas
Theory of constraints
what it means
The idea that any system has exactly one bottleneck limiting its total output at a time, and that improving anything other than that specific bottleneck produces no real improvement in overall throughput.
a real example
Manufacturing operations that identified and fixed their single slowest station — rather than uniformly speeding up every station — often saw total output rise dramatically with far less total investment.
when to use it
Any process with a visible backlog or delay — the discipline is finding the actual constraint through data, not assuming it's wherever effort feels most obviously needed.
when it backfires
Optimising non-bottleneck steps feels productive but doesn't move total output at all — effort and money spent there is essentially wasted until the real constraint is fixed.
put it into practice