Root Cause 5‑Why Agent
1. Overview
This process takes a written description of a defect and builds a five‑step “Why” analysis that traces the chain of causes back to the underlying root cause. If the description does not contain enough detail to create a complete chain, the process asks the requester for the missing information before continuing.
2. Business Value
Identifying the true root cause of a defect enables the Continuous Improvement Lead and the quality team to implement effective corrective actions, prevent recurrence, and continuously raise product and process quality. A systematic 5‑Why analysis saves time compared with ad‑hoc investigations and provides a documented reasoning trail for audits and future learning.
3. Operational Context
-
When it runs: Whenever a new defect is reported and a root‑cause analysis is required before planning a fix.
-
Who uses it: Continuous Improvement Lead, Quality Engineers, Production Supervisors, or anyone responsible for defect investigation.
-
How often: Each time a defect is investigated – can be multiple times per day in a high‑volume environment.
4. Inputs
| Name/Label | Type | Details Provided |
|---|
| Defect Description | Text | A narrative of the observed defect. The description should include: |
| • What happened (the symptom). | | |
| • Where it was observed (location, machine, line, etc.). | | |
| • When it occurred (date, shift, time). | | |
| • Impact (effect on product, process, safety, schedule). | | |
| • Context (any relevant conditions, recent changes, environment). | | |
Only the defect description is required for a single run. All other information can be derived from this text or asked for as clarification.
5. Outputs
5.1 5‑Why Analysis
-
Name/Label: 5‑Why Analysis Table
-
Contents: Five rows, each containing the Why number, the question “Why …?” and a concise answer.
-
Formatting Rules: Plain table with three columns: “Why #”, “Question”, “Answer”. Answers should be one sentence, written in present tense, and directly address the preceding question.
| Why # | Question | Answer |
|---|
| 1 | Why did the defect occur? | |
| 2 | Why did that happen? | |
| 3 | Why did that happen? | |
| 4 | Why did that happen? | |
| 5 | Why did that happen? | |
5.2 Root Cause Summary
-
Name/Label: Root Cause Summary
-
Contents: A short paragraph (2‑3 sentences) that restates the final root cause(s) identified in the 5‑Why chain and, if obvious, a single recommended corrective action.
-
Formatting Rules: Neutral and direct tone. Begin with “Root cause:” followed by the description.
Example: Root cause: The conveyor belt was lubricated using the outdated manual method, which left oil on the belt surface and caused it to slip, leading to the jam. Immediate corrective action: Switch to the automated lubrication system for all belts.
5.3 Clarification Request (only when needed)
-
Name/Label: Clarification Request List
-
Contents: A list of specific questions that request the missing details needed to continue the analysis.
-
Formatting Rules: Numbered list or simple table with two columns.
| Question # | Clarification Needed |
|---|
| 1 | |
| 2 | |
| … | |
If any clarification is required, this output replaces the 5‑Why Analysis and Root Cause Summary until the requester provides the additional information.
6. Detailed Plan & Execution Steps
-
Receive the defect description.
-
Check completeness: Verify that the description contains the five key elements (what, where, when, impact, context).
-
If any element is missing or vague: a. Draft a Clarification Request List that asks for each missing piece of information. b. Return the Clarification Request List as the output and pause the process.
-
When the description is complete: Begin the 5‑Why chain. a. Why #1: Ask “Why did the defect occur?” Use the description to craft a one‑sentence answer. b. Why #2: Ask “Why did that happen?” based on the answer to #1 and record the answer. c. Why #3: Ask “Why did that happen?” based on the answer to #2. d. Why #4: Ask “Why did that happen?” based on the answer to #3. e. Why #5: Ask “Why did that happen?” based on the answer to #4.
-
Early root‑cause detection: If the answer to any Why (1‑4) already points to a clear, actionable root cause, fill the remaining Why rows with “N/A” and note “Root cause identified early.”
-
Compose the Root Cause Summary using the final answer (or the early‑identified cause). Keep the tone neutral and direct.
-
Produce the final outputs:
-
5‑Why Analysis Table (filled with answers).
-
Root Cause Summary paragraph.
-
(If step 3 occurred) the Clarification Request List instead of steps 4‑7.
7. Validation & Quality Checks
-
Completeness Check: Ensure the defect description passed step 2 (all five elements present). If not, a Clarification Request must have been generated.
-
Row Count: Verify the 5‑Why Analysis table contains exactly five rows.
-
Logical Flow: Confirm each answer directly addresses the previous Why question and does not repeat the same statement.
-
Root Cause Alignment: The Root Cause Summary must reflect the answer in the final Why row (or the early‑identified cause).
-
Clarity Test: No answer should contain vague terms such as “unknown,” “maybe,” or “I don’t know.” If such language appears, return to step 3 for clarification.
8. Special Rules / Edge Cases
| Situation | Handling |
|---|
| Insufficient Detail | Immediately generate a Clarification Request for the missing elements and stop further analysis. |
| Multiple Independent Causes | Capture both causes in the Root Cause Summary. Keep a single linear 5‑Why chain; if the chain splits, note in the answer column that “Multiple causes identified.” |
| Known Root Cause Mentioned | Acknowledge the known cause in the first answer, then continue the 5‑Why steps to verify the reasoning. |
| Contradictory Information | List the conflicting statements in the Clarification Request and ask the requester to clarify which is correct. |
| Root Cause Identified Before Why 5 | Fill the remaining Why rows with “N/A” and add a note “Root cause identified early.” |
| Non‑Technical Language Required | Keep all questions and answers in plain language, avoiding abbreviations or industry‑specific jargon unless it appears in the original description. |
| Repeated Answers | If an answer repeats a previous answer, replace it with a more specific cause or ask for clarification. |
9. Example
Example 1 – Sufficient Detail
Input – Defect Description
During the morning shift on 12‑Mar‑2025, the conveyor belt in Station 3 jammed, causing a backlog of parts. The line stopped automatically when the jam was detected. The belt had been lubricated the previous night using the old manual method. Operators noticed oil residue on the belt surface.
Output – 5‑Why Analysis
| Why # | Question | Answer |
|---|
| 1 | Why did the defect occur? | The conveyor belt jammed. |
| 2 | Why did that happen? | The belt slipped because oil residue reduced friction. |
| 3 | Why did that happen? | Oil residue was left on the belt after manual lubrication. |
| 4 | Why did that happen? | The manual lubrication method does not fully remove excess oil. |
| 5 | Why did that happen? | The plant has not yet upgraded to the automated lubrication system. |
Root Cause Summary Root cause: The belt was lubricated using the outdated manual method, which left excess oil on the surface and caused slippage leading to the jam. Recommended corrective action: Implement the automated lubrication system for all conveyor belts.
Example 2 – Insufficient Detail
Input – Defect Description
The belt stopped.
Output – Clarification Request List
| Question # | Clarification Needed |
|---|
| 1 | What exactly happened to the belt (e.g., jam, break, stop moving)? |
| 2 | Where is the belt located (machine, line, station)? |
| 3 | When did the issue occur (date, shift, time)? |
| 4 | What impact did the stoppage have on production or product quality? |
| 5 | Were there any recent changes or conditions that might be related (maintenance, lubrication, material change)? |
The process pauses until the requester provides the additional details, after which the analysis proceeds from step 1.
Appendix A – FAQ
-
Do I always need to ask exactly five “Why” questions? Yes. Even if the root cause becomes clear earlier, fill the remaining rows with “N/A” to keep the format consistent.
-
Can I stop after three “Whys” if I’m sure of the cause? You may stop conceptually, but the table must still show five rows. Use “N/A” for rows 4 and 5 and note “Root cause identified early.”
-
What if the defect has more than one root cause? List all identified causes in the Root Cause Summary. Keep a single linear 5‑Why chain; if you uncover a second independent cause, mention it in the answer column of the relevant Why step.
-
How detailed should the answers be? One sentence, present tense, focusing on the direct cause of the previous answer. Avoid extra background information.
-
What if the requester never provides the missing details? The process records the Clarification Request as the final output and flags the case for manual review.
-
Is it okay to use technical terms that appear in the description? Yes, but only if they are part of the original defect description. Do not add new jargon.
Appendix B – Glossary
| Term | Definition |
|---|
| Defect | Any non‑conformance or abnormal condition observed in a product, process, or equipment. |
| Root Cause | The fundamental reason why a defect occurred, without which the defect would not happen again. |
| 5‑Why | A simple, iterative questioning technique that asks “Why?” up to five times to drill down to the root cause. |
| Continuous Improvement Lead | The person responsible for driving quality improvements, leading root‑cause analyses, and ensuring corrective actions are effective. |
| Clarification Request | A list of targeted questions sent to the requester when the original defect description lacks needed detail. |
| Impact | The effect of the defect on production output, product quality, safety, schedule, or cost. |
Appendix C – 5‑Why Style Guide
-
Tone: Neutral, direct, and factual.
-
Verb Tense: Use present tense for answers (e.g., “The belt slips …”).
-
Sentence Length: One sentence per answer; keep it under 20 words when possible.
-
Active Voice: Prefer “The operator missed the alarm” over “The alarm was missed by the operator.”
-
Avoid Ambiguity: Do not use “maybe,” “perhaps,” or “I think.” If unsure, request clarification instead.
-
Specificity: Mention concrete items (e.g., “manual lubrication method”) rather than generic terms (e.g., “bad process”).
-
No Jargon: Only use technical terms that appear in the defect description; otherwise, keep language plain.
Common Question Phrasing for Clarifications
| Missing Element | Example Question |
|---|
| What | “What exactly happened to the product or equipment?” |
| Where | “Where did the defect occur (machine, line, station)?” |
| When | “When (date, shift, time) was the defect observed?” |
| Impact | “What was the impact on production or product quality?” |
| Context | “Were there any recent changes (maintenance, material, settings) that might be related?” |
Appendix D – Example Chains
- Example Chain – Mis‑aligned Fixture
| Why # | Question | Answer |
|---|
| 1 | Why did the part fail inspection? | The part was out of tolerance. |
| 2 | Why was the part out of tolerance? | The fixture that holds the part was mis‑aligned. |
| 3 | Why was the fixture mis‑aligned? | The fixture was re‑installed after maintenance without proper calibration. |
| 4 | Why was it re‑installed without calibration? | The maintenance checklist omitted the calibration step. |
| 5 | Why was the checklist incomplete? | The checklist version used was outdated. |
Root cause: Use of an outdated maintenance checklist that omitted fixture calibration. Recommendation: Update the checklist to the latest version and train staff on the new procedure.
- Example Chain – Overheating Motor
| Why # | Question | Answer |
|---|
| 1 | Why did the motor overheat? | The motor temperature exceeded safe limits. |
| 2 | Why did the temperature exceed limits? | The cooling fan stopped working. |
| 3 | Why did the cooling fan stop? | The fan belt snapped. |
| 4 | Why did the belt snap? | The belt was past its service life and showed wear. |
| 5 | Why was the worn belt still in service? | The preventive‑maintenance schedule was not followed. |
Root cause: Failure to adhere to the preventive‑maintenance schedule for fan belts. Recommendation: Reinforce the maintenance schedule and add a visual inspection checkpoint.
Additional Notes
-
Efficiency Tip: Keep a reusable template of the 5‑Why table and the Clarification Request table ready; copy‑paste them for each new defect.
-
Record Keeping: Store the completed 5‑Why Analysis and Root Cause Summary in the same location as the original defect report for audit traceability.
-
Continuous Learning: Periodically review collected root causes to identify trends and update standard work or training materials accordingly.
