You fixed sales. Pipeline’s up, the new hires are landing deals and the board pack finally looks healthy. Then delivery starts to creak. Deadlines slip, the best people look tired and you find yourself back on client calls smoothing things over.
That isn’t bad luck, and the sales investment wasn’t wrong. It’s what happens when the real limit was never in sales. The pressure doesn’t disappear. It moves.
Why does fixing one function so often make another one worse?
Because a business is a flow, not a set of separate departments. Work comes in, gets sold, gets delivered and (hopefully) turns into repeat business. Every stage depends on the one before it.
When sales was slow, it was doing an odd kind of favour for the rest of the business. It kept the volume of work below the point where delivery broke. Speed up sales and you remove that protection. The work now arrives faster than the weakest stage can handle it.
So the function that felt most broken was just the most visible one, not the real limit. Sales problems are loud – targets, forecasts, a number on a dashboard every week. Delivery problems are quieter until they suddenly aren’t.
What does a moving bottleneck look like in practice?
Robert Patin describes a version of this loop for agencies in episode 238 of his Agency Blueprint podcast, “Why Most Agencies Misdiagnose Their Growth Problem”. The composite Mallard sees in founder-led scale-ups looks like this. Growth stalls, so the founder backs a new sales lead and a sharper proposition. Deals close. Within a quarter or two, the people who do the work are stretched thin. Quality slips and the founder starts sitting in on client calls again to keep key accounts steady. One or two of those accounts quietly don’t renew. Growth stalls again, and the conclusion in the room is that sales needs another push.
Because the story starts and ends in sales, nobody looks hard at the middle, which is where it actually broke.
You might recognise some of the signs:
- Work queues up in one place. Projects sit waiting for a particular person, team or sign-off.
- The same few people keep rescuing things. Often the founder, plus one or two long-serving people who know where everything is.
- Rework is rising. Things get done, then done again, because the handover was thin.
- Every function says it’s fine. Sales hit its number. Delivery is “just busy”. Nobody owns the whole path from first conversation to happy client.
That last one matters. When each function is judged on its own part, every part can look healthy while the business as a whole gets stuck.
What is constraint thinking, and where does it come from?
The idea that a system can only move as fast as its tightest point comes from Eliyahu Goldratt’s Theory of Constraints, which he introduced in his 1984 business novel The Goal. It started in manufacturing, but the logic travels well.
Goldratt’s five focusing steps, in short:
- Identify the constraint that limits the whole system.
- Exploit it – get the most out of it with what you already have.
- Subordinate everything else to it, so the rest of the business supports it rather than piling work on top.
- Elevate it by adding capacity, but only once the first three steps are done.
- Go back to step one, and don’t let inertia become the constraint. Once you’ve fixed one limit, another takes its place.
That last step is the point of this whole piece. The bottleneck moving isn’t a sign you failed. It’s a sign you fixed something. The mistake is assuming the next problem will show up in the same place as the last one, or investing in a function before you know whether it’s the real limit.
In a founder-led scale-up, the constraint is rarely a machine. It’s usually one of three things:
- A person. Often the founder, sometimes a key individual everything routes through.
- A handoff. The gap between sales and delivery, or delivery and account management, where context gets lost.
- A decision. Pricing, scope or resourcing calls that wait in a queue for one person to make them.
Notice that none of those is fixed by working harder in sales.
Won’t hiring more people fix it?
Usually not, at least not first. When delivery is stretched, the instinctive answer is more delivery people. Sometimes that’s right. Often it isn’t.
If the real constraint is unclear ownership, too many handoffs or decisions stuck with one person, extra headcount just makes the queue longer. Capacity is easier to see and easier to fix, so it tends to take the blame, but more people rarely fix a design problem.
Before you add capacity, check whether you’re already getting the most from the constraint you’ve got. That’s Goldratt’s order too: exploit before you elevate.
Where should you look first?
Before you spend on another sales hire or a new tool, three checks will tell you whether it’s aimed at the constraint or just the loudest symptom.
- Trace one piece of work end to end. Pick a recent client and follow it from first conversation to the latest invoice. Note every place it waited, every handoff and every time you got involved.
- Find where work waits longest. Busy and stuck are different things, and the constraint is wherever the queue is.
- Ask what moved last time. Think back to your last big fix and where the pressure went afterwards. Then ask who owns the whole flow. If the honest answer is “nobody” or “me”, that’s worth more attention than any single function.
How do you stop chasing the bottleneck around the business?
By looking at the whole operating system before you fix any part of it. The constraint is a property of how your people, practices and technology work together, not of one function on its own. That’s why the guide to working out what’s really holding your business back starts with diagnosis rather than solutions.
If you’d like help with that, Mallard’s Find diagnostic is built for exactly this question. Over 14 days it looks at 262 operational data points across people, practices and technology, and ends with a prioritised roadmap, so the first thing you fix is the real constraint. If you already know what it is, an Improve sprint puts a senior operator alongside your team to fix it end to end.
Either way, judge the fix by whether the work got better across the whole business, not just in the function you invested in.
Contact us