1. Method Name

Root Cause Analysis (RCA) / Root Cause Analysis

2. Alternative Names

Root Cause Analysis

3. Brief Description

RCA is an umbrella term for a structured approach and a set of techniques used to identify the true root causes of a problem or incident. Instead of addressing superficial symptoms, RCA focuses on identifying and eliminating the root cause, which, if eliminated, would prevent the problem from recurring.

4. Purpose / When to Use

It is used to address chronic, recurring problems, to investigate serious incidents (related to safety or quality), or to analyze system failures. The goal is to move from a reactive “firefighting” approach to a proactive and systematic problem-solving approach.

5. Procedure / How to Apply It

General RCA Process:
1. Define the problem: Describe clearly and factually what happened. Who, what, when, where, and what was the impact?
2. Collect data: Gather all relevant information, evidence, and observations from the scene (Gemba).
3. Identify possible causes (Brainstorming): Use techniques to generate all possible causes that could have contributed to the problem. Key tools in this phase
: - Ishikawa diagram (Fishbone / C&E): Categorizes causes into groups (e.g., People, Machine, Method, Material, Measurement, Environment).
- 5 Whys: A simple method for quickly getting to the root of the problem.
4. Identify the root cause: From the list of possible causes, systematically identify the one that lies at the heart of the problem. Verify hypotheses with data. More advanced tools such as Fault Tree Analysis (FTA) or Pareto analysis can also be used in this phase.
5. Implement corrective and preventive actions: Design and implement solutions that directly address the root cause to prevent it from recurring.

6. A Real-World Example

At the hospital, there were repeated instances of patients receiving the wrong medication (problem definition). The team created an Ishikawa diagram (causes: similar medication packaging, the doctor’s illegible handwriting, nurse fatigue, interruptions during work). Using the 5 Whys for each branch, they determined that the root cause lay in the process: “Why did the nurse administer the wrong medication?” -> “Because she was interrupted.” -> “Why was she interrupted?” -> “Because visitors are allowed to move freely on the ward during medication administration.” -> “Why is this allowed?” -> “Because we don’t have defined ‘quiet zones/times’ for preparing medications.” Root cause: A lack of a process to protect the nurse from interruptions. Solution: Introduce red "Do Not Disturb—Preparing Medications" vests and set aside a time slot free of visitors.

7. Benefits

- Permanent solution: Eliminates the problem permanently, not just temporarily
.- Prevents recurrence: Prevents the same or similar problems from occurring in the future.
- Improves understanding of processes: Through analysis, the team learns a great deal about how the system actually works
.- Saves resources: In the long run, it is cheaper to solve a problem once and for all than to repeatedly “put out fires.”

8. Risks / Limits

- Premature termination of the analysis: The team settles for the first cause (symptom) it finds and does not continue to investigate in depth.
- Blame Game: RCA can devolve into a search for “who” made a mistake, rather than “why” the system failed. A “blameless culture” is essential.
- Lack of data: Without accurate data and facts, RCA is merely an exercise in guesswork.
- Complexity: For highly complex problems with multiple intertwined causes, it can be challenging to identify the “single” root cause.

9. Practical Tips

- RCA is a team effort: Involve people from different fields who have different perspectives on the problem
.- Distinguish between causation and correlation: Just because two things happen at the same time doesn’t mean one causes the other.
- Distinguish between corrective and preventive actions: A corrective action addresses the current problem (repairs a broken machine). A preventive action addresses the root cause (implements a maintenance plan so the machine doesn’t break again).
- Verify the root cause: Before investing in an expensive solution, make sure you have identified the correct root cause.