What Is FMEA? Definition and Uses

FMEA — failure mode and effects analysis — is a structured method for anticipating what could go wrong with a process or product, and fixing the worst of it before it happens. A team lists every plausible failure, traces its effects, scores its risk, and works down the list in order. Developed for American military and aerospace programs in the mid-twentieth century and later made standard practice across the automotive industry, FMEA turns vague worry into a ranked work plan.

How it works

A cross-functional team walks the process step by step and asks three questions at each one: what could fail here, what happens downstream if it does, and what causes it. Each failure mode is then scored on three 1-to-10 scales — severity of the effect, likelihood of occurrence, and how reliably current controls would detect it before the customer is affected. Multiplying the three produces a risk priority number, and the table is sorted so the biggest risks rise to the top.

The scoring is only half the method. For the highest-ranked failures, the team assigns actions — redesign the step, add a control, mistake-proof the operation — each with an owner and a date. Once an action lands, the failure is re-scored to confirm the risk actually moved. A living FMEA is revisited whenever the process changes; a dead one gets laminated and hung by the door.

An illustration: the mail-order pharmacy

Imagine a mail-order pharmacy mapping its dispensing process. One failure mode: the right drug shipped at the wrong strength. Severity scores 9 — the effect on a patient could be serious. Occurrence scores 3, because software checks catch most slips. Detection scores 4; the final visual check is good but not infallible. The risk priority number is 9 × 3 × 4 = 108. Compare a smudged shipping label: severity 4, occurrence 5, detection 2, for a product of 40. Both are real problems, but the numbers say where the engineering hours go first — and the severity 9 would demand attention even if its total were lower.

• Score as a team — a lone engineer’s ratings inherit a lone engineer’s blind spots
• Write failure modes specifically; “label error” hides three different failures with three different causes
• Never let a modest total excuse a severity 9 or 10
• Re-score after every corrective action, or the document rots
• Treat the FMEA as a living file, reopened whenever the process changes

An FMEA is pessimism with a schedule — every fear written down, scored, and assigned a fix.

FMEA sits in the core toolkit of our Green Belt program — $299, about 35 hours, ending in a 100-question proctored exam — where you build one against a simulated process. Black Belt training extends the method into design work and ties it to the control plans that keep improvements from unravelling.