How to Perform Root Cause Analysis: Why Most Managers Are Doing It Wrong (And How I Learned the Hard Way)

Connect with us: SB Nation Community | Managing Madrid Forum | Artillery Forum | Professional Network

Three months ago, I watched a team of supposedly experienced managers spend six hours in a boardroom trying to figure out why their customer satisfaction scores had dropped by 23%.

They went around the table throwing out theories like confetti at a Melbourne Cup celebration. "It's the new system." "Staff need more training." "Customers are just harder to please these days." Sound familiar?

What they didn't do was actual root cause analysis. They did what 87% of Australian businesses do when problems arise - they guessed, pointed fingers, and implemented expensive solutions that barely scratched the surface.

I know this because I used to be exactly the same.

The Day I Finally Got It Right

Back in 2018, I was working with a manufacturing company in Brisbane whose production line kept shutting down. The operations manager was convinced it was equipment failure. Fair enough - the machinery was older than some of the workers operating it.

We replaced three major components over two months. Cost them nearly $80,000. Production kept stopping.

That's when I finally swallowed my pride and did what I should have done from day one: proper root cause analysis training. Not the superficial "five whys" nonsense that gets thrown around in corporate workshops, but genuine, systematic investigation.

Turns out the real issue was a shift scheduling problem that created communication gaps between teams. A $200 whiteboard and some basic process changes fixed what $80,000 in new equipment couldn't touch.

Why Traditional Problem-Solving Falls Short

Here's what I've learned after fifteen years of watching good people make terrible decisions: most managers treat symptoms because symptoms are obvious, immediate, and make you look like you're taking action.

Root causes? They're messy. They often point to uncomfortable truths about leadership, systems, or company culture that nobody wants to address.

Take customer complaints, for instance. The surface problem might be "slow response times." The root cause could be anything from inadequate staffing to poor training to a CRM system that's about as user-friendly as assembling IKEA furniture blindfolded.

But here's the thing - fixing response times feels achievable. Overhauling your entire customer service approach? That's proper work.

I've seen companies hire expensive consultants to "improve efficiency" when the real problem was a middle manager who'd rather micromanage than delegate. I've watched organisations invest in fancy project management software when their teams couldn't agree on basic priorities.

The Real Root Cause Analysis Process (Not the Textbook Version)

Forget the flowcharts and corporate jargon for a minute. Real root cause analysis starts with admitting you probably don't know what's actually wrong.

Step 1: Stop Assuming You Know the Problem

This is harder than it sounds, especially if you're the type of leader who prides themselves on having all the answers. I certainly was.

The best root cause investigators I know approach every situation like they're hearing about it for the first time. Even if it's the third time this month the same issue has come up.

Step 2: Talk to People Who Actually Do the Work

Not their supervisors. Not the department heads. The people who face the problem every single day.

You'd be amazed how often the front-line staff know exactly what's wrong but have never been asked. Or worse, they've mentioned it before and been told "that's just how we do things here."

Step 3: Follow the Data, Not the Drama

Every workplace has its personalities and politics. The loudest voice in the room isn't necessarily pointing you toward the real problem.

Look at what actually happened, when it happened, and who was involved. Proper problem-solving techniques require discipline, not just good intentions.

I once worked with a retail chain where the regional manager was convinced their Brisbane store's poor performance was due to "local market conditions." The data showed their top performer was literally across the street. Same market, different results.

Step 4: Test Your Theories Before Implementing Solutions

This is where most organisations fall apart. They identify what they think is the root cause, then immediately roll out company-wide changes.

Small pilot programs save massive headaches later. If your theory is correct, a limited test will prove it. If you're wrong (and you will be sometimes), you haven't disrupted your entire operation.

The Questions Nobody Wants to Ask

Real root cause analysis often leads to uncomfortable questions. Like:

• Is this problem happening because our processes are poorly designed?
• Are we hiring the wrong people, or failing to train the right ones properly?
• Does our organisational structure actually work against solving problems efficiently?
• Are we measuring the wrong things and incentivising the wrong behaviours?

These aren't fun conversations. They're necessary ones.

Why Quick Fixes Are Actually Expensive

I get it. Pressure from above, limited time, customers complaining - sometimes it feels like you need to do something, anything, to show progress.

But quick fixes create what I call "problem debt." Just like technical debt in software development, every shortcut you take today makes the real solution more expensive tomorrow.

The manufacturing company I mentioned earlier? They could have solved their production issues in week one with a $200 whiteboard and two hours of conversation. Instead, they spent $80,000 and three months because they were too busy fixing symptoms to investigate causes.

That's not efficiency. That's expensive theatre.

Building a Culture That Actually Solves Problems

The best organisations I work with have created environments where admitting "I don't know" is seen as the first step toward finding real answers, not a sign of weakness.

They reward people for identifying root causes, even when those causes point to uncomfortable truths about leadership or systems.

They invest time upfront in proper investigation because they understand it saves time later. And they're willing to implement solutions that might take longer but actually address the underlying issues.

Most importantly, they recognise that root cause analysis is a skill that needs to be developed, not something people automatically know how to do.

Getting Started (Without Overthinking It)

If you're dealing with a recurring problem right now, try this: assume everything you think you know about it is wrong.

Start fresh. Talk to different people. Look at the data from a different angle. Ask "what if" questions that challenge your assumptions.

And remember - the goal isn't to find someone to blame. It's to find something to fix.

Root cause analysis isn't about being smarter than everyone else in the room. It's about being systematic enough to find answers that actually work.

Because at the end of the day, your customers don't care how quickly you responded to their complaint. They care whether you fixed the thing that caused them to complain in the first place.

---

Looking to develop systematic problem-solving skills in your organisation? Connect with us through our communication training programs to learn more about building analytical thinking capabilities in your teams.