Story Framework
Failure Analysis
Walk through what went wrong, why, and what changes — a structured post-mortem for stakeholder reviews. Pairs honest accountability with a credible recovery plan.
Beat Diagram
- 1Opening Remarktext-1x / text
- 2Incident Breakdowntext-1x / text
- 3Impact Analysistext-1x / text
- 4Root Causetext-1x / text
- 5Proposed Solutionstext-1x / text
- 6Action Plantext-1x / text
- 7Evaluate Outcometext-1x / text
- 8Lessons Learnedtext-1x / text
- 9Preventive Measurestext-1x / text
- 10Closing Thoughtstitle / text
Use Failure Analysis in your next deck — for free
STORYD writes a presentation around your topic and applies Failure Analysis across every slide. No template hunting, no copy-paste.
Free, no card. Exports to PPTX.
OPF Config
narratives:failure-analysis{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "PPTX.gallery — narratives/failure-analysis",
"narrative": "failure-analysis",
"tags": [
"gallery:narratives/failure-analysis"
],
"slides": [
{
"id": "gallery-preview-1",
"layout": "title-slide",
"title": "Narrative preview",
"subtitle": "Storyline scaffolded by the \"failure-analysis\" narrative.",
"design": {
"contentBox": false,
"contentAlignment": "center",
"titleAlignment": "center"
}
}
]
}Preview this config live at pptx.dev/playground, or load it in the gallery visual editor.
Pace
15-45 minutes
10 beats
Audience Fit
Tags
Beat-by-Beat Guide
Opening Remark
Set an empathetic, accountable tone before any analysis. Acknowledge the impact on the people in the room and the customers affected. Authenticity here earns you the credibility you'll need for the rest of the deck.
Instruction: Set an empathetic tone
Incident Breakdown
Walk through what happened, in time order. Stick to facts: what systems, what users, what timeline. No causal claims yet — just an accurate, neutral reconstruction the audience can trust.
Instruction: Detail the failure
Impact Analysis
Quantify the damage. Customer-hours lost, revenue at risk, SLA breaches, downstream knock-ons. Be specific and direct; vague impact statements undermine the rest of the post-mortem.
Instruction: Describe failure's effects
Root Cause
Trace the failure to its underlying cause, not the most visible symptom. Use a 'five whys' or fishbone framing if useful. Distinguish between the proximate trigger and the systemic conditions that allowed it.
Instruction: Analyze underlying reasons
Proposed Solutions
Present the corrective actions you're taking. Lead with the highest-leverage fix; sequence the rest. For each action, name an owner and a date — solutions without owners are aspirations.
Instruction: Suggest corrective measures
Action Plan
Lay out the rollout: what ships when, how it's verified, who signs off. Show that 'fixed' has a definition and a deadline, not just intent.
Instruction: Map out steps
Evaluate Outcome
Define the metrics that will tell you the fix worked. Pre/post comparisons, monitoring SLOs, error budgets — whatever proves the failure mode is closed and not just deferred.
Instruction: Assess corrective actions
Lessons Learned
Distill the broader lessons that outlive this specific incident. What does the team or organization now know that it didn't before? What patterns will you watch for elsewhere?
Instruction: Reflect on failure lessons
Preventive Measures
List the systemic safeguards being added — process changes, automated checks, on-call procedures, review gates. Show how this category of failure becomes harder to recur, not just this specific instance.
Instruction: List safeguards
Closing Thoughts
Close with humility and forward momentum. Re-affirm accountability, thank the audience for their patience, and signal confidence in the path forward without overclaiming.
Instruction: Empathize, trust, and encourage