How to work out which part of your business to fix first
The most expensive mistake in operations is not making the wrong decision. It is solving the wrong problem.
A founder buys a project management tool to fix coordination, then a CRM to fix sales tracking, then a separate quoting tool. A year later there are five systems, three of them half-used, none of them talking to each other, and the team is back to managing things in spreadsheets.
Another founder hires an operations manager to take work off their plate. Six months later the founder is still in every decision because the operations manager cannot act without their input. The role was the fix. The decision rights structure was the actual problem.
Each of these costs time and money. Each of them was a fix without a deep diagnosis.
This article is about how to think diagnostically before you act, i.e. assessing the root cause before you act. The discipline of working out what is actually broken, not what appears broken at first glance. For founder-led businesses where operational efficiency is the difference between scaling and stalling, this is the skill that decides where every operational pound goes.
We have frequently undertaken assignments where we were asked to address specific pain points, only to discover deeper-rooted issues once our initial analysis concluded. While the client’s initial observations were not incorrect or asymptomatic, they were just not the primary drivers of the problems as they manifested.
Why founders misdiagnose their own businesses
Founders are closer to their businesses than anyone else. That proximity is usually an advantage, but in diagnosing problems in their business it works against them.
When you are inside the business every day, you see symptoms. Symptoms are loud. Cash is late. Clients are complaining. The team is stretched. Diagnosis means slowing down long enough to ask what is causing the symptom, and that is hard to do when the symptom is on fire.
The result is a predictable pattern of misreads. Most of us are familiar with at least one of these.
Cash flow problems blamed on the finance team. The invoices go out late. Follow-ups are inconsistent. Cash takes too long to land. The natural conclusion is that finance is not on top of it. The actual cause is usually upstream: a quoting workflow with no defined handoff to delivery, an invoicing process that depends on someone remembering to trigger it, sales and finance systems that do not talk to each other. Finance is the visible end of a broken chain. Replacing the finance manager fixes nothing.
Capacity problems blamed on people. The team is working long hours. Output does not match the effort. The instinct is to hire. Sometimes that is right. More often, the team is doing too much manual work because the workflows have not kept up with the size of the business. Hiring into a broken workflow gives you two people doing inefficient work instead of one. The cost goes up. The capacity does not.
Visibility problems blamed on tools. The founder cannot see how the business is performing. The conclusion is that the business needs a better reporting tool. Then the dashboard arrives and nobody trusts the numbers because the data going in is fragmented across five systems with no agreed source of truth. The tool is not the problem. The data structure underneath it is.
There is a fourth pattern worth naming, because it is becoming common.
AI blamed for not delivering value. Founders buy AI tools, embed them in workflows that are not ready, and then conclude AI does not work for their business. We covered this in detail in our analysis of the Deloitte AI report but the principle holds here too: the tool is not the problem when the foundation is not ready for it.
In each case, money gets spent. The symptom does not go away. The founder concludes the fix did not work, when the truth is the fix never addressed the cause.
The cost of fixing the wrong thing first
Misdiagnosis carries a financial cost as well as a strategic one.
Every operational pound spent on the wrong fix has three costs. The cost of the fix itself. The cost of the disruption it causes (new tool to learn, new hire to onboard, new process to adopt). And the cost of the underlying problem continuing to drain the business while the fix runs its course.
A small to medium sized business that misdiagnoses one operational problem a year and spends, conservatively, twenty thousand pounds chasing the wrong fix is not just out the twenty thousand. It has lost six to twelve months of trading where the real problem kept compounding. By the time the founder works out the fix did not land, the original problem is more pronounced and harder to unwind.
On a client engagement a few years ago, we were asked to review vendor management practices. The client had workflows in place to keep operations running, but they were inadequate, and the organisation continued to lose money through poor service delivery. During the briefing, we were told that legal had already reviewed the service level agreements and operations had improved handoffs. However, our investigation found the real issue was more fundamental: the organisation lacked a granular service catalogue. Without that, it could not properly define what vendors were accountable for, measure performance, or assess value for money. It was a clear example of how the apparent problem at the surface can be different from the root cause underneath.
The discipline that prevents this is not complicated. It is just rare. Surface the real issue first. Fix second. The order matters more than the speed.
How do you work out which part of your business to fix first?
There are two questions to answer, in this order. Where to look. Then how to look once you are there.
Where to look. When something feels off in a growing business, the cause sits in one of a small number of places. The way work is structured (process). The tools that hold the business together (systems). How work moves between people and stages (workflows). Who owns what (people). What is automated and how it is governed (automations, bots or AI agents).
Those five places roll up into three operational areas where strain tends to show up. Cash flow, operational control and visibility, and workflow efficiency. Pick the symptom, and the cause usually sits somewhere in this map.
That is the where. The how is a separate discipline.
How to look: the 5 Whys. This is a root cause analysis technique that came out of lean manufacturing, originally developed inside Toyota. The idea is simple. When you find a symptom, ask why it is happening. Then ask why that is happening. Then again. Keep going for roughly five iterations. By the fifth why, you are usually past the surface fix and into the structural cause.
Worked example. Take the operations manager hire from earlier.
Symptom: the founder is still in every decision after hiring an operations manager.
Why? The operations manager keeps escalating decisions back to the founder.
Why? They are not sure which decisions they are allowed to make on their own.
Why? Decision rights have never been written down or agreed.
Why? The business has always run on the founder making the call, so the question never came up.
Why? The structure that defines who decides what has not kept pace with the size of the team.
Five whys in, you have moved from "the operations manager is not stepping up" to "the business has no defined decision rights structure". The fix is to design and agree the decision framework, not to replace the operations manager. A second hire into the same structural gap would produce the same result.
The 5 Whys looks almost too simple to be useful. It is not. The reason it works is that it forces you past the first plausible answer, which is almost always wrong. Most operational misdiagnosis happens because the founder stops at why number one and acts on it.
Put the two together and you have a method. A map of where to look. A technique for how to look once you are there.
The problems an operating system solves
Surfacing the real issue once is useful. Doing it consistently is harder. The business keeps changing. What was the right diagnosis at one million pounds of turnover may not be the right diagnosis at five, or fifteen, or even twenty-five. The structural causes shift as the business grows.
This is where an operating system comes in. A business operating system is the live structure that holds the business together: the dashboards that show how it is performing, the rhythm that reviews what is working, the documented workflows that show how work moves, the defined ownership that says who is accountable for what. It adapts to how the business runs day to day.
The reason this matters for diagnosis is that an operating system makes ongoing surfacing possible. When the structure is in place, deviations become visible. A drop in cash conversion shows up. A workflow that is stuck shows up. A KPI that has slipped shows up. You see the symptom early, in context, and you have the structure to ask why.
Without it, you only notice problems when they have grown big enough to hurt. By then, they are expensive to fix. We made the case for an operating system in growing businesses in this earlier post and the surfacing argument is one of the strongest reasons to install one.
Where to start if you do not know where to start
The hardest part is starting. When everything sounds like it needs fixing, the founder freezes or picks the loudest symptom. Both lead to the same place: spending on the wrong fix.
We have built a free tool to make the start easier. The Operational Health Check is a 2 to 3 minute self-assessment that asks 12 questions about how your business operates across the three areas: cash flow, operational control, and workflow efficiency. You get a personalised report that highlights where the strain sits and what to prioritise first.
It is not a full diagnosis. It is the first pass. It tells you which area to look at and in what order. The deeper work, the 5 Whys and the structural fix that follows, comes after. Most founders or management teams do not need a deep diagnosis to start. They just need a few hints to get going and need to know whether to look at cash flow before operational control, or whether the workflow problem is actually the cash flow problem in disguise. The Operational Health Check answers that.
If you already know what needs fixing, book a call and we can talk through what you are facing, agree a plan of attack and move straight to designing and building the solution.
The point of all of this is the same. Operational efficiency in a small to medium sized business is not won by working harder or buying more. Instead it is won by spending the next operational pound on the right thing. Surfacing the real issue is what makes that possible.