Theory of Constraints: Why More Effort Points at the Wrong Problem

Lee: What if everything you're working on so hard is making your problem worse? What if the busyness, the campaigns, the extra resource, the visible effort is not solving anything at all because it's all pointed in the wrong place? What if the real constraint is somewhere far less comfortable, somewhere nobody wants to look? That's what this episode's all about. Hello and welcome to the Level Up Leadership Podcast. I'm Lee, and today I want to talk about one of the most consistent and costly mistakes of leadership, and honestly, one of the most underappreciated. It's the tendency to do more of what is easy and visible, rather than tackling what is genuinely constraining progress. We've touched on this theme of busyness versus impact in a couple of episodes, but today I want to go deeper because there is a specific pattern here that I think deserves its own space. I've seen it in organisations of every size and type. It shows up in strategy, in operations, in people and processes. And, uh, the reason it keeps showing up is that the wrong activity tends to look from the outside exactly like the right activity. So in this episode I'm going to introduce you to a framework that fundamentally changed how I think about where to point effort. I'll tell you a story about an apple farm, which I promise is more useful than it sounds. Then I will walk through three real world scenarios where this mistake plays out in corporate life. And by the end, I want to leave you with a question that you will want to sit with for a while. Let me start here. A long time ago, a physicist turned management thinker named Eliahu Guldrat wrote a book called the Goal. It was published in 1984 and it's still, in my view, one of the most practically useful business books ever written, even though it was written as a novel, which is quite an unusual choice. The central idea is called the theory of constraints, and it is built on something deeply simple. Every system, every process, every pipeline has a bottleneck, a single point that limits the output of the hole. And here's the insight that makes this really powerful. It does not matter how efficiently everything else in the system is running. If you are not addressing the bottleneck directly, you are not improving the system. In fact, you might be adding pressure to a pipe that is already firmly blocked. What makes this really tricky in practice is that the bottleneck is often not the most visible point of failure. It's often not the most comfortable place to intervene. It frequently sits in a location that could be politically sensitive, technically complex, or deeply embedded in how Things have always been done. So what tends to happen is that organisations go somewhere else. They add resource to a, uh, part of the process that is already flowing reasonably well. They launch initiatives that feel energetic and look impressive, and they call it progress. Activity is not the same as impact. And adding resource to the wrong place does not just fail to solve the problem, it can make the problem worse. Let me tell you the story of the apple farm to show you what I mean. Imagine a family run apple farm in rural Somerset, uk. They grow good apples, the orchards are healthy, and for years the operation ticked along reasonably well. But they had a persistent frustration. About half the apples they sent to market were arriving bruised, damaged or on the turn. The reason was the farm track. It was an old dirt road, barely maintained, full of ruts and potholes. The lorries that carried the fruit bounced along it, and by the time they reached the main highway, the damage was done. The apples that sat at the bottom of the crates bore the worst of it. And even when the apples made it to market in reasonable condition, the delays from the slow, difficult drive meant they were often arriving late in the trading day, when buyers had already made their purchases elsewhere. So the farm was losing around half of its revenue to attrition. The family's response to this was logical, at least on the surface. If we're losing 50%, they reasoned, let's grow more. Let's double the harvest. Then even with the losses, we'll be ahead. So they planted more trees, hired more pickers and doubled their volume. What followed was not the improvement they wanted. The lorries now had twice the load. Drivers were under pressure to make multiple runs, push a little harder down that track. The ride got rougher, the bruising got worse. The delays stretched longer because there were simply more loads to move. What had been 50% attrition crept up to 70% attrition. They were growing and picking more apples than ever and losing more of them than ever. The barns filled up with rotting fruit. The smell of waste was everywhere. And because the response to increasing losses was always to pick more, the cycle just kept tightening. At some point, eventually, someone in the family had the clarity, or perhaps desperation, to stop and look at the whole picture. Not the picking, not the storage, not the market strategy, that road. What they did next was counterintuitive enough that not everyone agreed with it at first. They decided to massively reduce the harvest, deliberately and significantly. Instead of picking everything, they picked selectively, only the best, most premium fruit. They cut the volume they were sending to market, which felt on the face of it, like giving up. But here's what happened. The lighter loads traveled more gently. The attrition rate dropped from 70 back down to 50 and then eventually even lower to 30. The apples that arrived were premium quality and commanded better prices. Revenue stabilised and crucially, they'd freed up more time than they had before. They had more time, resources and headspace to do the thing that they had never fixing that road. They invested in resurfacing the track. Now, that's not glamorous work. It didn't make a great story at the time, but once it was done, they could ramp the pipeline back up and this time the system could actually handle it. Volume, quality and delivery speed all improved together because the constraint had been addressed rather than worked around. The lesson is not that you should always do less. The lesson is that sometimes the most productive thing you can do is is to slow down the pipeline while you fix the bottleneck. That takes real nerve, because it looks from the outside like a retreat. Let me walk through three scenarios that might feel a bit closer to home in corporate life, because I've seen this pattern play out all over the place. Each of these scenarios looks different on the surface, but the underlying dynamic is the same. The first comes from the world of software development. A team is under pressure to deliver features faster. Leaders respond, hire more developers, the team grows, coding is being written faster than ever and yet delivery does not speed up. The backlog gets worse, not better. What is actually happening is that the bottleneck is not in development. It's in the quality assurance and testing function, which is a fraction of the size of the development team. For every developer added, more work is being fed into the testing queue that is already overwhelmed. Untested, um, code piles up, features sit idle waiting for sign off. Adding developers does not help. The intervention that actually changed things is adding testing capacity and putting a sensible limit on how much development work can be pushed forward at once so that the flow matches what the downstream process can absorb. The second example is one that will be familiar to anyone who has led large recruitment or onboarding processes. Imagine an organisation that needs to bring people through a vetting or compliance stage before they can take up their roles. That stage takes time, sometimes a considerable amount of time. The organisation starts to notice that it's losing candidates between offer and start date. People accept roles and then drift away before they can ever start. The response is to increase recruitment activity, run more campaigns, advertise more widely, interview more candidates, build a bigger pipeline at the front, so that even with Some attrition. Enough people will come through the other side. It looks proactive and it feels like momentum. The problem though is that the bigger pipeline flow into the same blocked stage is making things worse. The vetting queue gets longer. Candidates wait even more. People who might have waited six weeks are not willing to wait 14. The attrition rate increases. The organization is investing significantly in activity that is compounding the constraint rather than resolving it. The recruitment effort, UH is visible, energetic and well intentioned. But in terms of system flow, it is picking more apples and sending more lorries down the same broken road. What actually needs attention is the middle stage itself. An honest examination of, uh, what is slowing it down, and a targeted investment in removing those specific friction points. Whether that's more resource at that stage, a process redesign, better technology, or a sharper conversation about what that stage genuinely needs to include in order to be both thorough and timely. The third example comes from retail. A national chain is losing customers. The instinct is to invest in more promotions, better merchandising, new visual displays and more staff on the shop floor. All of that happens, but the problem persists. Eventually, a uh, proper look at the customer journey data reveals that the bottleneck is to checkout. Wait times have crept up. Self service machines have reliability issues. People are physically abandoning full baskets and walking out. Everything upstream at that point is performing well and being further invested in. While the actual point of failure has been overlooked entirely. The fix is not complex. Once the problem is identified, additional staffing at UH peak times, proactive maintenance of the checkout of equipment, and a dedicated queue management approach. Revenue recovery is almost immediate. Not because anyone found clever new strategies, but because they finally targeted the constraint instead of everything around it. So if the logic is this clear, why does the pattern repeat itself so reliably? I think there's a few honest reasons worth naming. The first is visibility. The bottleneck is often where the difficult, political, sensitive or technically complex work lives. Going after it requires the kind of courage that does not always get rewarded in the short term. Challenging an existing process, redirecting resource from activity that looks good, telling people that the busy thing they are doing is not the most important thing at all, that doesn't go down well. The second is that activity in the wrong place still feels like progress. It satisfies the need to do something. Leaders can get credit for launching campaigns, for increasing headcount, for showing urgency. That is a very human dynamic, and it's worth being honest about. The third is that the constraint is not always obvious. Without proper analysis, the Apple Farm's family genuinely believed picking more apples was the answer. They were not wrong to think it might work. But what they lacked was visibility of the whole system, not just their part of it. In my book Enhanced Leadership, I write about the pull that many leaders feel back towards the familiar technical work. Especially 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, um, I actually pointing effort at it? Or am I, uh, just doing more of what I know how to do? Leaders who do this well tend to share a few characteristics. They are curious about the whole system. They ask where things are actually 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 resist vanity metrics. A vanity metric is any measure that looks impressive but does not actually reflect real progress on the thing that matters. Number of applications received is a vanity metric. If the constraint is not the volume, but the processing speed. Lines of code written is a vanity metric. If the bottleneck is testing. Volume of footfall after promotions launched is a vanity metric. If customers are abandoning the checkout. The useful question is always what does this metric actually tell us about the system? And those leaders 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 build the case for why it deserves attention. It doesn't have to be bluntness. It is just strategic clarity combined with good communication. Perhaps most significantly, those leaders are willing to slow the pipeline before they speed it up. This is the counterintuitive move, the one that feels like a retreat, but is actually precision. The apple farm did not recover by picking faster. It recovered by picking better, briefly doing less, and using that breathing space to fix the road. That takes confidence and uh, it takes the willingness to tolerate short term discomfort for the sake of a system that, that actually works. Before you go, here's the question I want to leave you with today. Think about the problem in your organization that has the most resource pointed at it right now, the one with the most activity, the most budget and the most visible effort. And ask yourself honestly, is all of 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're not sure, then it might be the most important thing you do this week to find out if this episode has given you something useful, I would love you to pass it on to someone else who's working on problems, who doesn't seem to be moving the needle as much as they want to. Sometimes the missing piece is simply knowing where to look. So please like and subscribe and share the podcast wherever you're listening. And until next time, keep leading, keep learning and keep levelling up.

Speaker B: You've been listening to the Level Up Leadership podcast. If you found this episode, that probably means you're a leader looking to level up their leadership game. If that's right, make sure you follow us and subscribe wherever you find your podcasts. We're available on all major platforms. If you subscribe to our YouTube channel, you'll see we regularly have additional bite sized mini clips of the most important points. And if you subscribe to our main hub on levelupleadership.uk that's all one word, levelupleadership.uk you'll have access to the articles that come with each episode, as well as additional bonus articles, some of which are guests or collaborations with other writers. Make sure you follow and subscribe to Level Up Leadership now.