Theory of Constraints

A method for improving any system by managing its constraint, through five focusing steps: identify the constraint, exploit it (get the most from it as it is), subordinate everything else to it, elevate it (add capacity), then repeat, without letting inertia leave an old constraint in place.

Why it Matters

Because the constraint governs throughput, ongoing improvement means continuously locating and relieving it. The five steps give a repeatable, focused process instead of scattering effort across the whole system.

Signals

• Improvement programs spread evenly across all resources.
• Gains that never reach the bottom line.
• An old fix still treated as the constraint after the limit has moved.

Benefits

A disciplined cycle of improvement focused where it pays; subordination keeps non-constraints from undermining the constraint.

Risks

Skipping "exploit" and jumping straight to expensive "elevate"; stopping after one cycle; inertia, defending policies built around a constraint that no longer binds.

Tensions

Subordinating non-constraints means deliberately under-using them, which fights local efficiency goals and looks wasteful.

Examples

Offloading work from a bottleneck machine and feeding it steadily (exploit, subordinate) before buying a second one (elevate); re-checking what limits delivery after the previous bottleneck is resolved.