methodatlas
Engineering

Failure Scenario Analysis

Turns technical problems, hypotheses, and next steps into a tangible result by defining the system or process, collecting plausible failure scenarios, and deriving tests, prevention, and response.

Core question
How could the system plausibly fail, what would that impact be, and which controls are missing?
MediumWorkshop1-3 h
Open runsheetPlan sessionStart comparison
Purpose

The method helps clarify technical problems, hypotheses, and next steps in a concrete way. It breaks a technical problem into testable parts. The result is captured as failure scenarios, risk notes, and control gaps.

How it works

The team follows the steps: define the system or process boundary, collect plausible failure scenarios, analyze triggers and effects, assess controls and gaps, and derive tests, prevention, and response. Each step is captured visibly. At the end, failure scenarios, risk notes, and control gaps are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Failure Scenario AnalysisPlausible Ausfälle als Szenarien mit Auslösern, Auswirkungen, Kontrollen, Lücken und Response-Tests modellieren
Failure Scenario AnalysisDas Visual zeigt ein abgegrenztes System, einen plausiblen Ausfallpfad mit Auslöser, Ausfall und Impact sowie Kontrollen, Lücken und Response-Test.Plausible Ausfälle als prüfbare Szenarien vorbereitenDie Analyse macht sichtbar, wie ein System scheitern könnte, welche Kontrollen wirken und welche Response geprobt werden muss.konkrete GeschichteKontrollen und Lücken sichtbar machenSystemgrenzekritischer Prozess oderReleaseFailure Scenariorealistischer AusfallpfadAuslöserLastspitzeAusfallQueue läuft vollImpactCheckout blockiertKontrolleAutoscaling und AlarmLückeRunbook fehltResponse-TestGame Day oder Probealarm planen

Flow

  1. 1Define the system or process boundary
  2. 2Collect plausible failure scenarios
  3. 3Analyze triggers and effects
  4. 4Assess controls and gaps
  5. 5Derive tests, prevention, and response

The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Resilience planning
  • Architecture and operational risks
  • Release readiness

Not good for

  • Already occurred incidents without reconstruction
  • Pure creative ideas
  • Trivial single tasks

Deep dive

In detail

Failure Scenario Analysis starts by asking which realistic failure situations a system or process could face. For each scenario, the team looks at triggers, affected components, escalation paths, impacts, and existing controls. That turns failure from an abstract idea into a testable story. The scenarios then become tests, prevention measures, and response plans.

Facilitation

Use real incidents, architecture knowledge, and operational data as a starting point. Keep scenarios concrete enough for teams to derive actions. Do not focus only on spectacular outages; also look at frequent small disruptions with high total impact.

Output artifacts
Failure ScenariosRisk NotesControl GapsTest and Response Actions
Tags
failureresiliencerisk

Sources

Google SRE - Incident Response with Google's Strategiessre.googleFailure mode and effects analysis - Wikipediaen.wikipedia.org
Artifact templates
Failure Scenario Analysis Working TemplateCompact working template for Failure Scenario Analysis with context, input, output artifacts, and next step.
markdown

failure-scenario-analysis-working-template.md

Compact working template for Failure Scenario Analysis with context, input, output artifacts, and next step.

Failure Scenario Analysis Working Template

Goal

Analyzes plausible failure scenarios to prepare weak points, controls, and response options.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Failure Scenarios:
  • Risk Notes:
  • Control Gaps:
  • Test and Response Actions:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Fault Tree Analysis

Statt Failure Scenario Analysis, wenn du einen Ausfall top-down über logische Verknüpfungen und Fehlerpfade zerlegen willst.

Red Teaming

Statt Failure Scenario Analysis, wenn du eine Lösung gezielt aus adversarialer Sicht auf Schwachstellen prüfen willst.

Similar methods

All methods
Product Discovery
Assumption Mapping

Turns customer problems, solution ideas, and evidence into a tangible result through collecting assumptions, rating importance, and planning tests.

Engineering
Fault Isolation

Turns technical problems, hypotheses, and next steps into a tangible result by clarifying the symptom and system boundaries, breaking the fault space into areas, and narrowing the affected area.

Engineering
Goal Question Metric

Moves technical problems, hypotheses, and next steps toward a concrete result through "formulate the goal clearly", "derive probing questions for each goal", and "set the review cadence".

Engineering
Golden Path

Turns technical problems, hypotheses, and next steps into a tangible result by choosing a common use case, describing a best-practice path, and integrating feedback and exceptions.

Engineering
Hypothesis-Driven Troubleshooting

Turns technical problems, hypotheses, and next steps into a tangible result by collecting symptoms, formulating hypotheses, and refining them through testing.

Engineering
Kanban

Turns technical problems, assumptions, and next steps into a tangible result through mapping the workflow, making work visible, and improving bottlenecks.