Skip to content

Failure Mode Anticipation

Identify how a design could fail before implementation and prioritize prevention or mitigation.

The Diagnostic Story

Symptom: Failure is treated as a generic risk until something specific breaks, at which point everyone recognizes they had seen the signal before. Risk conversations produce probability scores and broad reminders to be careful, but no one names the concrete ways each function could fail, who would detect it, or what would change in the design to prevent it. The same category of incident keeps returning after each launch or handoff.

Pivot: Before implementation, map functions, name specific failure modes and their causes, assess effect severity and how detectable each failure is, prioritize by risk, and assign prevention or mitigation actions — changing design or controls rather than issuing vigilance reminders.

Resolution: Serious design weaknesses surface early enough to fix, and accountability for residual risk is explicit. Downtime, preventable harm, and rework drop because the design changed rather than relying on attention. Past incidents and near misses feed forward into the next anticipation cycle.

Reach for this when you hear…

[manufacturing quality] “Before we release this to the line, I want someone to sit down and write out every way it can fail at step seven, not just the obvious ones.”

[software release] “We always talk about risk in the abstract — I need a list of what specifically breaks and how we'd even know it broke before a user tells us.”

[emergency planning] “The plan assumes communications stay up, power stays on, and the secondary route is clear — what happens when exactly two of those three are wrong at the same time?”

Mechanisms / Implementations

  • Failure Modes and Effects Analysis: failure_modes_and_effects_analysis — This is a method that can implement Failure Mode Anticipation.
  • Hazard Analysis: Enumerates the hazards a control leaves behind — including the ones it displaces — and holds each residual against an explicit tolerance rather than against whatever the current design happens to achieve.
  • Premortem Workshop: premortem_workshop — This is a ritual that can implement Failure Mode Anticipation.
  • Fault Tree Analysis: Decomposes a single system-level harm downward through logical gates until the transfer path — and the exact boundary where risk crosses out of the controlled unit — becomes explicit.
  • Risk Register: A living table of what could go wrong — each adverse event tagged with its likelihood, its impact, an owner, and the trigger that fires its response — so downside uncertainty stays visible and assigned instead of remembered by whoever happened to worry about it.
  • Safety Case: safety_case — This is a document that can implement Failure Mode Anticipation.
  • Design Review: design_review — This is a ritual that can implement Failure Mode Anticipation.
  • Failure Scenario Review: failure_scenario_review — This is a method that can implement Failure Mode Anticipation.
  • Incident Pattern Review: incident_pattern_review — This is a method that can implement Failure Mode Anticipation.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 11 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

FMEA-Style Failure Analysis · method family · recognized

Uses a structured failure-mode, effect, cause, scoring, and action record to anticipate design weaknesses before release or operation.

Hazard Path Analysis · subtype · recognized

Anticipates failures by tracing how a hazardous state could arise, what exposure paths it creates, and which barriers can interrupt the path.

Premortem Failure Anticipation · method family · recognized

Imagines that the solution has already failed, then reasons backward to plausible causes, warning signs, and preventive changes.

Operational Failure Mode Mapping · subtype · recognized

Maps how a workflow, service, or operating process can fail at handoffs, dependencies, staffing constraints, data flows, and exception paths.

Policy Failure Mode Anticipation · domain variant · recognized

Applies failure-mode anticipation to policy designs, administrative rules, incentives, enforcement paths, equity effects, and implementation constraints.