How to Do Root Cause Analysis (RCA)

Root Cause Analysis (RCA) is a structured method for identifying the underlying reasons behind recurring issues. It ensures organizations focus on eliminating the actual source of problems, not just treating their symptoms. Within Lean Six Sigma, RCA is an essential discipline embedded into the DMAIC (Define, Measure, Analyze, Improve, Control) framework, enabling teams to permanently fix the issues that impact quality, performance, and customer satisfaction.

By reading this guide, you’ll learn how RCA integrates with DMAIC, explore the six-step RCA process, and understand how to choose the right RCA tool for your specific challenge.

Recommended Further Reading:

• DMAIC Guide
• How to do a 5 Whys Analysis

What is Root Cause Analysis?

Root Cause Analysis is a structured investigation technique designed to uncover the true origin of a problem. Rather than treating surface-level symptoms, RCA seeks to identify what failed in the system or process, and why that failure occurred. The approach encourages critical thinking, team collaboration, and data-informed decision-making.

RCA’s power lies in its ability to break cycles of repeated failure. For instance, if an error keeps occurring in a production line or software deployment, RCA helps teams dissect the contributing factors and implement process or design changes to eliminate the issue. This prevents firefighting, reduces costs, improves quality, and supports compliance efforts.

Why Root Cause Beats Quick Fixes

Organizations often fall into the trap of temporary solutions—resetting machines, retraining staff, or issuing memos. These responses may address the immediate issue but fail to stop it from happening again. RCA offers a more strategic response by asking: What condition allowed the issue to occur? What control was missing? What change can we make to eliminate this vulnerability?

RCA brings these long-term benefits:

• Recurrence prevention – eliminate repeat issues.
• Process reliability – stabilize operations.
• Cost reduction – avoid waste from defects, rework, or downtime.
• Stronger compliance – satisfy regulatory expectations.
• Enhanced customer trust – deliver consistent quality.

Ultimately, RCA shifts an organization from being reactive to being proactive.

A Brief History of RCA

Root Cause Analysis has matured alongside quality management practices over the last 70 years. It was heavily influenced by the work of W. Edwards Deming and Joseph Juran, who emphasized learning from failure and continuous improvement. Deming’s Plan-Do-Check-Act (PDCA) cycle introduced the idea of analyzing causes before acting, while Juran focused on defect prevention.

In the 1960s, Kaoru Ishikawa developed the Fishbone Diagram (also called the Ishikawa Diagram or Cause-and-Effect Diagram), which provided a visual framework for exploring contributing factors. Around the same time, the Failure Mode and Effects Analysis (FMEA) technique emerged in aerospace and military applications to anticipate failure. points.

In the 1980s, Motorola and General Electric popularized Six Sigma, formalizing root cause analysis as part of the DMAIC structure. DMAIC embedded RCA into a disciplined, data-based methodology. Later, tools like Fault Tree Analysis (FTA) and Kepner-Tregoe (KT) Problem Analysis added further structure and logic to root cause discovery. Today, RCA is integrated into ISO 9001 audits, Lean manufacturing, regulatory compliance, and high-reliability industries.

Recommended Further Reading:

• Guide: Plan, Do, Check, Act (PDCA)
• Visionary: W. Edwards Deming
• Visionary: Joseph Juran
• Guide: Fishbone Diagram

RCA in the DMAIC Framework

DMAIC provides a logical sequence for solving problems in a disciplined way. RCA is a natural fit within this structure, particularly during the Analyze and Improve phases. However, RCA principles are relevant throughout all stages:

RCA enriches DMAIC by guiding teams to focus on causes rather than symptoms. When integrated correctly, it ensures that improvement efforts are both effective and sustainable.

The 6-Step Root Cause Analysis Process

Root cause analysis is best conducted as a structured sequence of steps. Each builds upon the last and reinforces the rigor of the process.

1: Define the Problem

A clear, concise, and measurable problem statement is essential. Instead of saying “machine breaks often,” specify: “Machine A has unplanned downtime for 20+ minutes, three times per week, due to conveyor faults during Night Shift.”

A strong problem definition includes:

• What is happening (observable defect or deviation)?
• Where is it happening (location, line, system)?
• When and how often does it occur (timing, frequency)?
• Why it matters (impact on cost, time, quality, or safety)?

Avoid assumptions about cause at this stage. Focus on symptoms and facts. This step also defines the project’s scope, so you don’t chase unrelated issues.

2: Collect Data

Data anchors the analysis. Gather relevant facts from logs, reports, interviews, system dashboards, and direct observation. Look for:

• Timing of incidents
• Patterns (shift, product, operator)
• Environmental factors
• Changes to processes or materials

Visual tools like control charts, heat maps, and timelines help spot trends. Use process mapping to understand how the system flows and where deviations may occur. If data doesn’t exist, create a plan to collect it in real time.

Avoid relying solely on memory or anecdotal reports. Objective data makes the next steps of RCA more reliable.

3: Identify Possible Causes

Now you move from symptoms to potential causes. Use brainstorming sessions with cross-functional teams to explore all plausible sources of the problem. Tools that help include:

• Fishbone Diagram: Categorize potential causes into groups such as People, Process, Equipment, Materials, Environment, and Measurement.
• 5 Whys: Pick a symptom and ask “Why?” repeatedly to peel back layers. Ideally, stop when the response points to a systemic or process failure.
• FMEA: Anticipate where failures are most likely and most damaging. Score severity, occurrence, and detection to prioritize further investigation.

Consider multiple branches of inquiry. There may be more than one contributing cause, especially in complex systems.

4: Determine the Root Cause(s)

Use logical and data-driven techniques to validate or eliminate your suspected causes. This is where analysis becomes precise. Techniques include:

• Is/Is Not Analysis: Define what the problem is and is not to isolate what changed.
• Hypothesis Testing: Test if changing a variable leads to or eliminates the issue.
• Pareto Analysis: Rank potential causes by frequency or impact.

Look for evidence that proves a causal link. If you fix the cause and the problem stops recurring, you’ve likely found a root cause. If not, revisit and expand your possible causes.

Root causes tend to be systemic: a flawed process, inadequate training, poor design, or a missing control.

5: Implement Corrective Actions

With validated causes in hand, design solutions to eliminate them. The best corrective actions:

• Address the cause directly
• Are feasible and cost-effective
• Prevent recurrence (not just detection)

Use:

• Impact vs. Effort Matrices to prioritize solutions
• Pilot Testing to validate solutions in a controlled way
• Poka-Yoke systems to eliminate error-prone steps

Involve stakeholders in developing solutions. Ensure procedures, roles, and accountability are clearly defined. Don’t forget to consider unintended side effects of changes.

6: Monitor and Control

The final step ensures that the issue is truly resolved—and stays that way. Control systems help verify that your fix is effective long-term. Actions include:

• Updating SOPs and training documents
• Using control charts to monitor key metrics
• Conducting audits or checks on new procedures
• Displaying performance visually at the Gemba (workplace)

Build in triggers to alert teams if performance drifts. If the problem reappears, the system should flag it early.

Sustainability is the hallmark of a successful RCA. If the solution doesn’t hold, revisit the previous steps.

RCA Tool Comparsion Guide

Different RCA tools suit different types of problems. Use this chart to select the most appropriate method for your situation:

Selecting the right tool depends on:

• The type and complexity of the problem
• The experience level of the team
• The amount of time and data available

Sometimes, you may use multiple tools in sequence—e.g., start with Fishbone to explore, then apply 5 Whys to drill down.

Conclusion

Root Cause Analysis is more than just a problem-solving technique—it is a mindset that elevates the quality and sustainability of any improvement initiative. When embedded into the DMAIC framework, RCA ensures that each phase of your project is backed by clarity, evidence, and strategic insight.

By defining problems precisely, gathering meaningful data, identifying and validating causes, and designing targeted solutions, teams can resolve issues in a way that truly prevents recurrence. And with the right tools—whether 5 Whys for speed or FMEA for risk mitigation—you can tailor your approach to fit the complexity of your challenge.

Remember, every recurring issue is an opportunity for learning and growth. When RCA is done well, it doesn’t just solve the problem—it improves the process, strengthens team collaboration, and builds a culture of continuous improvement. Whether you’re addressing a production defect, a safety incident, or a service breakdown, the principles outlined in this guide will help you uncover what’s really happening—and fix it for good.

References

• American Society for Quality (ASQ). (n.d.). Root cause analysis. Retrieved from https://asq.org/quality-resources/root-cause-analysis
• Deming, W. E. (1986). Out of the Crisis. Cambridge, MA: MIT Press.
• Ishikawa, K. (1985). What is Total Quality Control? The Japanese Way. Englewood Cliffs, NJ: Prentice-Hall.
• Juran, J. M. (1999). Juran’s Quality Handbook (5th ed.). New York, NY: McGraw-Hill.
• Kepner, C. H., & Tregoe, B. B. (1981). The New Rational Manager. Princeton, NJ: Kepner-Tregoe, Inc.
• Mitra, A. (2016). Fundamentals of Quality Control and Improvement (4th ed.). Hoboken, NJ: Wiley.
• U.S. Department of Health and Human Services. Agency for Healthcare Research and Quality. (2020). Root Cause Analysis Toolkit. Retrieved from https://psnet.ahrq.gov/primer/root-cause-analysis
• Let us know if you’d like this formatted into a PDF, embedded into a training portal, or bundled with your RCA templates and toolkits.