Constraint

Effort spent away from the constraint feels productive and changes nothing. A team that doubles lead volume while the demo calendar is full gets longer queues, not more revenue. Founders also tend to work on the stage they enjoy or can see most easily.

Finding the constraint focuses limited time on the one place where it pays back. It also gives a clear order of work: fix the constraint, re-measure and move to the next one. When the constraint shows up as work queuing at one stage, it is also called a bottleneck. The full method for managing it is the Theory of Constraints.

1. Map the engine. List the stages from first visit to retained revenue, in order.
2. Measure each stage. Record volume in, volume out and time taken for the last 8 to 12 weeks.
3. Find the narrowest stage. Look for where work queues up, where capacity is fully used, or where the conversion ratio is lowest compared with what the stage before can supply.
4. Check it with a question. If this stage doubled its output tomorrow, would total revenue rise? If yes, it is the constraint.
5. Work on that stage only. Remove waste first, then add capacity, then change the process.
6. Re-measure monthly. Fixing one constraint exposes the next, so repeat.

A constraint is the one stage in a growth engine that limits the output of the whole system. Lead generation, sales calls, onboarding and delivery all run at different speeds, and the slowest one sets the pace. Speeding up any other stage does not raise output until the constraint moves.

A business has one main constraint at any time. It can sit in marketing (too few qualified visitors), sales (too few meetings), onboarding (too slow to go live) or capacity (too few people to deliver). It can also be a policy, such as an approval rule that holds every deal for a week.

• Naming the stage that feels most broken instead of the one that measures narrowest.
• Treating every weak metric as a constraint. Only the one that limits total output counts.
• Fixing the constraint once and moving on, when the next one appears immediately.
• Keeping idle capacity to hide a constraint, for example a sales team waiting on a slow onboarding stage.
• Confusing a constraint with a lack of effort, when the cause is a rule, a tool or a person.