What is Root Cause Analysis (RCA) and the 5 Whys?
Root Cause Analysis (RCA) is a systematic process used to identify the underlying origin of a problem or event, rather than focusing solely on its immediate symptoms. The 5 Whys is a foundational technique within RCA where the question "Why?" is asked repeatedly (usually five times) to peel away layers of symptoms and reveal the systemic cause of a failure.
"By investigating root causes, you are not just treating the symptoms but treating the underlying disease." — Super Thinking (Weinberg & McCann)
Why is fixing symptoms different from fixing the root cause?
That's the whole reason root cause analysis exists. Fixing symptoms feels productive and fails repeatedly. Fixing the cause is slower to set up and stops the problem. Developed at Toyota, the 5 Whys is foundational to Lean problem-solving.
How do the 5 Whys work in practice?
Ask "why did this happen?" for each answer until you reach a system-level cause. Here is a practical example from software delivery:
| Level | Question | Answer |
|---|---|---|
| 1 | Why are users abandoning checkout? | Payment step is slow. |
| 2 | Why is it slow? | The validation service times out. |
| 3 | Why does it time out? | It calls three APIs sequentially. |
| 4 | Why sequentially? | Nobody designed for parallel calls. |
| 5 | Why? | Root Cause: No performance requirements defined for this flow. |
The root cause is missing non-functional requirements. Fixing "the slow API" treats the symptom. Introducing a process for defining NFRs prevents the class of problem from recurring.
What is the Fishbone (Ishikawa) diagram?
The Fishbone diagram organizes potential causes into categories so teams brainstorm systematically instead of fixating on the loudest explanation.
| Category | Description | Focus Area |
|---|---|---|
| People | Skills, training, or human error | Training gaps, fatigue, communication |
| Process | Workflows, steps, or policies | Bottlenecks, outdated SOPs |
| Technology | Tools, software, or hardware | System bugs, server capacity |
| Environment | External factors or surroundings | Noise, lighting, market shifts |
How does RCA apply to team performance?
"Just as with incidents, the first explanation for poor performance is rarely the root cause." — from RCA notes
The same principle applies to team and process failures. The stated reason for a missed deadline is rarely the actual cause. RCA applied to team retrospectives surfaces the systemic issues — not just the most recent frustration.
FAQ: Root Cause Analysis (CBAP Guide)
Does RCA always require exactly 5 "Whys"? No. Five is a rule of thumb. You may find the root cause in three whys or it may take seven. Stop when asking "why" no longer yields actionable insights into the system.
What is the difference between a Root Cause and a Contributing Factor? A root cause is the primary source of the problem. A contributing factor is a condition that influenced the problem but did not directly cause it. Removing a contributing factor might lessen the impact, but only removing the root cause prevents recurrence.
Can a problem have multiple root causes? Yes. In complex systems, multiple independent failures can converge to create a single problem. This is where tools like Fishbone diagrams are more effective than the linear 5 Whys.
Exam tip: CBAP tests the difference between a root cause (the origin) and a contributing factor (something that made the problem worse). They require different interventions. Identifying the right level of cause is the analytical skill being tested.