thinking-theory-of-constraintslisted

# Theory of Constraints ## Overview The Theory of Constraints (TOC), developed by Eliyahu Goldratt in "The Goal," states that every system has exactly one constraint that limits its throughput. Optimizing anything other than the constraint is wasted effort—even counterproductive. Find the bottleneck, exploit it, subordinate everything else to it, and only then consider elevating it. **Core Principle:** A chain is only as strong as its weakest link. Strengthening any other link does nothing. ## When to Use - Performance optimization (systems, processes, teams) - Process improvement - Resource allocation - Throughput analysis - Project management - Capacity planning - Any optimization effort Decision flow: ``` Trying to improve throughput? → Have you identified the constraint? → no → FIND THE CONSTRAINT FIRST → Are you optimizing a non-constraint? → yes → STOP, FOCUS ON CONSTRAINT → Is the constraint working at 100%? → no → EXPLOIT BEFORE ELEVATING ``` ## The Five Focusing Steps ### Step 1: Identify the Constraint Find the one thing limiting the system: ```markdown ## Constraint Identification System: Software delivery pipeline Potential constraints: | Stage | Capacity | Utilization | Queue Time | |-------|----------|-------------|------------| | Requirements | 10/week | 60% | 0 days | | Development | 8/week | 95% | 3 days | | Code Review | 5/week | 100% | 5 days |←CONSTRAINT | Testing | 12/week | 40% | 0 days | | Deployment | 20/week | 20% | 0 days | Constr