The whole argument, in fifteen lines.

Adding more balls at the entrance does not necessarily increase what comes out.

The result of any system is produced by the flow that crosses its elements, not only by the elements individually.

Most of the time lost in any system is not in the work, but in the waiting between the work.

Every chain has a constraint that governs the performance of the entire system.

Local efficiency can rise while the global result gets worse; being busy is not the same as delivering.

Excess work released into the system creates queues, raises WIP, and stretches lead time, without increasing delivery.

The first step to recover a congested system is to limit the release of work, not to accelerate it.

A system’s performance does not come from every resource running free, but from all of them marching to the constraint’s beat.

Well-placed buffers make flow reliable even in the face of the unexpected, and they also show where to act.

A system’s capacity is not the sum of local capacities; it is set by the element with the least capacity for flow.

Throughput, Inventory, and Operating Expense reveal the true economics of flow, and the constraint decides the priority.

The quality of a system’s results is limited by the quality of the decisions made about its constraints.

Multitasking wastes the constraint’s capacity in context-switching: the more simultaneous tasks, the less flow the system generates.

Technology amplifies the existing system; it accelerates movement, but does not replace discernment about what deserves to be accelerated.

In the abundance of information, attention has become the universal constraint.