The primary goal of any business is to make money now and in the future. All actions should be evaluated based on whether they help achieve this goal.
Every system has at least one constraint that limits its performance. Identifying and managing this constraint is crucial for improving overall throughput.
A bottleneck is any resource whose capacity is equal to or less than the demand placed upon it. Non-bottleneck resources have capacity greater than demand. The key is to optimise the bottleneck, not every resource.
In any process with dependent events and statistical fluctuations, delays accumulate but gains do not. This causes inventory to build up and throughput to decrease.
Optimising individual parts of a system does not necessarily optimise the whole system. Focus should be on the system's overall performance, not individual efficiency metrics.
A production scheduling methodology where the bottleneck sets the pace (drum), buffer inventory protects against disruptions, and rope controls the release of materials into the system.
Improvement is not a one-time event but a continuous process. Once one constraint is resolved, another will emerge, requiring ongoing attention and refinement.
During a hiking trip with his son's scout troop, Alex Rogo discovers a powerful metaphor for understanding constraints in manufacturing through a boy named Herbie.
The scout troop sets off on a hike, but the line of boys quickly spreads out. Herbie, the slowest boy carrying the heaviest pack, falls behind, creating a growing gap between the front and back of the line. Despite the fastest boys at the front moving quickly, the group as a whole cannot arrive at their destination any faster than Herbie's pace allows.
Alex realises the hiking trail experience directly mirrors his factory problems:
This analogy reveals that maximising the efficiency of every resource (making every hiker walk faster) doesn't improve system performance. Instead, the key is to:
The breakthrough realisation is that an hour lost at the bottleneck is an hour lost for the entire system, whilst an hour saved at a non-bottleneck resource is merely a mirage that doesn't improve overall throughput.