Are You Fixing the Right Problem?
Focus on the real bottleneck
There is a particular kind of frustration that is hard to name at first. You are putting in the work. The campaigns are running, the headcount is up, the energy is visible. And yet the problem stubbornly refuses to move. In fact, it seems to be getting worse.
This is what I want to explore in this issue. Not busyness in general, but a specific and costly version of it: the tendency to pour resource and effort into the most visible part of a problem, while the actual constraint sits quietly elsewhere, untouched.
The Idea Behind the Framework
Back in 1984, a physicist-turned-management-thinker named Eliyahu Goldratt published a book called The Goal. It was written as a novel, which is an unusual choice for a business book, but it remains one of the most practically useful works in the genre. His central idea, the Theory of Constraints, is built on something deceptively simple.
Every system has a bottleneck: a single point that limits the output of the whole. And here is the part that matters most. It does not matter how efficiently everything else is running. If you are not addressing that bottleneck directly, you are not improving the system. You are adding pressure to a pipe that is already blocked.
The difficulty is that the bottleneck is rarely the most visible point of failure. It is often embedded in something politically sensitive, technically complex, or simply uncomfortable to examine. So organisations go somewhere else. They add resource to a part of the system that is already flowing reasonably well, launch initiatives that look energetic and impressive, and call that progress. Activity is not the same as impact.
A Story About Apples
Picture a family-run apple farm in rural Somerset. Good orchards, healthy crop, and a persistent problem: roughly half the fruit they sent to market was arriving bruised, damaged, or late. The reason was the farm track, a rough dirt road full of ruts that battered every load before it reached the highway.
The family’s response was logical on the surface. If you are losing fifty percent, grow more. Double the harvest and you will be ahead even with the losses. So they planted more trees, hired more pickers, and sent more lorries down the same broken road. What followed was not recovery. The loads were heavier, the drivers pushed harder, the bruising worsened, and the attrition rate climbed from fifty percent to seventy. The barns filled with rotting fruit.
Eventually, someone stepped back and looked at the whole picture. Not the picking. Not the storage. Not the market strategy. The road. They made a counter-intuitive decision: they reduced the harvest deliberately, cutting volume back to premium-only fruit. The lighter loads travelled more gently, the attrition rate fell, and they finally had the breathing space to resurface the track. Once they did, they could ramp up again with a system that could actually handle it.
The lesson is not that you should always do less. The lesson is that sometimes the most productive move is to slow the pipeline while you fix the bottleneck. That takes nerve, because it looks like retreat. It is not. It is precision.
Where This Plays Out in Organisations
This pattern repeats itself across industries with striking regularity. Three examples show the same underlying dynamic, each wearing a different face.
In software development, a team under pressure to deliver faster brings in more developers. Code is written at speed. And yet delivery slows, the backlog grows, and frustration mounts. The bottleneck was never in development. It was in the quality assurance and testing function, a fraction of the size. Every developer added simply fed more work into an already-overwhelmed queue. The fix is not more developers; it is more testing capacity, and a sensible limit on how much development work can be pushed forward at once.
In recruitment, an organisation losing candidates between offer and start date responds by expanding the pipeline. More campaigns, more interviews, more volume at the front end. But a bigger pipeline flowing into the same blocked vetting stage simply means longer waits. Candidates who would have waited six weeks will not wait fourteen. The attrition rate increases, and the organisation keeps investing heavily in activity that is compounding the problem rather than resolving it.
In retail, a national chain with healthy footfall and strong basket sizes is losing revenue to poor conversion. More promotions are launched, more staff added to the floor, more visual merchandising invested in. The problem persists. The customer journey data, when someone finally looks at it properly, shows that people are abandoning full baskets at the checkout. The wait times are too long, the self-service machines unreliable. Everything upstream is performing well and being further invested in, while the actual point of failure goes untouched. Fix the checkout and revenue recovers almost immediately, not through clever strategy, but through finally targeting the constraint.
Why Leaders Avoid the Bottleneck
If the logic is this clear, why does the pattern repeat itself so persistently? There are a few honest reasons worth naming.
The first is visibility. The constraint often sits where the difficult, politically sensitive, or technically complex work lives. Addressing it means challenging existing processes, redirecting resource from activity that looks good on paper, and telling people that the busy, visible thing they are doing is not the most important thing. That requires a kind of courage that does not always get short-term recognition.
The second is that misdirected activity still feels like progress. In organisations with strong accountability cultures, doing something is always more comfortable than pausing. Leaders receive credit for launching campaigns, increasing headcount, showing urgency. That is a deeply human dynamic, and pretending otherwise does not help anyone.
The third is that the constraint is not always obvious without proper analysis. The apple farm family genuinely believed more picking was the answer. They were not foolish; they simply lacked visibility of the whole system.
In Enhanced Leadership, I write about the pull that many leaders feel back towards familiar, technical work when things are under pressure. The harder discipline is to lift your head, look at the whole system, and ask an honest question: where is the constraint, and am I pointing effort at it, or am I doing more of what I already know how to do?
What Good Looks Like in Practice
Leaders who navigate this well tend to share a few qualities. They are curious about the whole system. They ask where things are slowing down, where the queue is building, where the attrition is happening. They look for the pile of rotting apples rather than celebrating the speed of picking.
They also resist vanity metrics: any measure that looks impressive but does not reflect progress on what actually matters. Number of applications received is a vanity metric if the constraint is processing speed, not volume. Lines of code written is a vanity metric if the bottleneck is testing. Promotions launched is a vanity metric if customers are abandoning at the checkout. The useful question is always what does this metric actually tell us about system flow?
And they are willing to be diplomatically direct. When the constraint sits in a difficult place, the effective leader does not pretend it is somewhere more convenient. They name it carefully, frame it constructively, and make the case for why it deserves attention. That is strategic clarity combined with good communication, and it is one of the most valuable things a leader can offer their organisation.
A Note for Coaches
If you work with leaders, this framework surfaces some rich territory. The most common pattern to watch for is a client who is genuinely working hard, fully committed, and still not moving the needle. The instinct is often to work harder on the same things. Before helping them build a better plan, it is worth asking: have they identified the actual constraint, or are they just adding lorries to a broken road?
A few questions worth exploring in session: where is the queue building in their team or organisation right now? Which part of the system is the bottleneck, and why has it been left unaddressed? What would it take to slow the pipeline temporarily in order to fix the underlying problem? And what would they need to say, to whom, to make that case?
The answers are often already present. What is missing is the permission to look at the uncomfortable place.
The Question to Sit With
Before you close this, take a moment with this question.
Think about the problem in your organisation that has the most resource pointed at it right now. The most activity, the most budget, the most visible effort. Ask yourself honestly: is that effort aimed at the actual constraint? Or is it aimed at the part of the problem that is most visible, most familiar, or most comfortable to work on?
If you are not sure, finding out might be the most important thing you do this week.
If this has been useful, I would love it if you passed it on to a colleague who is working hard on a problem that does not seem to move. Sometimes the missing piece is simply knowing where to look.
