Growth operations
Operational bottlenecks in growth
The bottleneck is rarely where you think it is. It's usually one function upstream from the symptom.
Growth bottlenecks are deceptive. Revenue is stalling, so the team invests in acquisition. Churn is increasing, so the team invests in retention campaigns. Conversion is dropping, so the team redesigns the landing page. Each response feels responsive. Each addresses the symptom showing on the dashboard.
These responses address symptoms, not causes. The actual bottleneck is usually operational, a process that can't scale, a team that's misaligned, a data system that can't provide the information needed for good decisions. It sits one or two layers below the symptom, which is why the team keeps fighting the symptom and the symptom keeps coming back.
There's a useful mental model. A bottleneck is the constraint that, if relieved, would improve the whole system. The theory is old, from manufacturing, and it transfers to revenue systems cleanly: every system has one binding constraint at a time, and improving anything other than the constraint creates local improvement that doesn't move the system. Most growth teams are hard at work improving everything except the constraint.
Finding the real bottleneck requires looking at the system holistically, understanding how information flows, where decisions get stuck, and which operational constraints are creating the downstream symptoms that show up in revenue metrics. The symptom is at the surface. The bottleneck is upstream. The distance between them is why responsive growth teams keep losing ground.
The pattern we see most: a company pours acquisition spend into a top of the funnel that drains through a conversion system no one has audited, into an onboarding flow no one owns, past a pricing page no one has tested, and out a retention motion that's entirely reactive. Then it increases the spend at the top and wonders why revenue doesn't move. The bottleneck was never the top. It was the system in the middle that nobody was minding.
A diagnostic that works: walk the revenue system end to end and ask, at each stage, what's the throughput here, what's the drop-off, and what would happen if we doubled the input. The stage where doubling the input produces the smallest change in output is the bottleneck. That's where the work is. Everything else is motion.
The organizational reason bottlenecks persist is that the bottleneck usually sits between functions, and between-functions is nobody's territory. The bottleneck is owned by the seam, and the seam is owned by no one. The companies that find and fix bottlenecks give someone the explicit job of looking across the seams, because no one inside a single function can see the bottleneck that's producing their symptom.
There's a sequencing insight worth pulling out. Fix the binding constraint, and a new constraint emerges somewhere else. This is the nature of systems: you don't eliminate bottlenecks, you move them. The companies that grow reliably don't solve their bottleneck once. They build the practice of finding and moving the next one, on a cadence, before each one costs them a quarter.
The bottleneck is rarely where you think it is. It's usually one function upstream from the symptom. The teams that find it stop treating their dashboard as a to-do list and start treating it as a map of where to look next. The growth comes from fixing the thing the dashboard is pointing at, not the thing the dashboard is measuring.