Only optimize the constraint — verify that improving…
Before attempting to improve a feedback loop component, verify it is actually the constraint by measuring whether improvements there would increase total system throughput, as optimizing non-constraints produces local gains without system-level improvement.
When This Fires
- Before investing effort in improving any component of a feedback loop
- When loop optimization isn't producing system-level improvement — you're probably optimizing a non-constraint
- When deciding which of several possible improvements to prioritize in a loop
- Complements Strengthen virtuous loops through one lever at a time (strengthen reinforcing loops) with the diagnostic for where to apply the intervention
Common Failure Mode
Optimizing the easiest component rather than the constraint: "Let's improve our data collection because that's straightforward." If data collection isn't the constraint (maybe it's analysis speed or decision implementation), improving it produces better data that piles up waiting for analysis. You've invested in a non-constraint while the actual bottleneck remains unchanged.
The Protocol
(1) Map the feedback loop: identify each component and the flow between them. (2) For each component, ask: "If I doubled this component's capacity, would the loop cycle faster or produce better output?" (3) The component where doubling capacity would most increase system throughput is the constraint. (4) Optimize only that component. Use the three levers from Strengthen virtuous loops through one lever at a time (reduce friction, increase gain, shorten cycle time) applied to the constraint specifically. (5) After improving the constraint, re-assess: the constraint has likely moved to a different component. Repeat the diagnostic. (6) The constraint moves with each improvement. This is expected — it means the system is improving. Follow the constraint.