Workshop · Problem solving
A blame-free RCA in 75 minutes: timeline, contributing factors, five whys on the top causes and actions ranked by how strongly they fix the system.
Free to use and to run live. No card needed.
Root cause analysis (RCA) is a structured way to find why a problem or incident happened so it doesn't happen again. This template runs a blame-free 75-minute RCA: a timeline and contributing factors from everyone's phone, dot voting, five whys on the top causes and actions ranked by strength, each with an owner and a measure.
01Inside
Root cause analysis with 5 areas, and a 75-minute agenda that runs it.
“Add a fact to the timeline, a contributing factor or a why. Facts and systems, not names.”
By the end of this meeting, we understand how the system allowed this to happen and have strong actions with owners, dates and measures.
02In the room
The shared screen, every phone and the summary afterwards, drawn from this template.
On the shared screen
Ideas land on the board from every phone, with no names on the notes. Then everyone dot-votes what matters most.
On every phone
People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.
Afterwards
Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.
03How to run it
Gather the facts before the meeting (records, logs, short interviews) and open with a clear no-blame statement.
Build the timeline and contributing factors from phones. Names don't show on the notes, which gets you details people won't say out loud.
Dot-vote the top factors and ask five whys on each until you reach something the organization controls.
Rank actions by strength and give each one an owner, a date and a measure. Set a date to check the actions actually worked.
04Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
A method for finding the underlying causes of a problem rather than its symptoms, so the fix prevents it from happening again. Common tools include a timeline, a fishbone diagram and the five whys.
After serious patient safety events, teams review what happened with a focus on systems, not individuals. The Joint Commission expects a comprehensive systematic analysis, such as an RCA, after a sentinel event.
A problem statement, a timeline of facts, contributing factors, the root causes with evidence, and corrective actions with owners, dates and a way to measure whether they worked.
The structure, wording and safety points in this template follow these published sources.
Keep going
Change anything in the editor. When you're ready, press Run live: everyone joins with a scan and answers on their phone.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
Root cause analysis workshopFree template