The pattern I keep seeing Someone tells me their team keeps missing deadlines. So they bought project management software. Three months later, deadlines are still slipping. Someone else says cash flow is tight. So they chase invoices harder. Six weeks later, still tight. Another person mentions staff turnover is killing them. So they raise salaries. A year later, people are still leaving. These are smart people. They identified a problem and took action. But they treated symptoms, not causes. And symptoms have a way of coming back. What a symptom actually is A symptom is the thing you notice. It is visible, measurable, and usually annoying enough to demand attention. Missed deadlines. Cash flow gaps. High turnover. Customer complaints. That feeling every Monday morning that something is fundamentally wrong but you cannot quite name it. Symptoms are real. They cost you money and sleep. But they are effects, not origins. The root cause is the thing generating those effects. It sits further back in the chain. It is often quieter, less obvious, and more uncomfortable to confront. Why we default to treating symptoms Three reasons, mostly. First, symptoms are concrete. You can point at them. You can measure them. You can tell your accountant or your partner exactly what is wrong. Root causes are murkier. They require digging. Second, symptom fixes feel productive. You can buy software today. You can send that email today. You can announce a salary increase today. Root cause work takes longer and the progress is harder to see. Third, root causes often implicate us. The missed deadlines might trace back to how you brief projects. The cash flow issue might connect to your pricing decisions. The turnover might reflect how you manage people. That is harder to sit with. So we stay at the symptom level. Not because we are lazy, but because it is easier and faster and feels like action. A real example I worked with someone running a consultancy in London. Revenue was strong but profit margins had dropped from 32% to 19% over eighteen months. The obvious symptom was rising costs. Their first instinct was to cut expenses. Renegotiate supplier contracts. Cancel some subscriptions. Standard stuff. We spent an afternoon mapping where the money actually went. The problem was not expenses in general. It was scope creep on client projects. Projects routinely ran 40% over the original estimate. That extra time was unbilled. Why the scope creep? Vague project briefs at the start. No sign-off process when clients requested changes. A team culture that said yes to everything because they wanted to keep clients happy. Cutting expenses would have saved maybe £800 a month. Fixing the scoping process recovered over £4,000 a month in billable work that was being given away free. Same business. Same financial pressure. Completely different intervention once we found the root. How to find the actual cause The simplest method is asking why five times. Not literally five, but enough times that you move past the surface. Why are deadlines slipping? Because the team starts projects late. Why do they start late? Because they are waiting on assets from clients. Why are clients slow? Because our briefing process does not specify what we need upfront. Why not? Because we have never standardised it. Now you have something to fix. Another approach is to look for patterns across time. If a problem keeps returning despite different solutions, you are probably treating symptoms. The root cause is still there, generating new versions of the same issue. You can also ask: if I fixed this, would anything else improve? Symptom fixes tend to be isolated. Root cause fixes tend to have knock-on benefits. That scoping process fix did not just improve margins. It reduced client frustration, cut revision rounds, and freed up team capacity. Where this connects to what is happening now There is a lot of noise at the moment about rising costs. Pharmacies warning about supply chain pressures. Retailers flagging uncertainty. Inflation figures shifting week to week. When external pressure increases, the temptation is to react fast. Cut here. Tighten there. Chase harder. Sometimes that is necessary. But I have watched businesses make panicked cuts that saved a few hundred pounds while ignoring structural issues that were costing thousands. The symptom got attention because it felt urgent. The root cause stayed hidden because no one had time to look. Pressure is exactly when you need to distinguish between the two. The uncomfortable truth Root cause work often means changing something about how you operate. Not just adding a tool or sending a memo. It might mean rewriting your pricing model. Restructuring how you onboard clients. Having a conversation with a team member you have been avoiding. Admitting that a process you designed is not working. That is why people avoid it. Symptom fixes let you stay comfortable. Root cause fixes ask you to change. But the maths is simple. You can spend two hours this week finding the real problem, or you can spend two hours every week for the next year managing the symptoms it keeps producing. What to do this week Pick one recurring problem in your business. Something that has shown up more than twice in the last six months. Write down what you have already tried to fix it. Then ask: did those fixes address the visible issue or the thing causing it? Run five whys on it. Actually write the answers down. Most people stop at two or three because the fourth gets uncomfortable. Keep going. If you want a structured way to do this, the 5 Whys tool at alira.london walks you through it. But a notebook works too. The method matters less than the honesty.