Exploit the constraint fully before investing in expanding it — audit utilization first

Why This Is a Rule

Goldratt's Theory of Constraints prescribes a specific sequence: identify the constraint, exploit it (maximize utilization of existing capacity), subordinate everything else to the constraint, then — and only then — elevate the constraint (invest in expanding capacity). Most people skip straight from identification to elevation: "Our bottleneck is engineering capacity, so let's hire more engineers."

But if your current engineering capacity is spending 30% of its time in meetings, 20% on low-priority tasks, and only 50% on highest-value work, you don't have a capacity problem — you have a utilization problem. Hiring more engineers adds capacity to a system that wastes half its existing capacity. The new engineers will also spend 30% in meetings and 20% on low-priority tasks. You've doubled your costs while only marginally improving throughput.

Exploitation means ensuring 100% of constraint capacity goes to the highest-value work. This is almost always cheaper, faster, and more effective than elevation. Only after exploitation has been maximized — when the constraint is genuinely running at full utilization on highest-value work and still insufficient — does elevation (capacity expansion) make sense.

When This Fires

• Considering hiring to address a capacity bottleneck
• Proposing budget for new tools, infrastructure, or resources to relieve a constraint
• Any situation where "we need more X" is the proposed solution to a throughput problem
• When a constraint has been identified and the next step is "invest in fixing it"

Common Failure Mode

Treating "the team is maxed out" as evidence that capacity needs expanding. "Maxed out" means the team is working at full effort — but not necessarily on the right things. A team working 100% on a mix of high and low-priority work is not fully exploiting its constraint. Only a team working 100% on highest-value work has exhausted exploitation and needs elevation.

The Protocol

Before investing in constraint elevation: (1) Audit how the constraint's current capacity is allocated. What percentage goes to highest-value work? (2) If less than 90% → exploit first. Redirect low-priority work away from the constraint. Protect the constraint from meetings, admin, and coordination overhead. (3) Re-measure throughput after exploitation. (4) Only if throughput is still insufficient after the constraint is running at 90%+ on highest-value work → invest in elevation (hiring, tools, capacity expansion).