Operations Analysis method

Failure Mode and Effects Analysis

Examines possible failure modes, effects, and causes and prioritizes actions for later effectiveness checks.

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

Core question

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

Plan Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 3-10 participants
Time: Multiple work sessions; verify actions after implementation

Paper illustration for Failure Mode and Effects Analysis

Functions
Functions
Clarify system boundary and functions; record possible failure modes and effects for affected users.
Controls
Causes and controls
Name potential causes and current prevention and detection controls.
Rating
S, O, D and RPN
S = severity, O = occurrence, D = poor detectability; RPN = S × O × D. Anchor scales beforehand.
Actions
Actions
Prefer preventing causes, then improve detection; agree owner, date and evidence.
Effectiveness
Effectiveness
Evidence implementation and effect; reassess S/O/D and record remaining needs.

After verified action implementation, reassess S, O and D with rationale; update the FMEA after changes.

A good fit when

For concrete products, processes or services with known functions and cross-functional knowledge.

Ideal for

Quality Planning
Safety-critical Processes
Operational Risk

Not good for

Early open ideation
Risks without an assessable process

Outputs

FMEA risk register
FMEA matrix with function, failure mode, effect, cause, controls, S/O/D, RPN, and actions with effectiveness evidence.
Verified residual state
The record preserves before and after assessments separately and states the next review date.

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 chain	Function	Failure mode	Effect	Cause	Current controls	S	O	D	RPN	Action / owner	Evidence / residual rating
1Enter function, failure chain, current controls and justified ratings; distinguish actions and evidence.	Send confirmation	No confirmation	Participants unsure of status	Transient sending failure without retry	Prevention: none. Detection: log entry without alert.	6	4	7	168	Jan by Friday: add queue retry and alert.	Fictionally after test and operational observation: S6/O2/D3 = 36; severity unchanged.

1. Function
1
Send confirmation
2. Failure mode
1
No confirmation
3. Effect
1
Participants unsure of status
4. Cause
1
Transient sending failure without retry
5. Current controls
1
Prevention: none. Detection: log entry without alert.
6. S
1
6
7. O
1
4
8. D
1
7
9. RPN
1
168
10. Action / owner
1
Jan by Friday: add queue retry and alert.
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

First step

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

Open the method guide

Good to do first

Operations

Process Mapping

Supplies the sequence of functions checked for failure modes.

Where to go next?

Decision Making

Risk Matrix

Carries the verified residual risk into an ongoing risk overview.

Operations

Kaizen Event

Implements risk-reducing measures in a focused improvement workshop.

Deep dive

Purpose

For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.

How it works

Every potential failure is considered together with its effect and its impact in the process context. This creates a distinction between harmless weaknesses and critical high-priority vulnerabilities. The review makes prevention plannable before real damage occurs.

In detail

FMEA thinks through possible failure modes before damage occurs and prioritizes them by risk. Concrete functions, realistic causes, existing controls, and traceable assessment of severity, occurrence, and detection are decisive. The table has value when design, process, or control actually get improved.

Facilitation

At the start, function, failure boundary, and the rating scales for severity, occurrence, and detection must be jointly understood. The real value shows when high risks are recognized not from individual scores but from problematic combinations. Close with preventive measures for the most critical cases and clear responsibility for following up on them.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Risk Quality Operations Root cause

Sources

ASQ: FMEAasq.orgProfessional society: functional failure, effects, causes, controls and actions. Example scores are editorial teaching values, not a standard scale.

In playbooks

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

Artifact templates

Failure Mode and Effects Analysis: WorksheetDefine scope, functions and agreed rating rules; prepare existing controls and failure data.

markdown

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 chain	Function	Failure mode	Effect	Cause	Current controls	S	O	D	RPN	Action / owner	Evidence / 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