Most business problems get fixed twice. Once quickly — and once properly.

The first fix addresses what’s visible: a dip in sales, a spike in staff absence, a missed production deadline. It might buy some breathing space. But if the underlying cause hasn’t been identified and addressed, the problem returns. Sometimes in a different form, which makes it harder to spot the second time round.

Root Cause Analysis (RCA) is a discipline. It ensures you’re solving the right problem, not just the most obvious one.

Symptoms vs. Root Causes: A Useful Distinction

A useful way to think about this: imagine a persistent ringing in your ears. You could manage it with earplugs. That’s not irrational — it may well be the right short-term move. But if there’s an underlying infection, the earplugs aren’t solving anything. They’re just making the situation more bearable while it worsens.

Business leaders face this dynamic regularly. Declining sales numbers, poor customer retention, high staff turnover — these are symptoms. They’re telling you something is wrong. They’re not telling you what.

Flow Charts as a Thinking Tool

One of the more practical aids in RCA is the flow chart. It is not a bureaucratic exercise. Instead, it makes complex cause-and-effect relationships visible, debatable, and testable.

Take a manufacturing business consistently missing production deadlines. A basic RCA might start with a single question: Why are we missing deadlines?

That question opens into branches:

• Is it equipment failure? → If yes, examine maintenance logs and replacement cycles.
• Is it staffing? → If yes, is the issue headcount, capability, or something else?

At each node, the team is forced to choose a direction based on data — not instinct. That discipline is where the value lies.

The more honest insight, though, is that most business problems don’t have a single root cause. In reality, the flow chart often looks less like a clean decision tree and more like a web. Production delays might stem from equipment failure and staffing shortfalls and a supplier dependency that nobody had formally mapped. The chart’s job is to make that complexity explicit, so it can be managed — rather than leaving it implicit, where it gets ignored.

How to Run a Useful RCA

The methodology doesn’t need to be elaborate. What it does need is rigour and honesty.

Start by defining the problem clearly — specifically, not vaguely. “Sales are down” is a starting point, not a problem statement. “New customer acquisition in the South East declined 30% over two quarters. However, retention has held steady.” is something you can work with.

Bring in cross-functional perspectives. The person closest to the problem often has the most detailed view of symptoms. This person may have the least useful view of causes. Someone from a different part of the business will ask different questions — and often better ones.

Build the flow chart collaboratively. The act of mapping it out tends to surface assumptions people have been carrying individually but never stated out loud. That’s where the real value often emerges.

Validate before you act. A plausible hypothesis isn’t a confirmed root cause. Test it against data. If the evidence doesn’t hold, revise the map.

Then implement with clarity — defined actions, owners, and timelines. And build in a review point. RCA isn’t a one-off exercise; it’s a feedback loop.

The Harder Truth

Most leadership teams know, at some level, when they’re treating symptoms rather than causes. The real obstacle is rarely analytical — it’s organisational. Fixing root causes often requires addressing uncomfortable issues. These may include a structural weakness, a leadership misalignment, or a strategic assumption that turned out to be wrong.

The flow chart doesn’t make that easier. But it does make it harder to avoid.