methodatlas
Method guideOperations

Failure Mode and Effects Analysis

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityHigh
Time2-6 h
Participants3-10
FormatWorkshop
MaturityCanonical
Plan
01

Prerequisite

What needs to be finished first

Complete firstFunctions and scales

Functions, effects and organisation-specific S/O/D scales are jointly understood.

Example ratings are not an approved industry scale.
02

Preparation

What needs to be ready before start

Materials

FMEA table, function flow, failure data and anchored S/O/D rating scales.

People / roles

Cross-functional team covering design, operations, quality and affected users.

Pre-read

Define scope, functions and agreed rating rules; prepare existing controls and failure data.

Time needed

Multiple work sessions; verify actions after implementation

Setup

Create one row per failure chain; display rating legend and current controls, keeping planned actions separate.

03

Core question

The one question this method answers

How can a function fail, what effects follow and which actions demonstrably reduce risk?

04

Flow

Phases with goal, actions, output and pitfall

FMEA proactively examines functions for failure modes, effects and causes. Existing prevention and detection controls are assessed; prioritised improvements are implemented and then reassessed.

Failure Mode and Effects Analysis· worksheet

Fictional example

FMEA proactively examines functions for failure modes, effects and causes. Existing prevention and detection controls are assessed; prioritised improvements are implemented and then reassessed.

Failure Mode and Effects Analysis· worksheet
Failure chainFunctionFailure modeEffectCauseCurrent controlsSODRPNAction / ownerEvidence / residual rating
1Enter function, failure chain, current controls and justified ratings; distinguish actions and evidence.Send confirmationNo confirmationParticipants unsure of statusTransient sending failure without retryPrevention: none. Detection: log entry without alert.647168Jan by Friday: add queue retry and alert.Fictionally after test and operational observation: S6/O2/D3 = 36; severity unchanged.

  1. 1. Function

    1
    Send confirmation

  2. 2. Failure mode

    1
    No confirmation

  3. 3. Effect

    1
    Participants unsure of status

  4. 4. Cause

    1
    Transient sending failure without retry

  5. 5. Current controls

    1
    Prevention: none. Detection: log entry without alert.

  6. 6. S

    1
    6

  7. 7. O

    1
    4

  8. 8. D

    1
    7

  9. 9. RPN

    1
    168

  10. 10. Action / owner

    1
    Jan by Friday: add queue retry and alert.

  11. 11. Evidence / residual rating

    1
    Fictionally after test and operational observation: S6/O2/D3 = 36; severity unchanged.

Fictional teaching ratings, scale 1–10: higher is worse. S6 significant service disruption; O4 occasional, O2 rare; D7 weak detection, D3 reliable alerting in tests. 6 × 4 × 7 = 168; after verified action 6 × 2 × 3 = 36.

ASQ: FMEA

  1. 1

    Functions

    Functions

    Goal

    Failure chains

    Inputs for this step

    • Functions
    • Requirements

    Actions

    • Clarify system boundary and functions; record possible failure modes and effects for affected users.
    • Keep mode, effect and cause in separate fields.

    Output

    Failure chains

    Are failure mode and effect distinct?

    Quality check

    Are failure mode and effect distinct?

    Pitfall

    Everything is bundled as technical failure. Name loss of function and concrete effect separately.

    Timing: 20–40 minutes

  2. 2

    Controls

    Causes and controls

    Goal

    Control picture

    Inputs for this step

    • Failure chains
    • Existing controls

    Actions

    • Name potential causes and current prevention and detection controls.
    • Separate effective existing controls from planned actions.

    Output

    Control picture

    Do controls exist and work today?

    Quality check

    Do controls exist and work today?

    Pitfall

    Planned controls already lower initial ratings. Assess the baseline before actions.

    Timing: 20–40 minutes

  3. 3

    Rating

    S, O, D and RPN

    Goal

    Reasoned priority

    Inputs for this step

    • Controls
    • Rating rules

    Actions

    • S = severity, O = occurrence, D = poor detectability; RPN = S × O × D. Anchor scales beforehand.
    • Prioritise high severity independently of the product and justify ratings.

    Output

    Reasoned priority

    Does high D mean poor detection?

    Quality check

    Does high D mean poor detection?

    Pitfall

    RPN is treated as a precise probability. State ordinal scoring and data uncertainty.

    Timing: 20–40 minutes

  4. 4

    Actions

    Actions

    Goal

    Action plan

    Inputs for this step

    • Prioritised risks
    • Resources

    Actions

    • Prefer preventing causes, then improve detection; agree owner, date and evidence.
    • Severity falls only when the actual effect changes.

    Output

    Action plan

    Does the action change a specific risk driver?

    Quality check

    Does the action change a specific risk driver?

    Pitfall

    An extra check is assumed to lower S. Rate detection effects under D; retain S when effects are unchanged.

    Timing: 15–30 minutes

  5. 5

    Effectiveness

    Effectiveness

    Goal

    Verified residual state

    Inputs for this step

    • Implemented actions
    • Evidence

    Actions

    • Evidence implementation and effect; reassess S/O/D and record remaining needs.
    • Preserve before and after separately and schedule review.

    Output

    Verified residual state

    Is reassessment based on evidence?

    Quality check

    Is reassessment based on evidence?

    Pitfall

    New low scores replace evidence of effectiveness. Require tests or operating data; keep residual scoring open until then.

    Timing: 15–30 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

FMEA · Failure Mode & EffectsFehlermodi mit Schwere, Auftreten und Entdeckbarkeit bewerten, priorisieren und Maßnahmen ableiten
FMEADas Visual zeigt Failure Modes, S-O-D-Bewertung, Risk Priority Number, Maßnahmen und Re-Scoring.Fehlermodi priorisieren, bevor sie auftretenSchwere, Auftreten und Entdeckbarkeit machen Risiken vergleichbar und führen zu gezielten Gegenmaßnahmen.bewertenTop-RisikosenkenScopeProzess oder ProduktgrenzeFailure Mode and Effects AnalysisFailure ModeSODRPNDatenverlust934108Latenz-Spike65390Falsch-Negativ846192MaßnahmenOwner, Termin und WirkungprüfenRe-ScoreRPN nach Maßnahme neu bewerten
Form

FMEA matrix with function, failure mode, effect, cause, controls, S/O/D, RPN and actions with effectiveness evidence.

Versioning / ownership

Record date and scope; retain the previous version and reason when changing it.

Tool alternatives
  • FMEA spreadsheet
  • Quality-management system
  • Facilitated risk register

fmea-working-template.md

Define scope, functions and agreed rating rules; prepare existing controls and failure data.

Failure Mode and Effects Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete cycle Time: Multiple work sessions; verify actions after implementation

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: FMEA table, function flow, failure data and anchored S/O/D rating scales.
  • Roles: Cross-functional team covering design, operations, quality and affected users.
  • Advance information: Define scope, functions and agreed rating rules; prepare existing controls and failure data.
  • Overall time needed: Multiple work sessions; verify actions after implementation
  • Setup: Create one row per failure chain; display rating legend and current controls, keeping planned actions separate.

Prepare for the work steps

Functions: Functions

  • Functions
  • Requirements

Controls: Causes and controls

  • Failure chains
  • Existing controls

Rating: S, O, D and RPN

  • Controls
  • Rating rules

Actions: Actions

  • Prioritised risks
  • Resources

Effectiveness: Effectiveness

  • Implemented actions
  • Evidence

Failure Mode and Effects Analysis· worksheet

Failure chainFunctionFailure modeEffectCauseCurrent controlsSODRPNAction / ownerEvidence / residual rating
1
  • 1: Enter function, failure chain, current controls and justified ratings; distinguish actions and evidence.

Define your own rating anchors first. S = severity, O = occurrence, D = poor detectability; RPN = S × O × D. Examine high severity separately; no universal RPN acceptance threshold. Reassess only after effectiveness evidence.

ASQ: FMEA

Functions: Functions

Expected artifact: Failure chains

Are failure mode and effect distinct?

Entry:

...

  • Are failure mode and effect distinct?

Controls: Causes and controls

Expected artifact: Control picture

Do controls exist and work today?

Entry:

...

  • Do controls exist and work today?

Rating: S, O, D and RPN

Expected artifact: Reasoned priority

Does high D mean poor detection?

Entry:

...

  • Does high D mean poor detection?

Actions: Actions

Expected artifact: Action plan

Does the action change a specific risk driver?

Entry:

...

  • Does the action change a specific risk driver?

Effectiveness: Effectiveness

Expected artifact: Verified residual state

Is reassessment based on evidence?

Entry:

...

  • Is reassessment based on evidence?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/fmea/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

fmea-beispiel.md

Concrete filled scenario, fictional example

Fictional example

Function and scale: Fictional: send course confirmation. Teaching scale 1–10, higher = worse; S6 substantial service disruption, O4 occasional, D7 weak detection before customer contact.

Failure chain and controls: Mode: no confirmation. Effect: participants do not know their status. Cause: transient sending failure without retry. Control: simple log entry, no active alert.

Initial assessment: S6 × O4 × D7 = 168. The product supports prioritisation but does not replace examining each factor.

Action: Jan adds queue retries and missing-confirmation alerts by Friday; test with simulated sending failure.

Reassessment: Fictionally after a passed failure test and operational observation: S6 unchanged, O2, D3; RPN 36. In real use, reassess only after evidence.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. FunctionsEverything is bundled as technical failure.View in phase
  2. Causes and controlsPlanned controls already lower initial ratings.View in phase
  3. S, O, D and RPNRPN is treated as a precise probability.View in phase
  4. ActionsAn extra check is assumed to lower S.View in phase
  5. EffectivenessNew low scores replace evidence of effectiveness.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

RPN alone is insufficient: address high severity separately. Equal products can conceal different risks; assume no universal acceptance threshold.

Method after U.S. Military. FMEA was formalized in military and later industrial quality contexts. Curated with 1 sources.

Sources: ASQ: FMEA

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix

Carries the verified residual risk into an ongoing risk overview.

Paper illustration for Kaizen Event.
Operations
Kaizen Event

Implements risk-reducing measures in a focused improvement workshop.

View in playbookSystematically Solve a Recurring Operations ProblemMove from direct on-site observation through a structured DMAIC treatment to a new, anchored standard.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods