Every system has one binding constraint, and improvement anywhere else is an illusion that shows up as inventory rather than throughput. Find the constraint, protect it, subordinate everything to it, then elevate it - and expect the constraint to move once you do. In business analysis it explains why capex in the wrong place buys nothing.
A plant manager learns that a system's output is set by its bottleneck.
Recommended by: Mohnish Pabrai, Nat Eliason and 5 others
Meadows wrote this before systems thinking became a popular phrase, and it remains the clearest account of why short-term interventions in complex systems so often backfire. The chapter on leverage points is the conceptual core of what long-term thinking actually requires from decision-makers.
Recommended by: Patrick O'Shaughnessy, Daniel Burka and 3 others
A novel in which an IT manager rescues a failing project using lessons from The Goal.
Every system has one constraint; find it, exploit it, and subordinate all else to it.
A novel applying the theory of constraints to finishing projects on time.