Every one of these companies could tell you their revenue target for the year. None of them could tell me, without checking, how many orders their scheduling process could actually absorb per week before lead times started stretching. That gap — between the number leadership was chasing and the number the operation could actually carry — is where each of these plans quietly broke.
The plan was never the problem
In each case, the growth plan itself was reasonable. New customers, a new product line, a second shift. What wasn’t examined was whether the underlying system — scheduling, materials flow, quality checks, the informal judgment calls one supervisor had been making for a decade — could stretch to match it. Ambition scales in a spreadsheet. Capacity scales in a shop.
Growth is constrained by organizational capacity, not organizational ambition.
What actually broke first
It wasn’t the same thing twice. One company’s bottleneck was a single approval step that only one person could execute. Another’s was a stockroom that had never been asked to hold two products’ worth of buffer inventory at once. The third’s was simplest and hardest to see: nobody owned the handoff between sales and production, so orders arrived without anyone actually checking whether the floor had room for them.
None of these are dramatic failures. They’re the kind of constraint that’s invisible right up until volume tests it — which is exactly why they’re worth mapping before the growth plan is finalized, not after it stalls.
The pattern worth carrying forward
Before committing to a growth number, it’s worth asking a narrower question first: what is the slowest, least-visible step in the current operation, and what happens to it at twice the volume? That question rarely has a comfortable answer. It’s usually the right one to sit with anyway.