Aidar Akmaev
Disclosure: NOXI publishes this guide and is one of the tools it mentions; the method works in any presentation software.
Quick answer: A root cause analysis presentation proves what caused a problem and what will stop it coming back. Use 9 slides in 15 minutes: the problem with its number, containment, timeline, a Pareto of where it concentrates, causes considered, the causal chain with evidence, corrective and preventive actions, cost and payback, and how and when you will check the fix worked.
Many root cause analysis decks stop at a fishbone covered in sticky-note causes. A plant manager, customer or patient-safety committee needs to see which cause was proven, by what evidence, what changes, who owns it and when it will be checked.
In short
- The ruleUse a fishbone to widen the search, 5 Whys to go deep, data to prove it, and an A3 or 8D to present it: problem, evidence, root cause, action, and the date you will check it worked.
- Length9 slides in 15 minutes, plus 10 minutes of questions; the full analysis stays in the written RCA report.
- ActionsContainment, corrective and preventive actions with owners, dates and strength; at least one stronger than training.
- Methods scoredA3 74, 8D 68, fishbone 60, Pareto 60, FMEA 56, 5 Whys 50, fault tree 50, for the job of presenting an RCA, on six printed rules.
- Worked exampleCalder Valve Co. cuts leak returns from 2.23% to an expected 0.31%: an $18,664 fix that saves $30,530 a quarter and pays back in 1.8 months.
Key numbers
What is root cause analysis?
Root cause analysis (RCA) is a structured method for finding why a problem happened, at the level of the system rather than the individual, so that corrective actions stop it recurring. AHRQ describes it as a structured method used to analyse serious adverse events [5]; manufacturers apply it to defects, returns and complaints.
A root cause is the deepest cause you can still act on and verify: remove it and the problem stops. An RCA often finds one root cause and several contributing factors, and the presentation says which is which.
What root cause analysis is not
Root cause analysis is not a search for someone to blame or a brainstorm. The Veterans Health Administration's five rules of causation say a human error or a procedure violation must have a preceding cause, and a failure to act is causal only where there was a duty to act [6].
| Term | What it means | Example (valve plant) |
|---|---|---|
| Symptom | What the customer or patient sees | Valves leak in service |
| Direct cause | The physical event behind the symptom | Seals damaged in assembly |
| Contributing factor | A condition that made the problem more likely or let it escape | The leak test sampled 1 valve in 50 |
| Root cause | The system cause that, removed, stops recurrence | No fixture wear check in the maintenance plan |
Manufacturing teams often separate the occurrence root cause (why the defect was made) from the escape point (why it reached the customer); both deserve an action.
Root cause analysis steps
Root cause analysis has seven steps: define the problem with a number, contain it, collect data, identify possible causes, verify the root cause with evidence, act, and check that the actions worked. The presentation follows the same order.
| Step | What you do | Output that goes on a slide |
|---|---|---|
| 1. Define | What, where, since when, how big | Problem statement with a rate |
| 2. Contain | Protect the customer or patient while you investigate | Containment action and its start date |
| 3. Collect data | Records, measurements, samples, interviews | Timeline and Pareto |
| 4. Find causes | List possible causes by category (fishbone), then drill down (5 Whys) | Causes considered, ruled in or out |
| 5. Verify | Reproduce or measure the cause | Causal chain with evidence |
| 6. Act | Corrective and preventive actions | CAPA table and payback |
| 7. Check | Measure on a date set in advance | Effectiveness metric and review date |
How long does a root cause analysis take?
A root cause analysis takes from an hour for a shop-floor 5 Whys to several weeks for a serious event. The Joint Commission expects a comprehensive systematic analysis and corrective action plan within 45 business days of a sentinel event or of becoming aware of it [3]; the Veterans Health Administration's own RCAs are due within 45 calendar days [6]; manufacturing customers set deadlines in their supplier requirements.
The 9-slide root cause analysis presentation template
The 9-slide root cause analysis presentation runs 15 minutes: problem, containment, timeline, Pareto, causes considered, causal chain, actions, payback and the effectiveness check. The causal chain gets the most time because a sceptical audience tests it.
| # | Slide | What goes on it | Minutes |
|---|---|---|---|
| 1 | The problem | What, where, since when, how big, as a number | 1 |
| 2 | Containment | What protects the customer or patient, since when | 1.5 |
| 3 | Timeline | Event sequence or defect trend | 1.5 |
| 4 | Where it concentrates | Pareto of the problem by type, line, shift or product | 2 |
| 5 | Causes considered | Fishbone categories, each cause ruled in or out | 2 |
| 6 | The causal chain | 5 Whys to the root cause, with the evidence under each step | 2.5 |
| 7 | Actions (CAPA) | Containment, corrective and preventive actions: owner, date, strength | 2 |
| 8 | Cost and payback | Fix cost, saving, payback with its formula | 1.5 |
| 9 | How we will know | Metric, threshold, check date, decision needed | 1 |
| Total | 9 slides | 1 + 1.5 + 1.5 + 2 + 2 + 2.5 + 2 + 1.5 + 1 | 15 |
The timings are our planning guidance for a 25-minute slot, not a standard. With 10 minutes, merge slides 3 and 4, and 8 and 9. With a customer, open on containment: their first question is whether bad parts are still on the way.
How many slides for a root cause analysis presentation?
A root cause analysis presentation needs about 9 slides for 15 minutes. Fewer than 6 usually means the evidence or the check is missing; more than 12 means the investigation diary moved onto slides.
Root cause analysis report vs presentation
A root cause analysis report is the full written record: team, scope, data, interviews, every cause considered, evidence and action plan; the presentation is the 15-minute argument built from it. Write the report first, then title every slide as a finding ("Seal damage is 60.0% of returns", not "Pareto analysis"), so the deck also works as a pre-read.
How to present root cause analysis findings
Present root cause analysis findings as a chain of facts, each with its evidence, ending in actions with owners and dates. Say what was proven, what was ruled out and what is still unknown, and state causes as conditions in the system, not as a person's failing.
Five rules for the findings slides
- One piece of evidence per step. Every "why" carries a measurement, record, test result or observation; a step without one is labelled "probable" and gets an action to confirm it.
- Show what you ruled out. Slide 5 lists every cause considered, ruled in or out, with the reason, which answers the reviewer's question: did you look at the material, the method, the people?
- Cause and effect in one sentence. As the VA's first rule asks: "the worn pin let the seal seat off-centre, which tore its lip", not "fixture problem" [6].
- Specific words, no blame. The VA's second rule asks for specific, accurate descriptors instead of negative, vague words: "the maintenance plan had no wear check for this fixture", not "poor maintenance" [6].
- Actions match causes. Each root cause and contributing factor has an action, and each action points back to a cause.
Root cause analysis methods and tools, one by one
The seven root cause analysis methods compared here are 5 Whys, the fishbone (Ishikawa) diagram, Pareto analysis, fault tree analysis, FMEA, 8D and A3. Fishbone, FMEA and fault tree map many causes, 5 Whys goes deep on one, Pareto prioritises with data, and 8D and A3 are formats for running and presenting the whole analysis.
5 Whys
The 5 Whys follows one problem down a chain of "why" questions to a system cause. IHI attributes it to Taiichi Ohno of the Toyota Production System and notes that a problem may have more than one root cause [9].
Use it when the problem is narrow and the team knows the process. Watch for one chain hiding a second cause, or an answer that stops at a person.
Fishbone diagram (Ishikawa, cause and effect)
IHI describes the cause and effect diagram, also known as the Ishikawa or fishbone diagram, as a tool for exploring and displaying the possible causes of an effect, with classic categories of materials, methods, equipment, environment and people [8]. Manufacturing teams often use the 6M version: machine, method, material, people (man), measurement and environment (mother nature).
Use it when nobody knows where the cause lies. Watch for unverified opinions presented as findings.
Pareto analysis
Pareto analysis sorts the contributors to a problem from largest to smallest so the team works on the "vital few" that account for most of the effect. IHI describes the Pareto chart as a bar chart that arranges contributing factors in order of the size of their effect [10].
Fault tree analysis
Fault tree analysis starts from one undesired top event and works downward through AND and OR gates to the combinations of failures that can cause it. NASA's Fault Tree Handbook (version 1.1, August 2002) calls it a deductive, failure-based approach [14].
FMEA (failure mode and effects analysis)
FMEA lists each step or component, how it could fail, the effect of each failure and the controls in place, then ranks the failure modes and records an action against the riskiest. IHI calls it a systematic, proactive method for evaluating a process or product to find where and how it might fail, particularly useful before a new process is implemented [11].
Watch for presenting the full worksheet; show the top five failure modes.
8D (eight disciplines)
8D is a team problem-solving format with eight steps, from forming a team and containing the problem to verifying the root cause, implementing permanent corrective actions and preventing recurrence. The Automotive Industry Action Group (AIAG) teaches an 8-D approach to corrective action alongside its CQI-20 Effective Problem Solving Guide [12].
Watch for eight filled boxes with no evidence in D4.
A3 problem solving
A3 problem solving puts the whole problem on one sheet of A3 paper: the current situation, the analysis, the countermeasures, the action plan with who and when, and the follow-up showing whether it worked. The Lean Enterprise Institute describes the A3 report as a method Toyota pioneered [13].
5 Whys vs fishbone: when to use which
Use a fishbone diagram to widen the search across every category of cause, and 5 Whys to go deep on the cause the data points to. The fishbone stops a team from fixing the first cause it thinks of; the 5 Whys stops it from stopping at a symptom. Use both, in that order, and prove the result with data.
| Question | Fishbone | 5 Whys |
|---|---|---|
| Direction | Wide: many causes, several categories | Deep: one chain from symptom to root cause |
| Best when | The cause is unknown and the team disagrees | The problem is narrow and the team knows the process |
| Time | An hour or more of team discussion | Minutes to an hour |
| Main risk | Opinions presented as findings | One chain hides a second cause |
| On the slide | A table of causes ruled in or out | Five boxes with evidence under each |
How to combine fishbone and 5 Whys
Combine them in four moves: draw the fishbone and mark each cause likely or unlikely; check the likely ones against data; run a 5 Whys on each cause the data supports; and write each chain's last answer as a cause and effect sentence with its evidence.
Fault tree analysis vs fishbone
A fishbone groups possible causes by category with no logic between them; a fault tree links them with AND and OR gates, showing which failures must combine to produce the top event, with probabilities if needed. Use a fishbone to brainstorm and a fault tree when combinations matter.
FMEA vs root cause analysis
FMEA is proactive: it looks for ways a process could fail before it does. Root cause analysis is reactive: it explains a failure that happened. After an RCA, update the FMEA and check other lines for the same failure mode; to score and present those risks, see our risk management presentation guide.
Seven root cause analysis methods scored for presenting an RCA
For the job of presenting a root cause analysis, A3 scores 74 out of 100, 8D 68, fishbone and Pareto 60, FMEA 56, and 5 Whys and fault tree 50, on six criteria with printed rules. The scores rank fit for a presentation, not method quality: FMEA and fault tree are strong tools that belong in an appendix.
How we scored: 1, 3 or 5 per criterion, by the rules below, applied the same way to every method from its documented steps; weighted score = rating ÷ 5 × weight, out of 100. This is our editorial rubric, not a hands-on test.
| Criterion (weight) | 5 means | 3 means | 1 means |
|---|---|---|---|
| C1 Breadth of causes (20) | Structures several cause categories or branches by design | Several causes, no built-in structure (ranked from data, or the tool is left to the team) | One causal chain per problem statement |
| C2 Verification built in (20) | A named step verifies the cause or the fix | Data-based, but verification is not a named step | No verification step |
| C3 Speed (15) | The documented steps usually take under an hour with a small team | Hours to a few days | Weeks, because the steps include implementation or follow-up |
| C4 Actions built in (15) | Corrective or preventive actions with owners and dates are a named step | An actions column or field | Analysis only |
| C5 Fits on one slide (15) | Designed as one page or one figure | A multi-section form spread over several slides | A worksheet or large diagram for the appendix |
| C6 Recognised (15) | Named in a regulation or customer requirement opened on publish day | Taught by a national public body or a non-profit professional or industry body | Neither found |
| Method | C1 | C2 | C3 | C4 | C5 | C6 | Weighted total (arithmetic) |
|---|---|---|---|---|---|---|---|
| A3 problem solving | 3 | 5 | 1 | 5 | 5 | 3 | 12 + 20 + 3 + 15 + 15 + 9 = 74 |
| 8D | 3 | 5 | 1 | 5 | 3 | 3 | 12 + 20 + 3 + 15 + 9 + 9 = 68 |
| Fishbone | 5 | 1 | 3 | 1 | 5 | 3 | 20 + 4 + 9 + 3 + 15 + 9 = 60 |
| Pareto analysis | 3 | 3 | 3 | 1 | 5 | 3 | 12 + 12 + 9 + 3 + 15 + 9 = 60 |
| FMEA | 5 | 3 | 1 | 3 | 1 | 3 | 20 + 12 + 3 + 9 + 3 + 9 = 56 |
| 5 Whys | 1 | 1 | 5 | 1 | 5 | 3 | 4 + 4 + 15 + 3 + 15 + 9 = 50 |
| Fault tree analysis | 5 | 3 | 1 | 1 | 1 | 3 | 20 + 12 + 3 + 3 + 3 + 9 = 50 |
A3 and 8D score 5 on verification and actions because both name a check step and an action plan with owners and dates, and 1 on speed because those steps run for weeks; A3 leads because it was designed as one page, while 8D is a multi-section form.
C6 on 21 October 2026: every method appears in such guidance (fishbone, 5 Whys, Pareto and FMEA in IHI's toolkits [8–11], 8D in AIAG's training [12], A3 at the Lean Enterprise Institute [13], fault tree in NASA's handbook [14]), and none in a regulation we opened. The Joint Commission lets each organisation choose its tools, though its thoroughness test says the analysis must repeatedly ask "Why?" until it identifies the systemic causal factors [3]. So all score 3. If your customer's manual requires an 8D, re-score it to 5 on C6: 68 becomes 74, level with A3.
Which root cause analysis method should you use?
| Your situation | Start with | Present as |
|---|---|---|
| Narrow shop-floor problem | 5 Whys, checked with one measurement | One A3 slide |
| Cause unknown, team disagrees | Fishbone, then Pareto on the data | The 9-slide deck |
| Customer complaint (automotive, electronics) | Fishbone and 5 Whys inside the 8D steps | The customer's 8D form plus a 9-slide deck |
| Serious patient-safety event | RCA² with a cause and effect diagram | The committee's format, with the action plan |
| Complex system, combined failures | Fault tree | One branch on a slide, the tree in the appendix |
| New or changed process | FMEA (proactive) | Top five failure modes and their actions |
Root cause analysis presentation example: Calder Valve Co., slide by slide
The Calder Valve Co. example is a complete root cause analysis presentation: a 2.23% leak-return rate, 60.0% of returns on one defect, a five-step causal chain with evidence, an $18,664 fix and a 1.8-month payback.
Slide 1: the problem in one number
412 of 18,500 valves shipped in Q3 2026 returned for leaks: 412 ÷ 18,500 = 2.23%. Each return costs Calder $86 to handle (inspection, replacement valve and freight, from its own cost records), so the quarter cost 412 × $86 = $35,432.
Slide 2: containment
From 2 October 2026 every valve gets a leak test before shipping, instead of 1 in 50. No leaking valve has shipped since.
Slide 3: timeline
Returns rose for valves built from week 27 (from 29 June 2026). The locating pin on press 3's seating fixture was last replaced in March 2024.
Slide 4: where it concentrates (Pareto)
| Defect type | Returns | Share (returns ÷ 412) | Cumulative share |
|---|---|---|---|
| Seal damage | 247 | 247 ÷ 412 = 60.0% | 60.0% |
| Thread damage | 82 | 82 ÷ 412 = 19.9% | 329 ÷ 412 = 79.9% |
| Body crack | 49 | 49 ÷ 412 = 11.9% | 378 ÷ 412 = 91.7% |
| Other | 34 | 34 ÷ 412 = 8.3% | 100% |
| Total | 247 + 82 + 49 + 34 = 412 | 100.1% (rounding) |
The shares add to 100.1% from rounding; the slide says so in a footnote. Lot codes traced 221 of the 247 seal-damage returns to press 3: 221 ÷ 247 = 89.5%.
Slide 5: causes considered (fishbone as a table)
| Category | Cause considered | Verdict and evidence |
|---|---|---|
| Machine | Press 3 seating fixture | Ruled in: pin worn 0.4 mm; 89.5% of seal returns from press 3 |
| Method | Seating sequence | Ruled out: same work instruction on all 6 presses |
| Material | Seal batch | Ruled out: lots from both seal suppliers failed at the same rate |
| People | Operator training | Ruled out as a cause: no difference between the 3 shifts |
| Measurement | Leak test sampling | Contributing factor: 1 in 50 sampling let leaking valves escape |
| Environment | Shop temperature | Ruled out: within the 18–24 °C range all quarter |
Slide 6: the causal chain (5 Whys with evidence)
- Why do valves leak? The seal lip is torn. Evidence: 30 returned seals sectioned under a microscope.
- Why is the lip torn? Seals were pressed off-centre. Evidence: 27 of 30 sectioned seals (90%) show off-centre compression marks.
- Why off-centre? The fixture's locating pin is worn 0.4 mm. Evidence: pin measured on 6 October against its 0.1 mm wear limit.
- Why was the wear not caught? The maintenance plan has no wear check for this fixture. Evidence: maintenance records, March 2024 to October 2026.
- Why is there no check? The plan was copied in 2024 from a press model that has no such fixture. Evidence: plan revision history. This is the root cause.
Slide 7: corrective and preventive actions
| Type | Action | Owner and date | Strength (VA hierarchy) |
|---|---|---|---|
| Containment | Leak test every valve before shipping | Quality manager, from 2 Oct 2026 | Temporary |
| Corrective | New press 3 fixture with a hardened, replaceable pin: $14,200 | Maintenance lead, done 9 Oct 2026 | Intermediate (substitute the device) |
| Preventive | Fixture wear check added to the maintenance plans of all 6 presses | Maintenance lead, by 30 Oct 2026 | Intermediate (checklist) |
| Preventive | Train 24 operators for 6 hours on the new check: 24 × 6 × $31 = $4,464 | Production supervisor, by 20 Nov 2026 | Weaker (training) |
Fix cost: $14,200 + $4,464 = $18,664. The containment test is a running cost carried in the line budget until the check on 15 January 2027.
Slide 8: cost and payback
Since 9 October, the new fixture has built 6,200 valves, and the 100% leak test caught 19 leaks: 19 ÷ 6,200 = 0.31%, against 2.23% before. Calder uses that rate as the expected return rate once 100% testing ends.
| Line | Arithmetic | Result |
|---|---|---|
| Returns before, a quarter | Q3 2026 actual | 412 |
| Returns expected after | 18,500 × 19 ÷ 6,200 = 56.7 | 57 |
| Returns avoided | 412 − 57 | 355 |
| Saving a quarter | 355 × $86 | $30,530 |
| Fix cost | $14,200 + $4,464 | $18,664 |
| Payback | $18,664 ÷ $30,530 × 3 months | 1.8 months |
| Saving a year | $30,530 × 4 | $122,120 |
Check: $35,432 − 57 × $86 = $35,432 − $4,902 = $30,530. Payback is rounded once, at the end: 18,664 ÷ 30,530 × 3 = 1.83, shown as 1.8 months. For a larger capital request, use our business case presentation guide.
Slide 9: how we will know it worked
Effectiveness check on 15 January 2027: the leak rate found by the 100% test must stay below 0.5% for all valves built on the new fixture to the end of Q4; at a full quarter's 18,500 valves that means 92 leaks or fewer (18,500 × 0.005 = 92.5). If it passes, leak testing returns to 1 in 10; if it fails, the RCA reopens. Decisions needed today: ratify the $14,200 fixture bought on 9 October under the containment authority, and approve the $4,464 training.
Here are two slides from this article's worked example, as NOXI built them, unedited.
Corrective and preventive action (CAPA): the slide that changes things
Corrective and preventive action (CAPA) removes the root cause of a problem that happened (corrective) and stops the same cause producing problems elsewhere or later (preventive), each action with an owner, a date and a check that it worked.
Containment vs correction vs corrective action vs preventive action
| Type | What it does | Example |
|---|---|---|
| Containment | Protects the customer now; temporary | Test every valve before shipping |
| Correction | Fixes the bad output already made | Replace the 412 returned valves |
| Corrective action | Removes the root cause where it occurred | New fixture on press 3 |
| Preventive action | Stops the same cause elsewhere or later | Wear check on all 6 presses |
Action strength: why "retrain staff" is not enough
Actions differ in strength: the less an action depends on people remembering, the more effective it is. The Veterans Health Administration's action hierarchy, modelled on the hierarchy of controls, sorts actions into stronger, intermediate and weaker, and says an action plan should not consist only of weaker actions [6].
| Strength | Examples from the VA action hierarchy | On a manufacturing slide |
|---|---|---|
| Stronger | Physical changes, forcing functions or interlocks, simplified and standardised processes | A fixture that cannot accept a seal off-centre |
| Intermediate | Substitute a device, redundancy, software changes, checklists, reduced workload | New fixture; wear check in every maintenance plan |
| Weaker | Double checks, warnings, new policy or memo, training, more study | Operator training; a warning label |
Weaker actions still help: the VA notes that training is often needed for a stronger action to be used well [6], while AHRQ lists over-reliance on weak solutions such as education among the reasons RCAs fail [5]. A strength column on the CAPA slide shows whether the plan changes the system. Close with an effectiveness check that can fail: a metric, a threshold, a period and a review date, not "monitor going forward".
8D reports and A3s: presenting to a customer or to management
An 8D report is the customer-facing format for a root cause analysis and an A3 the one-page management format; both carry the content of the 9-slide deck.
What is an 8D report?
An 8D report documents a problem solved in eight disciplines. The common form, with the slide each discipline maps to:
| Discipline | Content | Slide in the 9-slide deck |
|---|---|---|
| D1 Team | Cross-functional team and its leader | Title slide or appendix |
| D2 Problem | What, where, when, how big | 1 |
| D3 Containment | Interim actions protecting the customer | 2 |
| D4 Root cause | Root cause and escape point, verified | 3 to 6 |
| D5 Choose actions | Permanent corrective actions, verified before full use | 7 |
| D6 Implement | Actions in place, containment removed, results validated | 7 and 9 |
| D7 Prevent | Systems, procedures and similar products changed | 7 |
| D8 Recognise | Thank the team, close the report | Closing line |
Customers often add a step before D1 for emergency response and set deadlines per discipline; follow their form. Payback has no 8D discipline, so leave it out of the customer version if costs are confidential.
What is an A3 report?
An A3 report is a one-page problem-solving summary on a sheet of A3 paper (297 by 420 millimetres), with the problem and current condition on the left and the countermeasures on the right, plus who does what by when and evidence that it worked [13]. A typical A3 problem solving sequence runs background, current condition, goal, root cause analysis, countermeasures, plan with who and when, and follow-up. To present one, show it whole, then zoom into its blocks over two or three slides.
Root cause analysis in healthcare: RCA² and the Joint Commission timeline
In US healthcare, a root cause analysis follows a sentinel event: a patient safety event, not primarily related to the natural course of the patient's illness, that reaches a patient and results in death, permanent harm or severe harm. The Joint Commission expects a thorough and credible comprehensive systematic analysis and corrective action plan within 45 business days of the event or of becoming aware of it [2][3].
The Joint Commission adopted its Sentinel Event Policy in 1996 [2]; AHRQ notes it has required RCA for sentinel events since 1997 [5]. Reporting to the Joint Commission is strongly encouraged but not required, yet every sentinel event must undergo a comprehensive systematic analysis, and an unacceptable response gets an additional 15 business days to resubmit [3].
What the Joint Commission asks the action plan to contain
The Sentinel Event Policy chapter in the July 2026 update of the Joint Commission's home care manual says the corrective action plan must cover actions tied to the causal and contributory factors, who is responsible, timelines, how effectiveness will be evaluated and how the change will be sustained, and that the organisation should identify at least one intermediate or stronger action [3]. Each accreditation programme has its own manual.
RCA²: root cause analysis and action
RCA² (root cause analyses and actions) is the name the National Patient Safety Foundation, now part of IHI, gave the process in 2015 to stress that prevention requires action; it looks at system vulnerabilities, not individual performance [7]. A committee version follows the 9-slide spine with no patient identifiers and the action plan, with strength ratings, as the longest slide.
The Joint Commission says that in January 2027 its Sentinel Event List will adopt the 28 events on the National Quality Forum's Serious Reportable Events list and keeps three workforce safety events [4]. For the patient-level talk at rounds, see our clinical case presentation guide.
This section describes published policy for presentation purposes only; it is not legal, regulatory or clinical advice.
Root cause analysis in manufacturing: FDA's QMSR since 2 February 2026
In manufacturing, root cause analysis starts from a defect, a return or a complaint and ends in a CAPA record or an 8D report. For US medical device makers, the FDA's Quality Management System Regulation (21 CFR Part 820) became effective on 2 February 2026 and incorporates ISO 13485:2016 by reference [1].
The FDA's page adds that the QMSR incorporates clause 3 of ISO 9000:2015 for definitions, that the ISO 13485 framework now specifically requires risk management, and that the FDA stopped using its Quality System Inspection Technique (QSIT) for device inspections on 2 February 2026 [1]. On your slides, use the terms of ISO 13485 and your quality manual, and link each corrective action to the risk it reduces. This summarises the FDA's page; it is not compliance advice.
Software and IT incidents
For outages and security incidents, the same logic is usually presented as a postmortem, with a detection-and-restoration timeline and blameless wording. See our incident postmortem presentation guide.
Service operations and projects
In service teams, use the same deck with a Pareto of complaint types or delay reasons on slide 4. When the cause sits in how a project was run, take it to the project closure presentation; when it changes how staff work, see the change management presentation. To share a near miss or an RCA finding with every shift in five minutes, use one of our safety moment ideas.
Pass/fail checklist before you present a root cause analysis
Run this check before you send the pre-read; each line passes only if its condition is true.
- The problem has a number.Count, denominator, period and the rate.
- Containment is dated.What protects the customer now, since when.
- The Pareto adds up.Counts sum to the total; rounding noted; "other" under 20%.
- Every category was considered.Each category: causes ruled in or out, with reasons.
- Every why has evidence.Evidence under each step; unproven steps labelled probable.
- The root cause is a system cause.A condition in a process, design or plan, not a person.
- Each action has an owner, a date and a strength.At least one action is intermediate or stronger.
- The money is shown.Fix cost, saving and payback, with arithmetic.
- The check can fail.Metric, threshold, period, review date and the fallback.
- It fits the slot.Rehearsed under 15 minutes.
For chart choices on slides 4 and 8, see our guide to presenting data.
3 AI prompts for a root cause analysis presentation
Use them in NOXI after attaching your RCA report and defect data, or in any AI tool that accepts files. Replace the brackets; the tool should arrange your evidence, never invent it.
Create a 9-slide root cause analysis presentation for the [plant leadership team], 15 minutes, from the attached [RCA report (Word)] and [defect log (Excel)]: the problem with its rate [412 of 18,500 valves, 2.23%]; containment with its start date; timeline; defect counts by type, largest first, with shares and cumulative shares; causes considered, ruled in or out with evidence; the 5 Whys chain with evidence under each step; actions with owner, date and strength; cost, saving and payback with arithmetic; the effectiveness check and the decision needed. Use every number exactly as in the files and invent none. Titles as full-sentence findings.
On the corrective and preventive actions slide, add a column "Strength" and rate each action as stronger, intermediate or weaker using this list: [physical change or forcing function = stronger; new device, checklist or software change = intermediate; training, memo or warning = weaker]. Add a final row with the effectiveness check [leak rate below 0.5% for Q4, reviewed 15 January 2027]. Change nothing else.
Create a 7-slide 8D summary for our customer [Northfield Pumps] from the attached [8D form (PDF)]: D2 problem, D3 containment, D4 root cause and escape point with evidence, D5 and D6 corrective actions with validation results, D7 preventive actions, and the effectiveness check date. Leave out internal costs and add nothing that is not in the form.
How to build a root cause analysis presentation in NOXI
NOXI turns your RCA report and defect data into a structured deck: it builds the slides from your report, table or outline, and you edit any slide by chat. It is free, with no card and no watermark; uploading files needs a free account, and a deck uses about 25 of the 1,000 monthly credits.
Step 1: Attach your RCA report and defect data
Choose Create from file and attach your RCA report or 8D form (Word or PDF) and your defect log (Excel or CSV), up to 200 MB each. Paste Prompt 1 so NOXI builds the 9 slides from your own evidence.
Step 2: Review the outline first
Choose Plan mode to review the outline. Check that slide one states the problem with its rate, every title reads as a finding and the deck ends with the check and the decision, then generate and watch each slide being built.
Step 3: Check every number against your data
Compare each count, share, cost and date with your files. Edit text on the slide, edit table cells and chart numbers, or ask the AI in plain English or Arabic to correct a figure on one slide or across the deck.
Step 4: Add your logo and brand colour
Add your logo and brand colour. Click any element and tell the AI what to change, for example to highlight the root cause step in the causal chain.
Step 5: Strengthen the actions slide and tighten to 15 minutes
Paste Prompt 2, then ask the AI to move interview notes and raw data to appendix slides after slide 9. Rehearse full-screen in present mode and time yourself.
Step 6: Share, export and present
Share a view-only link for the pre-read, or invite a colleague to edit together in real time. Download an editable PowerPoint (.pptx) with real text boxes and embedded fonts, or a PDF, or present full-screen.
Frequently asked questions
- What is root cause analysis?
- Root cause analysis is a structured method for finding the underlying system causes of a problem, defect or adverse event, proving them with evidence and choosing actions that stop the problem recurring. It moves from symptom to direct cause to root cause, separates contributing factors, and ends with a dated check that the corrective actions worked.
- How do you present a root cause analysis?
- Present a root cause analysis in about 9 slides and 15 minutes: the problem with its number, containment, timeline, a Pareto of where it concentrates, causes considered, the causal chain with evidence, corrective and preventive actions with owners, cost and payback, and the effectiveness check with its date. Write every slide title as a finding.
- What are the steps of root cause analysis?
- Root cause analysis has seven steps: define the problem with a number, contain it to protect the customer or patient, collect data and build a timeline, list possible causes by category, verify the root cause with evidence, choose corrective and preventive actions with owners and dates, and check on a set date that the actions worked.
- What is the difference between 5 Whys and a fishbone diagram?
- A fishbone diagram widens the search, listing possible causes across categories such as machine, method, material, people, measurement and environment. The 5 Whys goes deep, following one cause through repeated questions to a root cause. Use the fishbone first when the cause is unknown, check the likely causes against data, then run 5 Whys on each supported cause.
- What is an 8D report?
- An 8D report documents a problem solved in eight disciplines: form the team, describe the problem, contain it, find and verify the root cause, choose permanent corrective actions, implement and validate them, prevent recurrence, and recognise the team. Automotive and electronics customers often require one for each complaint, on their own form and timetable.
- What is an A3 report?
- An A3 report is a one-page problem-solving summary on a sheet of A3 paper, a method Toyota pioneered. The left side shows the background, current condition and root cause analysis; the right side shows countermeasures, the action plan with owners and dates, and the follow-up. It works as a management presentation on one slide.
- What is CAPA?
- CAPA stands for corrective and preventive action. Corrective action removes the root cause of a problem that has happened; preventive action stops the same cause producing problems elsewhere or later. Each action has an owner, a due date and an effectiveness check. Containment, which protects the customer while you investigate, is temporary and comes first.
- How long do you have to complete an RCA after a sentinel event?
- The Joint Commission expects an accredited US health care organisation to prepare its comprehensive systematic analysis, most commonly a root cause analysis, and corrective action plan within 45 business days of a sentinel event under its policy, or of becoming aware of it. If the response is unacceptable, it allows an additional 15 business days to resubmit.
- Can AI make a root cause analysis presentation from my report?
- Yes. AI presentation tools can turn an RCA report, 8D form or defect spreadsheet into a structured deck, write full-sentence titles and lay out the defect counts, causal chain and action table as slides. Give the tool your own evidence and tell it to invent nothing, then recheck every count, share, cost and date against your data before presenting.
Sources & methodology
How this guide was made: facts come from the FDA, the Joint Commission, AHRQ PSNet, the Veterans Health Administration, IHI, AIAG, the Lean Enterprise Institute and NASA, all checked on 21 October 2026. The template, timings, scorecard rules and checklist are our editorial recommendations, not standards. Calder Valve Co. and its figures are fictional.
- [1] QMSR effective 2 February 2026, amending 21 CFR Part 820; incorporates ISO 13485:2016 and clause 3 of ISO 9000:2015 by reference; the ISO 13485 framework now specifically requires risk management; QSIT no longer used for device inspections from 2 February 2026, compliance programme 7382.850 (content current as of 02/02/2026) — U.S. Food and Drug Administration, Quality Management System Regulation (QMSR). Checked 21 October 2026.
- [2] Sentinel Event Policy adopted in 1996; sentinel event definition; RCA and plan of action submitted within 45 business days of the date the organisation became aware of the event; policy released per accreditation programme (January 2027 releases) — Joint Commission, Sentinel Event Policy and Procedures. Checked 21 October 2026.
- [3] Comprehensive systematic analysis (most commonly a root cause analysis) and corrective action plan within 45 business days; every sentinel event must be analysed whether or not reported; contents of the corrective action plan; the organisation can determine its own process, tools and methodologies; a thorough analysis must repeatedly ask "Why?"; at least one intermediate or stronger action from the VA action hierarchy; an additional 15 business days to resubmit; measures of success tracked for at least 120 days; shading for changes effective 1 July 2026 — Joint Commission, Sentinel Event Policy (SE) chapter, Comprehensive Accreditation Manual for Home Care, Update 1, July 2026 (PDF). Checked 21 October 2026.
- [4] From January 2027 the Sentinel Event List adopts the 28 events on the NQF Serious Reportable Events list and retains three workforce safety events — Joint Commission, Sentinel Events (knowledge library). Checked 21 October 2026.
- [5] RCA definition; Joint Commission has mandated RCA for sentinel events since 1997; one RCA found 17 distinct errors behind a wrong-patient cardiac procedure; a 2017 commentary identified eight common reasons RCAs are ineffective, including over-reliance on weak solutions such as education (UC Davis PSNet Editorial Team, 15 June 2024; last reviewed 2024) — AHRQ PSNet, Root Cause Analysis. Checked 21 October 2026.
- [6] RCA team composition should be between four and six members; VA RCAs completed within 45 calendar days; five rules of causation; action hierarchy (stronger, intermediate, weaker) modelled on the hierarchy of controls; an action plan should not consist only of weaker actions (revision 02/05/2021) — VHA National Center for Patient Safety, Guide to Performing a Root Cause Analysis (PDF). Checked 21 October 2026.
- [7] RCA² renamed root cause analyses and actions; systems-based improvement, not individual performance; National Patient Safety Foundation, 2015 — IHI, RCA2: Improving Root Cause Analyses and Actions to Prevent Harm. Checked 21 October 2026.
- [8] Cause and effect diagram, also called Ishikawa or fishbone; classic categories materials, methods, equipment, environment and people; part of IHI's QI Essentials and Patient Safety Essentials toolkits — IHI, Cause and Effect Diagram. Checked 21 October 2026.
- [9] 5 Whys attributed to Taiichi Ohno of the Toyota Production System; there may be multiple root causes — IHI, 5 Whys: Finding the Root Cause. Checked 21 October 2026.
- [10] Pareto chart orders contributing factors by the size of their effect; the vital few — IHI, Pareto Chart. Checked 21 October 2026.
- [11] FMEA as a systematic, proactive method for evaluating a process or product to identify where and how it might fail; useful before implementing a new process — IHI, Failure Modes and Effects Analysis (FMEA) Tool. Checked 21 October 2026.
- [12] Training "Taking Effective Corrective Action: Using the 8-D Approach"; CQI-20 Effective Problem Solving Guide, 2nd edition (August 2018) — Automotive Industry Action Group (AIAG), Problem Solving. Checked 21 October 2026.
- [13] A3 report pioneered by Toyota; A3 is a 297 × 420 mm sheet; problem and current condition on the left, countermeasures, action plan and follow-up on the right — Lean Enterprise Institute, Lean Lexicon: A3 Report. Checked 21 October 2026.
- [14] Fault tree analysis as a deductive, failure-based approach starting from an undesired top event; version 1.1, August 2002, prepared for the NASA Office of Safety and Mission Assurance — NASA, Fault Tree Handbook with Aerospace Applications (PDF). Checked 21 October 2026.
Build your root cause analysis presentation in NOXI, free: attach your RCA report and defect log, check the problem slide and the nine titles in Plan mode, and export an editable PowerPoint or a PDF.
