5 Why Root Cause Analysis — User Guide

Root Cause Analysis Tool

When to use this root cause analysis tool

Use the 5 Why Root Cause Analysis tool to define a problem, trace cause chains, confirm the real root cause, assign prevention-focused corrective actions, and generate a sponsor-ready report.

Launch 5 Why Tool
View Quick Reference

What the tool does

The tool helps project managers, PMO leads, quality managers, workstream leads, and facilitators run a structured 5 Why Root Cause Analysis. It is useful when a problem, incident, readiness failure, process gap, or adoption issue needs more than a quick fix.

Define the problem

Capture the incident, impact level, observed facts, facilitator, and project context before jumping to causes.

Trace the why chain

Ask why up to five times, add evidence, classify the cause type, and mark where the root cause has been reached.

Confirm the root cause

Use the visual root cause map to check whether the chain is logical, evidence-based, and actionable.

Assign corrective actions

Connect each root cause to prevention-focused actions with owners, due dates, status, and success measures.

Generate AI critique

Request an AI RCA analysis to test weak links, challenge premature conclusions, and improve the action plan.

Export the report

Create a sponsor-ready report, export JSON or CSV, and print or save the analysis as a PDF.

Confidentiality reminder: the tool stores data locally in your browser unless you export it. AI analysis sends your problem statement, why answers, evidence, and actions to the LLM service, so avoid personal data and unnecessary sensitive detail.

Open the tool

Open your browser and go to https://5why.readinesscompass.com. You should see the ReadinessCompass logo, the title 5 Why Root Cause Analysis, and a blank analysis form.

First time visiting? Click Load demo to populate the tool with a realistic sample analysis.
Starting fresh? Click Reset to clear all data and begin with an empty analysis.
Protecting current work? Export JSON before loading demo data or resetting the browser state.

Understand the screen layout

The tool uses a two-column working layout: a wider left column for the analysis and a narrower right column for live metrics, the process guide, and quality checks.

Left column: analysis workspace

Problem statementCause analysisRoot cause mapCorrective actionsReport previewAI RCA analysis

Right column: quality guide

Completion %BranchesActionsQuality checks

The top-right toolbar contains + Add cause branch, Load demo, Generate summary, and Print / PDF.

Conduct a 5 Why analysis

Define the problem

Record the project name, problem date, problem statement, affected area, impact level, facilitator, and evidence or observed facts. Write what happened, when it happened, where it happened, and why it matters.

Start the why chain

Use Why 1 to explain why the problem happened. Then use Why 2 to explain Why 1, and continue until the chain reaches a specific, evidence-based cause.

Add evidence and category

Evidence turns the analysis from opinion into finding. Add tickets, metrics, interview notes, logs, process observations, survey feedback, or other facts. Classify causes as People, Process, Technology, Data, Governance, or External where helpful.

Mark the root cause

Tick Is root cause? on the why level where the chain should stop, then write a final root cause statement that is specific, evidence-based, and actionable.

Add branches when needed

Some incidents have more than one root cause. Use + Add cause branch for separate causes such as process gap, resource constraint, system limitation, or governance issue.

Save and protect the work

The tool autosaves to the browser. Export JSON regularly because autosave is per-browser and per-device.

Problem field	What to enter	Example
Project name	Project or initiative context	ERP Rollout 2026
Problem date	When the problem occurred or was identified	2026-06-15
Problem statement	Specific description of what happened, when, where, and with what impact	Monthly financial close report was three days late, causing the CFO board pack to miss its deadline.
Problem area	Team, process, or system affected	Finance / Record to Report
Impact level	Severity of the impact	High
Evidence / observed facts	Data, examples, tickets, incidents, observations, or feedback	CFO email complaint; close report due 2026-06-15 and delivered 2026-06-18.

Good root cause statement: “No cross-training plan exists for the monthly close process; only one analyst knows the reconciliation steps, and there is no documented backup procedure.” Avoid vague conclusions such as “lack of communication.”

Understand the root cause map

The map visualises the causal flow from problem to why-chain, decision point, root cause, and solution. Use it as a quick check before you move from diagnosis to corrective action.

Problem→Why 1→Why 2→Why 3→Why 4→Why 5→Root cause→Solution

Blue boxes show the why answers in sequence.
The decision point tells you whether to ask why again or confirm the logical root cause.
The green root cause should be specific, evidence-based, and actionable.
The red solution should prevent recurrence, not only repair the immediate symptom.

Add corrective actions

Once the root cause is clear, define actions that change the system so the issue is less likely to happen again.

Action field	What to enter	Example
Action	The specific prevention-focused corrective action	Create a cross-training plan and document the monthly close procedure.
Owner	Person accountable for completion	Finance Operations Manager
Due date	Target completion date	2026-07-30
Status	Not started, In progress, or Done	Not started
Success measure	How the team will know the action worked	Two analysts can independently produce the close report.
Branch	Which root cause branch the action addresses	Primary cause

Prevention beats reaction. “Assign a backup analyst next month” may fix the immediate symptom. “Create a cross-training plan, document the procedure, and add a succession readiness check” changes the system.

Generate a report

Use Generate summary once the analysis is ready for sponsors, steering committees, quality records, or a problem-solving review.

The report includes problem statement, date, area, impact, facilitator, and evidence summary.
Each branch includes its why chain, root cause, notes, and related corrective actions.
The summary modal lets you copy the report or download it as a text file.
Print / PDF opens the browser print dialog and produces a cleaner report layout.

Generate an AI-powered RCA analysis

After you have entered a problem statement and at least some why answers, use the AI panel to critique the quality of the root cause analysis.

Quick critique

About 600 words covering executive summary, root cause verdict, top issues, and suggested actions.

Deep RCA analysis

About 2500 words covering problem statement critique, chain critique, prevention actions, strengths, and sponsor-ready RCA summary.

Regenerate after edits

If you change why answers or actions after generating, run the AI analysis again so the critique reflects the latest state.

Status indicators: Live LLM means the backend is connected. Mock mode means no LLM key is configured. Backend not reachable means the service is down or temporarily unavailable.

Export your data

Export early and often. The analysis lives in the browser, so JSON export is the safest way to preserve or share a working copy.

Export JSON

Creates a full backup of the problem statement, branches, whys, root causes, actions, and notes.

Import JSON

Restores a previous analysis so a colleague can continue editing or you can recover work on another device.

Export CSV or PDF

CSV gives spreadsheet-friendly why-chain data. Print / PDF creates a clean printable report.

Troubleshooting

Data disappeared after refresh

Check whether you used a private window, cleared browser data, or changed device. Restore from an exported JSON file.

AI panel shows Mock mode

The backend does not have an LLM key configured. The mock analysis can still help, but it is heuristic rather than live AI.

Backend not reachable

Wait briefly and refresh. If it persists, contact the project owner.

Root cause pending

Write the final root cause statement and tick the why level where you believe the chain should stop.

Report preview is empty

Click Generate summary. The report preview is generated on demand.

Demo data replaced my work

Import your JSON backup if you exported one. Next time, export before loading demo data or resetting.

Quick reference card

I want to…	Do this
Start a new analysis	Click Reset, then fill in the problem statement.
Add a why answer	Type in the Why N answer field.
Add evidence	Type evidence next to the why answer.
Mark the root cause	Tick the Is root cause? checkbox.
Add a second cause branch	Click + Add cause branch.
Add a corrective action	Click + Add action in Section 4.
Generate a report	Click Generate summary.
Generate an AI critique	Scroll to Section 6 and click Generate AI analysis.
Backup my data	Click Export JSON in the toolbar.
Print a clean report	Click Print / PDF.

Confidentiality note

The 5 Why Root Cause Analysis tool may contain sensitive information about incidents, failures, personnel, or process gaps. Treat the analysis as confidential and avoid unnecessary personal data.

For sensitive incidents: use roles instead of names, use generic system or team labels where possible, keep evidence references indirect, delete local data after generating the final report, and do not share JSON exports outside the core RCA team.

When to use this tool vs the others

The 5 Why tool is for problem solving and incident analysis after something has happened. Other ReadinessCompass tools support earlier transformation planning, stakeholder mapping, impact management, or steering governance.

Tool	When to use	Output
Complexity Assessment	At the start of a program, to assess overall change complexity	Score, classification, radar chart, AI implementation strategy
Stakeholder Analysis	To map stakeholder groups and plan engagement	Bubble heatmap, priority scores, AI engagement strategy
Change Impact & Mitigation Register	To list specific changes and track mitigation	Impact register, KPIs, Excel import/export, AI mitigation strategy
Transformation RAID Log	To track risks, assumptions, issues, and dependencies	RAID log, Excel import/export, AI weekly steering report
5 Why Root Cause Analysis	When a problem or incident occurs and you need to find the root cause	Why-chain, root cause map, corrective actions, AI RCA critique

Incident response flow

Identify the problem, run the 5 Why analysis, define corrective actions, generate the AI critique, create the sponsor report, and link unresolved risks or issues into the RAID Log.

Ready to run the analysis?

Open the 5 Why Root Cause Analysis tool and work through the problem statement, why chain, root cause map, corrective actions, and AI RCA analysis.

Launch 5 Why Tool View Quick Reference