Table of Contents

5 Whys Root Cause Analysis Guide

Learn how to systematically investigate quality problems using the 5 Whys method. Identify root causes and assign corrective actions in 5 steps.

Start 5 Whys RCA

What Is the 5 Whys Method?

The 5 Whys is a root cause analysis technique where you repeatedly ask "Why?" to peel back the layers of a problem until you reach the fundamental cause. It was developed by Toyota as part of the Toyota Production System and is now a standard quality tool used across all manufacturing industries. The tool guides you through each "why" level and helps you document corrective and preventive actions.

When Should I Use This Tool?

  • When a defect, failure, or non-conformity occurs and you need to find out why
  • After a fishbone diagram brainstorm to drill deeper into the most likely causes
  • As part of an 8D, CAPA, or corrective action report that requires documented root cause analysis

Before You Start

Have the following ready:

  • A clear description of the problem, including when and where it happened
  • Facts and data from the event (not assumptions) -- talk to the people involved first

1 Define the Problem

Describe the problem clearly and factually. Include when it happened, where, and what the impact was.

Problem Description (required)
Write a clear, factual description. Example: "5 out of 50 parts from Order #4520 had OD measurements above the upper spec limit of 25.10 mm."
Date of Occurrence
When the problem was first discovered or occurred.
Location / Area
Where the problem occurred (machine, work center, production line, etc.).
Tip
Be specific and factual. "5 parts out of tolerance" is better than "bad parts." Include numbers when possible.
Click to view screenshot
Problem definition page with problem description, date, and location fields

2 Ask the 5 Whys

For each "Why," write the answer based on facts and evidence. The tool lets you add up to 5 levels (or more if needed). When you reach the fundamental cause, mark it as the root cause.

Check the box when you reach the root cause -- you do not have to use all 5 levels
Close-up showing the checkbox to mark a Why answer as the root cause
Tip
You do not always need exactly 5 levels. Sometimes the root cause appears at Why #3, other times you may need 6 or 7 levels. Stop when you reach a cause you can act on and that, if fixed, would prevent the problem from recurring.
Click to view screenshot
5 Whys chain showing multiple levels filled in with a root cause marked

3 Define Actions

Now that you know the root cause, define three types of actions:

Containment Action
What you did immediately to stop the problem from getting worse. Example: "Quarantined remaining parts from Order #4520 pending re-inspection."
Corrective Action
What you will do to fix the root cause so this specific problem does not happen again. Example: "Replace worn cutting insert and reset tool offset."
Preventive Action
What you will change in the system or process to prevent similar problems in the future. Example: "Add tool wear check to daily machine startup checklist."
Tip
Containment is about the immediate fix. Corrective addresses this specific root cause. Preventive addresses the system so similar problems are caught earlier. All three matter.
Click to view screenshot
Actions page showing containment, corrective, and preventive action sections

4 Set Priority and Assignment

Assign each action to a responsible person, set a due date, and choose a priority level. This ensures accountability and follow-through.

Tip
Assign actions to specific individuals, not departments. "John Smith" is better than "Quality Department." Set realistic due dates and follow up.
Click to view screenshot
Priority and timeline page with responsible person, due date, and priority level fields

5 Save or Download Your Report

Your complete RCA report includes the problem statement, the full Why chain, root cause, all actions with assignments, and priority levels. Save it to your dashboard, download as a PDF, or share with your team.

Tip
Attach the PDF to your formal corrective action report. It provides a complete, auditable trail from problem to root cause to actions taken.
Click to view screenshot
Final RCA report page showing the full analysis with save and download options

Tips & Best Practices

  1. Always base each "Why" on facts and evidence, not opinions or assumptions. Talk to the operators and review the data.
  2. If you have trouble going deeper than Why #2, try asking "What evidence do we have?" to uncover the next layer.
  3. A good root cause is something you can take action on. "Operator error" is usually not a root cause -- ask why the error was possible.
  4. Follow up on your corrective actions. Use the dashboard to revisit the RCA report and verify that actions were completed and effective.

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.