What Is Root Cause Analysis (RCA)?

Definition

Root Cause Analysis (RCA) is a structured way of finding the underlying reason a problem happened, so the corrective action removes the cause instead of only treating the symptom.

Root Cause Analysis in Simple Terms

When a defect is found, the quick fix is to sort the parts and carry on. RCA asks why the defect was made and why it was not caught, then keeps asking until it reaches a cause that can be fixed and verified.

It sits at the heart of CAPA and the 8D method, where it is the fourth discipline.

Common RCA Methods

  • 5 Whys: ask why repeatedly until the real cause appears.
  • Fishbone diagram: group possible causes under headings such as man, machine, method, material, measurement and environment.
  • Is / Is Not analysis: compare where the problem occurs with where it could occur but does not.
  • Fault tree analysis: work down from the failure through logical causes.
  • Data checks: control charts, Pareto charts and comparisons of good and bad parts.

Example

Holes on a bracket are out of position. Why? The part moved in the fixture. Why? The clamp did not close fully. Why? Chips were trapped under the locator. Why? The coolant nozzle was moved during a tool change and no longer clears the fixture. The fix is a fixed nozzle position and a fixture cleaning check, verified by a capability study.

Common Mistakes

  • Stopping at "operator error" without asking why the process allowed the error.
  • Finding only the occurrence cause and not why the defect escaped detection.
  • Not testing the root cause by turning the problem on and off.
  • Closing the action without checking it worked.

OperaHive quality inspection software records nonconformances so investigations start from the inspection data.

FAQ

Frequently Asked Questions

Still unsure? Ask our team.

What is root cause analysis?

Root cause analysis (RCA) is a structured way to find the underlying reason a problem happened, so the fix stops it recurring rather than only treating the symptom.

What is the 5 Whys technique?

It is a simple RCA method where the team asks "why" repeatedly, often about five times, until it reaches a cause that can be fixed.

What is the difference between root cause and contributing cause?

The root cause is the main reason the problem occurred. Contributing causes made it more likely or worse but would not cause it on their own.

What are the most common root cause analysis tools?

Common tools are the 5 Whys, fishbone (Ishikawa) diagram, fault tree analysis, Pareto chart, is/is not analysis and process mapping.

What is a root cause analysis example?

A batch of holes is drilled oversize. Asking why shows the drill was worn, because tool life was not tracked, because the tool change interval was never set in the control plan. The fix is adding a counted tool change.

What are the steps of root cause analysis?

Define the problem, contain it, gather data, list possible causes, verify the root cause with evidence, put in corrective action, and check that the problem does not return.

How does root cause analysis fit into 8D?

In the 8D method, root cause analysis is discipline D4. The team must find both why the defect occurred and why it escaped detection.

What are common root cause analysis mistakes?

Typical mistakes are stopping at "operator error", jumping to a fix before verifying the cause, ignoring why the defect escaped, and not checking the fix worked.

Who should be involved in root cause analysis?

A small cross-functional team works best, including people who know the process, such as operators, engineers, quality and maintenance.

Is root cause analysis required by IATF 16949 and AS9100?

Yes. Both standards require corrective action that determines the causes of nonconformities and acts to prevent recurrence.

Put Root Cause Analysis (RCA) Into Practice

Book a demo and see how OperaHive handles this on your own parts, processes and documents.