Description
Identifies the single constraint limiting a system's throughput and improves it first, recognising that improvements elsewhere do not raise overall output.
Goldratt argued every system has at least one constraint that determines throughput. The five focusing steps are: identify the constraint, exploit it (get maximum from it), subordinate everything else to it, elevate it (add capacity), and repeat as the constraint moves. TOC's thinking processes (current reality trees, evaporating clouds) extend the logic to policy constraints. In UX and service design, constraints may be a verification step, a scarce expert, an approval policy or a user's limited attention. Teams often optimise non-constraints, such as polishing early funnel steps when the bottleneck is a manual review, achieving nothing.
Attributes
- Discipline
- Systems & Complexity
- Loss type
- Unmigrated
- Stage
- Definition, Post-launch
- Data
- Mixed
- Effort
- Days
Steps
- Define the system's goal and throughput measure (e.g. completed onboardings per week).
- Map the flow and measure capacity and queues at each step to find where work accumulates.
- Confirm the constraint (the step with highest utilisation or growing backlog).
- Exploit it: remove waste at the constraint (e.g. pre-check documents before human review).
- Subordinate other steps: pace intake to the constraint, avoid flooding it.
- Elevate if needed, then re-measure to find the next constraint.
Sources
- Goldratt & Cox, The Goal: A Process of Ongoing Improvement (1984)
- Goldratt, What Is This Thing Called Theory of Constraints (1990)
Also known as
- TOC
- Five focusing steps
- Drum-buffer-rope
- Bottleneck analysis
Categories
- Strategy & Collaboration
- Systems & Complexity