If you can name three bottlenecks, you haven't found the bottleneck.
That sounds like wordplay and is not. At any moment, one thing sets your growth rate. The rest are real problems whose resolution will not move the number.
Binding constraint versus symptom
The binding constraint is the single factor whose removal immediately increases growth; a symptom is any problem that is genuinely annoying and whose removal changes nothing.
Separating those two is the entire job. Teams typically list five or six symptoms — low conversion, high churn, slow delivery, small team — and work all five at once. The result is progress on five fronts and a barely moved revenue line.
A simple test: if this problem were magically solved tonight, would you have more revenue tomorrow? For four out of five, the answer is no.
The four layers a constraint can live in
| Layer | Question | Sign it lives here |
|---|---|---|
| Demand | Do we know enough of the right people? | Good conversion, low inbound volume |
| Conversion | Do enough of them say yes? | High volume, low close rate |
| Delivery | Can we deliver what we sold? | Waitlists, delays, sales deliberately slowed |
| Retention | Do customers stay? | Healthy gross growth, flat net growth |
The fourth layer produces the most misdiagnosis. A team winning ten customers a month and losing nine feels like it has a sales problem. It does not have a sales problem.
The measurement that separates them in one week
You do not need months of data. Four numbers for the last six months are enough:
- Qualified opportunities per month.
- Conversion rate from opportunity to customer.
- Average time from contract to first delivered value.
- Net revenue retention — this month's revenue from customers you had twelve months ago.
Now find which of these stayed flat over six months while the others improved. That flat line is your constraint.
If all four are flat, the problem sits above these layers — usually in positioning or market selection.
Why teams misdiagnose
Three predictable biases, all structural rather than personal.
The loudest problem is not the binding one. A complaining customer makes noise; opportunities that never arrived make none. Attention flows toward whatever is audible.
The problem we know how to fix is more attractive. The technical team locates the constraint in the product. Sales locates it in pricing. Everyone finds it inside their own competence.
The constraint moves. Fix delivery and it relocates to demand. Teams who do not expect this conclude the previous fix did not work.
Why working all five problems is the worst option
The natural instinct on seeing five problems is to work on all five. It sounds reasonable and is in practice the worst possible allocation.
The reason is arithmetic rather than motivational. Split team capacity across five fronts and each gets a fifth of the attention — usually below the threshold that produces a measurable change. Four of those fronts have no effect on revenue anyway.
The result: all capacity consumed, five marginal improvements achieved, and the headline number unmoved. The team gets tired and concludes that business is hard.
Concentrating on one layer works precisely because it moves capacity from below the threshold to above it.
When the constraint sits above these four layers
Sometimes all four numbers are flat and fixing any of them helps nothing. Then the constraint is one level up, and it is usually one of three:
- Positioning. Your message is not written for someone who has budget and treats the problem as urgent. The sign: long sales cycles and heavy discounting.
- Market selection. The segment is not large enough, or not in enough pain. The sign: good conversion on a small volume that does not grow.
- Pricing model. Price is not aligned with the value the customer perceives. The sign: satisfied customers who never expand.
None of these is diagnosable through internal measurement. Each requires conversations with ten customers — and more importantly, ten people who did not buy.
A worked example: six months spent on the wrong layer
A B2B software company with roughly flat monthly revenue decided to invest in lead generation. The marketing budget doubled and opportunity volume grew 70 percent over four months.
Revenue barely moved.
Laying out the four numbers made it obvious: conversion had fallen from 19 to 11 percent. The sales team was still the same three people, now handling twice the opportunities, so each got half the attention.
The real constraint was conversion capacity, not demand. Six months and a doubled budget went into filling a funnel with a fixed output.
The more instructive part came next. After hiring two more salespeople, the constraint moved to delivery within three months. That was not a failure. It is what always happens.
The thirty days after you name it
Having found the constraint, the temptation is a six-month plan. What works better is smaller:
- Pick one change that acts directly on that layer and is executable in thirty days.
- Record that layer's number before starting.
- Start no new work on any other layer during those thirty days.
- On day thirty, measure again and revisit the diagnosis.
The third point is the hardest and the most valuable. Work three layers simultaneously and you will not know which change did anything.
The limits of this method
The framework works for businesses with one reasonably clear revenue path. With several products across several markets it has to be run per path — and it often returns different answers.
Equally, when the market itself is shifting, a flat number may have nothing to do with your operations. Internal diagnosis will not answer that.
What if two layers both look broken?
Usually one causes the other. High churn is often the result of weak delivery rather than an independent problem. Follow the chain until you reach a layer with no external cause.
How often should the diagnosis be repeated?
Quarterly, and immediately after any successful fix. The constraint relocates, and a diagnosis older than one quarter is not valid.
Is this the same as the theory of constraints?
Same root, applied to four business layers rather than a production line. The practical difference is that here the constraints are usually informational rather than physical.
Closing
Growth does not accelerate by solving more problems. It accelerates by solving the right one. And there is almost always only one.
If you want this diagnosis run against your own business, the growth bottleneck assessment asks these four layers in a structured way.
Comments (0)
You need to log in to post a comment.
Login / Sign up