Root Cause Analysis Workbook: Guided 5-Whys & Fishbone Investigations

The problem this kills

An incident happens, and the investigation that follows is only as good as the questions someone thought to ask. Too often the analysis stops at the first easy answer — "operator error," "didn't follow the procedure" — and the real, systemic cause never surfaces. So the same near-miss comes back next quarter, the corrective action treats a symptom, and when an auditor or regulator asks "how did you land on this root cause?" the trail is a few bullet points in a Word file nobody can reconstruct.

Good root cause analysis is structured: a 5-Whys chain that keeps pushing past the obvious, or a fishbone that forces you to look at people, process, equipment, material, and environment instead of just blaming the nearest human. The hard part is doing that consistently, on every incident, under time pressure — and keeping a clean record of how you got there. That's exactly the kind of disciplined, repeatable work you can build a tool for. And you do not need to be a developer to build it.

What you'll build

A simple internal web tool for your EHS and quality team. You open an incident, and the tool walks you through a guided investigation: a 5-Whys chain, a fishbone across the five classic categories, or both. At each step the AI proposes probing follow-up questions ("you said the guard was removed — why was it possible to run the machine with the guard off?") and drafts candidate contributing and root causes — but those suggestions stay clearly marked as AI drafts. The investigator decides what's real, recording the causes they confirm in their own words. When the analysis is done, the investigation lead reviews and approves the official root cause(s) and the recommended actions. Only then does the tool commit them and export an RCA report (PDF/CSV) plus a CAPA-ready action list you can hand straight to corrective action. The full reasoning trail — every AI suggestion, every human edit — is stored.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how you run investigations today, what your incident records actually contain, which methods you use (5-Whys, fishbone, or both), your severity and approval rules, the categories and templates you already rely on, and the messy edge cases like multi-cause incidents or contractor involvement. It reads a short spec back to you for a thumbs-up, then builds the tool around your world instead of a generic template. From there it walks the agent through the data model, opening an incident, the guided 5-Whys and fishbone screens with AI-suggested questions kept separate from confirmed answers, the lead's approval gate, and the RCA report and CAPA export. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a defensible investigation needs: login so only your team can use it, row-level security so people only see their own organization's incidents, a complete audit trail of every cause edit, suggestion, and approval (who, what, when, and why), a hard human-approval gate so the AI never sets the official root cause — the lead does — and a duplicate guard so each incident gets exactly one RCA. The AI is there to ask better questions and draft possibilities; a qualified person makes the call and signs their name to it.

Who it's for

EHS investigators, quality engineers, and supervisors who need consistent, defensible investigations and are tired of root causes that stop at "human error." If you can describe how you investigate an incident today, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be running your first guided investigation this weekend.