A machine breaks down on the production floor. The team replaces the part, restarts the line, and moves on. Two weeks later, the same failure happens again. Sound familiar? This cycle of fixing symptoms instead of solving the actual problem costs organizations thousands, sometimes millions, in lost productivity. What is root cause analysis? It’s the disciplined process of tracing a problem back to its origin so you can eliminate it permanently, not just patch it temporarily.
Root cause analysis (RCA) sits at the core of every effective Lean Six Sigma engagement. At Lean Six Sigma Experts, we’ve used RCA since 2011 to help manufacturers, corporate operations teams, and service organizations stop recurring failures and redirect wasted resources toward profitable growth. Our engineering-based approach means we rely on scientific data and proven methodologies, not guesswork, to pinpoint why problems exist and what to do about them.
This article breaks down the key steps of root cause analysis, walks through the most widely used tools, shares real-world examples, and shows you how to measure the ROI of doing it right. Whether you’re an operations manager dealing with chronic defects or a professional pursuing your Green or Black Belt certification, you’ll leave with a clear, actionable understanding of RCA and how to apply it.
What root cause analysis is and is not
Root cause analysis is a structured problem-solving methodology that identifies the deepest underlying cause of a problem, not just the visible symptoms. When you ask "what is root cause analysis," the honest answer is that it’s both a mindset and a deliberate process. You’re not satisfied with fixing what you can see; you’re committed to understanding why the failure occurred so it never comes back. RCA gives you a systematic framework to move from raw observation to hard evidence to a conclusion you can act on with confidence.
What RCA actually is
RCA is a disciplined investigation. You gather factual data, map out the sequence of events, and test hypotheses until you can trace the problem to its origin. Think of it as working backwards: a defect appears on the line, and you follow the chain of cause and effect until you reach the true source of the failure. The process is not opinion-based, and it is not a blame session. It focuses entirely on the system, process, or condition that allowed the problem to exist in the first place. That distinction matters, because it shifts your team’s energy away from pointing fingers and toward making permanent changes.
RCA answers one question above all others: what would have to change so this problem is physically impossible to repeat?
What RCA is not
Many organizations confuse corrective action with root cause analysis, and that confusion costs them time and money. Replacing a broken component, retraining an operator, or adding an inspection step are all responses to a problem, but none of them qualify as RCA unless they address the root cause directly. Applying a fix without identifying the root cause is like treating a fever with cold water. You may feel temporary relief, but the underlying condition remains fully active.
RCA is also not a one-time audit or a report you file and forget. It’s an ongoing discipline embedded in your improvement culture. Equally important, RCA is not reserved for catastrophic failures only. You get the most value when you apply it consistently to small, recurring problems before they escalate into major production disruptions or safety incidents. Organizations that treat RCA as a routine practice stop chasing fires and start preventing them, which is exactly where the real operational gains are made.
Why root cause analysis matters for Lean Six Sigma
Lean Six Sigma is built on two complementary goals: eliminate waste and reduce variation. Neither goal is achievable without understanding why defects, delays, and failures keep happening. Root cause analysis is the diagnostic engine that powers the DMAIC cycle (Define, Measure, Analyze, Improve, Control), particularly in the Analyze phase where you determine what is actually driving the problem. Without RCA, your improvement projects are based on assumptions, and assumptions lead to solutions that look good on paper but fail in practice.
RCA as the bridge between data and action
The question "what is root cause analysis" takes on a specific meaning inside a Lean Six Sigma framework. You’re not just looking for any cause; you’re looking for a statistically validated root cause that explains the gap between your current process performance and your target. The Analyze phase of DMAIC demands that you bring evidence, not intuition, to every conclusion you reach.
Without a confirmed root cause, any improvement you implement is a guess dressed up as a solution.
Why skipping RCA undermines your results
When organizations rush through RCA, they spend capital and labor on fixes that don’t hold. The Control phase collapses, performance drifts back to baseline, and the project earns a reputation for failure. You lose credibility with leadership, and your team loses confidence in the improvement process itself.
Investing time in rigorous RCA upfront is what separates a project that produces lasting, measurable gains from one that delivers temporary relief and a binder full of slides nobody reads again.
How to run an RCA step by step
Understanding what is root cause analysis in theory is useful, but executing it correctly is what actually drives results. Most RCA failures happen because teams skip steps or rush toward solutions before they’ve confirmed what they’re actually solving. Follow this sequence to run a rigorous investigation every time.
Define the problem and collect hard data
Your first task is to write a precise problem statement. Vague problem statements produce vague investigations. Define what is happening, where it is happening, when it started, and how frequently the failure occurs. Specificity is not optional; it determines how efficiently your team works through the rest of the process.
Once you have a sharp problem statement, collect factual data before you form any hypothesis. Pull process records, failure logs, inspection reports, and direct observations from the floor or the system. Going into your analysis with assumptions already in place will bias your conclusions and send your team in the wrong direction.
The more specific your problem statement, the shorter your path to the root cause.
Identify possible causes, test them, and verify
With solid data in hand, your team maps out potential causes using a structured tool like a fishbone diagram or the 5 Whys method. List every plausible cause across categories such as equipment, methods, materials, and personnel, then rank each candidate based on the evidence you collected.
From that ranked list, test your top candidates against the data. A cause that cannot be supported by evidence gets removed. Once you identify the leading candidate, verify it through a controlled test or statistical validation before committing resources to a corrective action. Verification is the step most teams skip, and it is the step that determines whether your fix holds.
RCA tools and when to use each
No single tool works for every problem. Choosing the right RCA tool depends on the complexity of the failure, the number of potential causes you suspect, and how much data you already have on hand. The table below maps the most common tools to their ideal use cases.
| Tool | Best for | When to avoid |
|---|---|---|
| 5 Whys | Simple, linear failures | Multi-cause failures |
| Fishbone diagram | Broad cause mapping | When data is very limited |
| Fault tree analysis | Complex, high-risk failures | Routine process defects |
| Pareto chart | Prioritizing multiple causes | Single-cause problems |
5 Whys
The 5 Whys method is the most accessible starting point for straightforward, linear failures. You ask "why" repeatedly until you reach a cause that, if removed, would prevent the problem from recurring. Most teams reach the root cause in three to seven iterations, not always exactly five.
Apply the 5 Whys when the failure chain is relatively direct and your team can trace one cause to the next without branching. If your investigation keeps splitting into multiple parallel causes at the same level, switch to a fishbone diagram instead.
Fishbone Diagram
Understanding what is root cause analysis on more complex problems often starts with the fishbone diagram, also called the Ishikawa diagram. This tool organizes potential causes across defined categories such as equipment, methods, materials, and people, giving your team a visual structure to work through before testing any hypothesis.
Use the fishbone diagram when you suspect several contributing factors and need to ensure nothing gets overlooked during your brainstorm session.
The fishbone diagram organizes your team’s thinking; it does not replace the data that confirms or eliminates each cause.
Examples and ROI you can expect
Knowing what is root cause analysis matters less than seeing it produce results. Real examples ground the methodology in outcomes your leadership team will recognize and your finance team will care about.
A manufacturing defect turned into measurable savings
A mid-size metal fabrication company was scrapping roughly 4% of output every shift due to dimensional failures. The team assumed operator error and ran retraining. The problem continued. Once they applied RCA using the fishbone diagram and statistical process control data, they traced the variation to thermal expansion in a worn fixture that was never part of the original hypothesis. Replacing the fixture reduced scrap to under 0.5% within 30 days. The annual savings exceeded $340,000, and the fix cost less than $8,000 to implement.
The gap between what you assume is causing the problem and what the data confirms is often where the most money is hiding.
Measuring the return on your RCA investment
Calculating ROI from RCA is straightforward when you focus on the right numbers. Track scrap costs, rework hours, downtime frequency, and warranty claims before and after your corrective action. Compare the cost of your investigation and fix against the annualized savings in each category.
Most organizations that run rigorous RCA on their top five recurring failure modes see cost reductions between 15% and 40% in the targeted process within the first year. The return compounds over time because the root cause stays eliminated, which means you stop spending the same money on the same problem year after year.
What to do after you find the root cause
Finding the root cause is a milestone, not a finish line. Once you confirm the true source of your problem, design and implement a corrective action that directly targets that cause, then build controls into the process to prevent regression. Document everything: the investigation path, the confirmed cause, the solution you chose, and the baseline metrics you’ll use to verify success. Without documentation, you lose institutional knowledge the moment a key team member changes roles.
After you implement the fix, track your target metrics for at least 30 to 90 days before closing the project. If performance holds, update your standard operating procedures to reflect the change. Share the results with your team and leadership so the lesson transfers across similar processes in your organization.
Understanding what is root cause analysis demands more than reading about it. If you’re ready to apply rigorous RCA methodology to your most persistent operational problems, connect with our Lean Six Sigma consulting team and put the process to work.