domains / families / general / thinking-theory-of-constraints

thinking-theory-of-constraints

separate

When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.

When to use

• Latency or throughput goal where one stage dominates time or rate.
• Work piles up before one stage; downstream idles.
• Adding capacity/workers elsewhere does not raise end-to-end output.
• Need ordered plan: exploit cheaply before spending to elevate.

When not to use

• Load is spread; no stage dominates—use systems for interactions.
• Problem is correctness/fault, not flow rate—debug the fault.
• Bottleneck hops every run due to coupling/contention without a stable stage—systems or concurrency design, not five focusing steps.
• Constraint already known and a cheap fix is ready—apply it without ceremony.

Skill page

Source