5 Whys Root Cause Analysis Template

What the 5 Whys technique is for

The 5 Whys is a root-cause identification technique. You take a problem, ask why it happened, and then ask why of each answer that comes back, usually around five times, until you reach a cause you can actually act on. It is simple enough to run in a short session, and it works best when the answers come from what people know about the work rather than from assumptions. The 5 Whys Root Cause Analysis Template supports that work. It sets out 28 questions across three sections, so each leg of the analysis follows the same sequence: state the problem, ask why in successive steps, and finish with a proposed corrective action. The sections are: - Leg 1: Specific Problem — How Was the Defect Produced? - Leg 2: Detection Failure — Why Was the Problem Not Detected? - Leg 3: Systemic Failure — Why Did the Possibility for Failure Exist? A plain five-why chain follows a single line of questioning. It tends to find one path to one cause. The three legs here split the investigation into three separate chains, which is useful when a defect was made, shipped, and only then noticed: the reasons it was made and the reasons it was not caught are usually not the same reasons.

Why investigating one chain of why questions is rarely enough

Most problems have more than one story behind them. Something caused the defect to be produced, something allowed it to pass through review, testing, or handover without being caught, and something about the system or process made both of those possible. If you only ask why the defect was made, the corrective action addresses the production step and leaves the detection gap and the systemic condition in place. The template builds this into the structure. Leg 1 closes with a proposed corrective action for the root cause of the specific problem. Leg 2 closes with a proposed corrective action for the root cause of the detection failure, prompted by the question of why the problem was not detected before it reached the customer or end user. Leg 3 closes with a proposed corrective action for the root cause of the systemic failure, prompted by why a possibility for failure existed within the system or process. Each leg produces its own finding and its own action, so nothing is folded into a single fix that only covers part of the problem.

How to run each leg

Work through the template in order. The first three questions capture the basic record: when it was conducted, who prepared it, and the location. Instructions open each section, followed by the substantive questions. **Leg 1: how was the defect produced?** Start by describing the specific problem or defect that occurred and how it was produced. Then work down the chain: why did that happen, why did that happen again, and so on across Why 2, Why 3, Why 4 and Why 5. The fifth why is where you identify the root cause. Follow it with a proposed corrective action that addresses the root cause of this specific problem. **Leg 2: why was the problem not detected?** Begin with why the problem was not detected before it reached the customer or end user. The same five-step chain follows, ending with the root cause and a proposed corrective action for the detection failure. **Leg 3: why did the possibility for failure exist?** Begin with why a possibility existed for failure within the system or process. Again the chain runs to the fifth why, where you identify the root cause, and closes with a proposed corrective action for the systemic failure. The template ends with a signature and a finished-at time, plus the inspection's real start and end dates, so the analysis carries a record of who completed it and when.

What a good 5 Whys analysis looks like

A useful analysis stays honest about the answers. Because each question builds on the previous response, a weak answer early on sends the rest of the chain in the wrong direction. Keep each answer short and specific, and base it on what you can point to: what was done, what was seen, what was recorded. If the group does not know, the better move is to find out before writing an answer than to write something plausible. A few habits keep the chain on track: - Ask why of an actual event or condition, not of a person's competence or attitude. - Treat the fifth why as a stopping point to review, not a fixed rule to obey. If you reach a cause you can act on before the fifth step, say so; if the fifth step is still superficial, keep going in the corrective action notes until it is not. - Keep the three legs separate. The root cause of the production failure and the root cause of the detection failure are different findings, and merging them loses one. - Write the corrective action next to the root cause it addresses, so the link is visible to anyone reviewing the record later. Used this way, the 5 Whys Root Cause Analysis Template gives you a repeatable structure for the investigation and a written record of how each conclusion was reached.

Frequently Asked Questions

The 5 Whys is a root-cause identification technique. You state a problem, then ask why it happened, and ask why again of each successive answer, typically about five times, until you reach a cause that is actionable. You can use it on your own or with a small group, and the checklist gives the sequence a place in a standard workflow.

A single chain of why questions usually traces one path to one cause. The three-legged investigation splits the analysis into three separate chains: how the defect was produced, why it was not detected before it reached the customer or end user, and why a possibility for failure existed within the system or process in the first place. Each leg ends with its own proposed corrective action, so you address the origin of the defect, the gap in detection, and the systemic condition separately rather than in one combined thread.

It is a general-purpose root-cause analysis technique rather than a standard tied to one industry. Because every leg ends in a proposed corrective action, it fits any team that needs to trace a problem back to its source and decide what to change, including sales, marketing, and cross-functional teams.

Complete one leg at a time. Leg 1 traces how the defect was produced, Leg 2 traces why it was not detected, and Leg 3 traces why the system allowed the possibility of failure. You can do a leg on your own or with the people closest to the work, writing a short answer at each step, and the last proposed corrective action of each leg becomes your output.

Each of the three legs has its own corrective action, so a complete analysis produces up to three: one for the root cause of the specific problem, one for the detection failure, and one for the systemic failure. Writing the action directly alongside the root cause keeps the output of the analysis tied to the cause you actually found.

The questions build on the previous answer on purpose, so the record only makes sense if each step is answered as you go. Stopping before the fifth why, or writing the root cause without the chain that led to it, leaves the corrective action without the evidence it depends on, which makes it hard for anyone else to review or act on later.

Written by

Arne Reis

Founder

Process optimizer with 25 years of expertise, focused on operational excellence in quality, maintenance, EHS, and commissioning. Emphasizes innovative solutions and top-quality standards.

View LinkedIn profile