Stop Playing Whack-a-Mole: Why Your Business Problems Keep Coming Back

Connect with us: SB Nation | Doodle or Die | Pexels | Medium | Cool Palettes

Three months ago, I watched a manager spend four hours fixing the same customer complaint system crash for the sixth time this year. When I asked why they weren't investigating what kept causing it, they looked at me like I'd suggested we sacrifice a goat to the IT gods. "We don't have time for analysis," they said, "we need solutions."

That's the problem right there. Everyone's so busy putting out fires they never ask why the bloody building keeps catching alight.

Root cause analysis isn't rocket science, but after seventeen years in workplace training, I've seen more businesses treat symptoms than a GP surgery in flu season. They'll spend thousands on Band-Aid solutions whilst the real problem laughs at them from the shadows.

What Actually Is Root Cause Analysis?

It's detective work for your business problems. Instead of asking "how do we fix this?" you ask "why did this happen in the first place?" Then you keep asking why until you get to something you can actually control.

The Japanese call it the "5 Whys" technique, though honestly, sometimes you need more like twelve whys to get anywhere useful. I've seen people stop at why number two and think they've cracked the case. That's like diagnosing chest pain as "because it hurts."

Most Australian businesses are terrible at this. We're action-oriented people - we see a problem, we want to fix it NOW. But that means we're constantly treating effects, not causes.

The Real Cost of Skipping Root Cause Analysis

Here's a statistic that'll make you wince: businesses that don't use proper root cause analysis spend 340% more on problem resolution over twelve months. I've seen companies burn through their maintenance budgets by October because they keep replacing parts instead of fixing the underlying issues.

Take customer complaints. Most businesses track complaint numbers, response times, all that surface-level stuff. But how many track the root causes? Effective communication training often reveals that 70% of customer issues stem from unclear internal processes, not product defects.

I worked with a Perth manufacturing company last year - they were getting constant quality complaints. Management wanted to hire more quality checkers. But when we did proper root cause analysis, we discovered their training manual hadn't been updated since 2019, and three critical steps were missing from the process documentation.

Cost of more quality checkers: $180,000 annually.
Cost of updating documentation: $3,000.

Guess which solution they'd been avoiding?

Why People Resist Root Cause Analysis

Time pressure. That's the big one. When your phone's ringing and customers are angry, sitting down to analyse why feels like luxury you can't afford.

But here's what I tell people: you can spend twenty minutes now finding the real cause, or spend two hours every month for the next year fixing the same problem. Your choice.

The other resistance comes from fear. Root cause analysis often points to human error, system failures, or management decisions. Nobody wants to be the messenger who tells the boss their favourite procedure is actually causing half the problems.

I remember working with a Sydney retail chain where staff turnover was through the roof. Management blamed "young people having no work ethic." When we dug deeper, we found their employee onboarding training was non-existent, their shift scheduling was chaotic, and their performance feedback system consisted of annual reviews where managers basically told people what they'd done wrong all year.

Young people weren't the problem. Management practices were.

The Tools That Actually Work

Forget fancy software for now. Start with a whiteboard and some honesty.

The 5 Whys Method: Problem: Customer complaints increased 40% last month. Why? Response times got slower. Why? Staff are taking longer per call. Why? They're having to search for information. Why? The new system doesn't have the old database integrated. Why? IT said it would take too long, so they went with a quick fix.

Boom. Real cause identified.

Fishbone Diagrams (Ishikawa): Draw a fish skeleton. The head is your problem. The bones are categories: People, Process, Equipment, Environment, Materials, Management. Under each bone, list potential causes.

This method's brilliant because it forces you to consider multiple angles. Most people fixate on one category - usually blaming people when it's actually a process issue.

The "So What?" Test: After identifying a cause, ask "So what would happen if we fixed this?" If the answer doesn't significantly impact the original problem, you haven't found the root cause yet.

Common Root Cause Analysis Mistakes

Stopping Too Early: Finding the first plausible explanation and running with it. Real root causes are usually boring, not dramatic.

Blame Focus: Turning it into a witch hunt instead of a learning exercise. The point isn't to find someone to punish, it's to prevent recurrence.

Single Cause Thinking: Most complex problems have multiple contributing factors. Don't assume there's one magic bullet.

Data Blind Spots: Making assumptions without checking the facts. I've seen teams spend hours analysing problems that turned out to be measurement errors.

Building a Root Cause Culture

This is where most businesses fail spectacularly. They'll do root cause analysis for major incidents but ignore the daily annoyances that slowly kill productivity and morale.

Make it routine. When someone reports a problem, the first question should be "have we seen this before?" If yes, why wasn't it properly fixed last time?

Train your people properly. Problem solving skills training isn't just for managers. Frontline staff often have the best insights into what's really going wrong.

Create psychological safety. If people get blamed for finding root causes, they'll stop looking. Celebrate good analysis, even when it reveals uncomfortable truths.

The Technology Question

Everyone asks about software. There are decent tools out there - Sologic, TapRooT, various quality management systems. But honestly, most small to medium businesses should master the basics first.

I've seen companies spend $50,000 on root cause analysis software they never properly implement because their people weren't trained on fundamental problem-solving thinking.

Master the whiteboard version first. Then upgrade if you need more sophisticated tracking and trending.

Real World Application

Let me give you a proper example. Adelaide logistics company, constant delivery delays. Management wanted to hire more drivers.

Root cause analysis revealed:

• Delivery routes weren't optimised (outdated planning software)
• Warehouse loading sequence caused bottlenecks (process design flaw)
• Customer delivery windows were unrealistic (sales promising impossible timelines)
• Morning briefings ran too long (unnecessary micromanagement)

Four different root causes, zero of which would've been solved by more drivers. Total fix cost: about $15,000 in software updates and process changes. Annual savings: roughly $200,000 in overtime, fuel, and customer retention.

When Not to Use Root Cause Analysis

Emergency situations. If the building's on fire, put it out first, analyse later.

One-off incidents that aren't likely to recur. Don't spend a week analysing why the office printer jammed once.

When you don't have the authority to fix the root cause anyway. No point identifying systemic management issues if you're not in a position to address them.

Getting Started Tomorrow

Pick one recurring problem that's been bugging you for months. Something that keeps coming back no matter how many times you "fix" it.

Gather the people closest to the problem - not just managers, but the people actually dealing with it daily.

Ask why. Keep asking why. Don't accept the first answer that sounds reasonable.

Document what you find. Take photos, keep notes, create a simple timeline.

Test your solution on a small scale before rolling it out everywhere.

The Bottom Line

Root cause analysis isn't complicated, but it requires discipline and honesty that many businesses struggle with. It means admitting that quick fixes aren't actually fixes, and that the real solutions might involve changing things nobody wants to change.

But here's the thing - problems don't go away because you ignore their causes. They just get more expensive and more disruptive over time.

Start small. Pick one annoying recurring issue and really dig into why it keeps happening. You might be surprised what you find lurking underneath the obvious explanations.

And remember - every problem solved at the root level is dozens of future problems prevented. That's got to be worth twenty minutes of proper thinking.

The Japanese have another saying: "Fix the process, not the blame." Maybe it's time more Australian businesses took that advice.