Root Cause Analysis for Business: The Real Problem No One Is Talking About
Root cause analysis for business is one of the most underused tools in strategic tool box — and one of the most valuable. It isn’t a new concept. But the structured, disciplined version, the kind that produces findings a leadership team will act on, is rarer than most organizations realize. Analysis of 51 projects taught me a little something about root cause analysis, and where the real problems live.
Most organizations are very good at treating problems. They’re far less good at solving them.
The distinction matters more than most leadership teams realize. Treating a problem means responding to what’s visible: the missed deadline, the budget overrun, the customer complaint, the team that isn’t delivering. Solving a problem means finding what’s really causing it. And those two things are rarely the same.
Uncovering the Problems
Several years ago, a client hired me to analyze their product development lifecycle and help identify why they were constantly missing delivery deadlines and falling short on revenue projections.
Over several months, I studied 51 of their projects in detail. I went looking for the patterns, the real ones, not the ones people assumed were there.
The results were surprising. Not because the problems were obscure or unusual, but because they were so consistent, and so preventable.
The failures weren’t caused by bad ideas. They weren’t caused by lack of funding or poor talent. They were caused by things that happened – or didn’t happen – before the work ever started.
The top three root causes, in order:
- Poor initial planning and insufficient scope definition – 15 out of 51 projects (29%) failed because of this alone. Not because the scope was ambitious. Because it was never actually defined.
- Dependencies on other teams that were never properly identified or managed. Work that required input, decisions, or resources from other parts of the organization, assumptions that were never confirmed, or conversations that were never had.
- Requirements that looked good on paper but weren’t clearly defined or executable, weren’t approved, documentation was unclear, or they were simply undeliverable as written.
Here’s what struck me most: in 90% of the failed projects, these issues were visible within the first or second sprint. The signals were there. The warning signs existed.
But no one had a structured way to identify them. And no one had a framework for acting on them before they became expensive.
The Problem With How Most Organizations Diagnose Problems
When something goes wrong in an organization, the instinct is to fix what’s visible. The project is late, so we add resources. The team is missing targets, so we change the team. The customer is unhappy, so we apologize and offer a discount.
These responses aren’t wrong, exactly. They’re just incomplete. Because they address the symptom without ever asking what caused the problem.
And when the root cause goes unaddressed, the problem comes back. Sometimes in the same form. Sometimes in a different one. But it comes back, because nothing that caused it has changed.
I’ve watched organizations apply band-aid after band-aid to the same wound for years. Not because they weren’t smart or capable, but because finding the real root cause takes something most organizations struggle to create: the space for honest conversation, the structured process to surface what’s true, and sometimes the courage to follow the diagnosis somewhere uncomfortable.
What Structured Root Cause Analysis Actually Looks Like
What I built after that 51-project study wasn’t a report. It was a framework, a structured diagnostic process that any leadership team can use to find what was driving underperformance, misalignment, or stalled growth.
We use scoring rubrics, risk assessments, and complexity matrices. Not gut feel, just quantified analysis that can be defended, shared, and acted on.
The process works across four structured dimensions:
- Problem definition and quantified impact assessment across revenue, cost, customer, and operational dimensions. Not “we’re missing targets” but “here is exactly what this is costing us, measured in terms leadership can act on.”
- Cause and effect mapping – a visual framework that connects root causes to business impacts across (eight recommended or customized) cause categories and (eight recommended or customized) effect categories. This is where symptoms get separated from sources.
- Five Whys structured analysis – a guided process for drilling beneath the surface. Not stopping at the first answer that feels right, but continuing until something true emerges.
- Prioritized action planning with impact ratings, effort estimates, and recommended owners. So the output isn’t just understanding but a clear path forward your team built and owns.
The Most Important Part of the Process
The framework matters. But the most important part of root cause analysis isn’t the tool. It’s the conversation.
Real root causes surface when the right people are in the room, asking honest questions, and genuinely willing to follow the answers wherever they lead. That’s not something that happens naturally in most organizations, often times because the truth is uncomfortable, and most organizations (and people) are very good at avoiding uncomfortable conversations.
That’s why we don’t deliver root cause analysis as a report. We facilitate it as a process with your leadership team, in the room, doing the work, surfacing the findings themselves. Because a diagnosis your team built is one your team believes. And a diagnosis your team believes is one your team will actually work to resolve.
When we leave, the findings belong to your organization. The tool stays with you. And your team has the capability to run future analyses independently without needing us in the room.
The Question Underneath All of It
Every root cause analysis, regardless of the industry, the size of the organization, or the nature of the problem, comes back to the same question:
Are you solving the right problem?
All the execution discipline in the world won’t save you if the answer is no. And in my experience, after more than 30 years in technology and business strategy, the organizations that ask this question honestly, early, and with the right structure around it are the ones that fix things.
The ones that skip it just get better at treating the same problems over and over again.
—
If your organization is treating the same problems repeatedly and not getting ahead of them, it might be time to find the source.
Root Cause Analysis is part of the Discover & Understand Phase of the Touchstone Discovery Method. Learn more using the link below:
Not sure about your next steps?
Start with our free Pre-Engagement Alignment Assessment — a quick diagnostic tool that helps you identify where your business needs to focus before any engagement begins.
Ready to talk? Book a 30-minute discovery call.