The Binding Constraint
Which constraint is stopping value from compounding now?
A binding constraint is the limit that governs the whole system. Improving a non-binding part may make that part look better while the business stays stuck.
Core Move
Test value fit first. Does the offer solve a painful problem for a reachable buyer?
If value is real, test leverage and distribution:
- Leverage sets how much value each unit of time, capital, attention, and labour can create.
- Distribution sets whether that value reaches the right people through channels the business can afford and control.
| Low distribution | High distribution | |
|---|---|---|
| Low leverage | Pure grind | Demand becomes damage |
| High leverage | Elegant but invisible | A compounding flywheel |
The top-right is not a permanent state. Growth often moves the constraint to trust, capability, capital, time, focus, or coordination.
Constraint Signals
- Value: clever work without enough demand.
- Trust: attention without conversion.
- Capability: ambition without delivery.
- Capital: a viable idea that cannot survive long enough.
- Time: the right idea outside its market window.
- Focus: motion without progress.
- Coordination: local wins that weaken the whole.
The stage changes the likely constraint. Pre-revenue work often binds on value or trust. Founder-led services often bind on leverage.
A strong product with weak sales binds on distribution. Fast growth may bind on coordination, capital, or timing.
Apply It
- Name the visible problem and the outcome it blocks.
- Ask which single limit, if removed, would release the most downstream value.
- Choose the principle that explains that limit.
- Make the smallest intervention that could disprove the diagnosis.
- Read the new constraint after the result.
Proof signal: the intervention changes the blocked outcome and exposes a different next constraint.
Failure Modes
- Automating weak value fit makes waste faster.
- Adding demand to weak delivery turns sales into damage.
- Improving every metric hides the one that governs throughput.
- Treating a familiar strength as the constraint protects the operator from harder evidence.
Changes my mind: improving a non-binding area repeatedly lifts whole-system throughput more than acting on the diagnosed constraint.
Context
- depends-on First Principles — strip the diagnosis to the forces that make it true.
- applies-to Leverage — increase output without proportional effort.
- applies-to Distribution — carry proven value to reachable demand.
- proved-by Performance Reality — use gauges to test whether the constraint moved.
- pairs-with Virtuous Feedback Loop — each correction creates the next reading.
Questions
Can you explain why this constraint governs the system without naming its symptoms?
Next question: What is the cheapest intervention that could prove this diagnosis wrong?
- Which downstream outcome should change first?
- What new constraint would success expose?