What is Root Cause Analysis?

What is Root Cause Analysis? (A Simple Definition)

Root Cause Analysis (RCA) is a systematic method of problem-solving used to identify the core, underlying reason why a problem or defect occurred. The purpose of RCA is not just to "find the fault," but to permanently eliminate it so that the problem never happens again. If you want a straight answer: it is the difference between putting a bucket under a leaking roof, and actually climbing up to fix the hole.

In the context of Lean Six Sigma, RCA takes place during the Analyse phase of the DMAIC framework. It forces teams to look past the obvious symptoms and rely on evidence and data to pinpoint the systemic failure that allowed the issue to exist in the first place.

Why Surface-Level Fixes Fail

Most businesses suffer from a culture of "firefighting." When a customer complains about a late delivery, the manager yells at the shipping team, they work overtime to clear the backlog, and the issue is considered "resolved." However, the systemic issue—perhaps a broken inventory tracking software—remains untouched. Next month, the exact same problem will happen again.

Surface-level fixes fail because they only treat the symptom. They rely on "human error" as an excuse. In Root Cause Analysis, there is a fundamental rule: Human error is a symptom, not a root cause. If an employee makes a mistake, the RCA approach asks: "Why did the system allow that mistake to occur?"

Two Essential RCA Methods

There are many tools available for Root Cause Analysis, but two stand out as the most widely used and effective across any industry: The 5 Whys and the Fishbone Diagram.

1. The 5 Whys

The 5 Whys is arguably the simplest yet most powerful RCA tool. Originally developed by Toyota, the method involves looking at the problem and asking "Why?" until you reach the systemic root cause. Typically, it takes about five iterations to drill past the symptoms.

• The Problem: The machine stopped working.
• Why? Because the motor burned out.
• Why? Because the oil was never changed.
• Why? Because there was no maintenance schedule in place.
• Why? Because the maintenance manager left and their duties were not reassigned.
• Root Cause: Lack of a standardised handover process for critical maintenance roles.

Notice how the first "why" points to a mechanical failure, but the final "why" reveals a management and process failure. That is the power of the 5 Whys.

2. The Fishbone Diagram (Ishikawa)

While the 5 Whys is great for linear problems, some issues have multiple contributing factors. The Fishbone diagram (also known as a Cause and Effect diagram) helps teams brainstorm and categorise every possible cause before narrowing them down.

The problem is written at the "head" of the fish. The "bones" represent categories of potential causes. In manufacturing, these are often the 6Ms: Methods, Machines, Materials, Manpower, Measurement, and Mother Nature (Environment). In an office setting, you might use the 4Ps: Policies, Procedures, People, and Plant (Technology).

By visually mapping out all the potential causes, the team can use data to systematically eliminate the unlikely causes until only the true root cause remains.

Example of a Problem Being Solved Properly

Let's look at a practical example from an e-commerce company experiencing a high rate of returned items because customers received the wrong product.

The "Firefighting" Approach: The warehouse manager blames the packing staff for not paying attention. He issues a warning, tells them to "be more careful," and hires an extra quality-check person. Costs go up, morale goes down, and errors only drop slightly.

The Root Cause Analysis Approach: The team uses a Fishbone diagram to brainstorm causes. They notice a cluster of issues around "Materials" and "Methods". They apply the 5 Whys to a specific error:

• Why was the wrong item shipped? The packer picked an item from bin A12 instead of A13.
• Why did they pick from the wrong bin? The barcode scanner approved the item from A12.
• Why did the scanner approve it? The barcodes on product A12 and A13 are identical.
• Why are the barcodes identical? The supplier updated the product packaging but the procurement team didn't log the new SKU in the inventory system.

The True Fix: The team implements an automated check in the procurement software that prevents a new shipment from being received into the warehouse without unique SKU verification. The errors drop to zero, no extra staff are needed, and the packers are no longer blamed for a system failure.

Summary

Root Cause Analysis is about finding the disease, not just treating the symptoms. By using structured tools like the 5 Whys and Fishbone diagrams, organisations can stop blaming individuals and start fixing broken systems. Whether you are dealing with manufacturing defects or administrative delays, identifying and eliminating the root cause is the only way to achieve sustainable, long-term improvement.