Why Your FMEA Should Fail on Paper Before Anything Fails in the Field
A Failure Mode and Effects Analysis is supposed to be the cheapest failure you will ever have. You gather the people who know the process, you imagine every way it can break, and you decide what to do about the worst risks — all before a single customer is affected. Done well, it is one of the most useful tools in the Lean Six Sigma kit. Done badly, it is a spreadsheet nobody reads twice.
After two years of disrupted supply lines and teams scattered across home offices, a lot of organizations rebuilt processes in a hurry. FMEA is exactly the discipline that catches what the scramble missed — but only if you avoid the traps that quietly drain it of value.
The mistakes that hollow out an FMEA
Treating it as a deliverable, not a working session. The value is in the conversation among people who actually run the process — an operator, an engineer, a customer-facing voice. When one person fills in the template alone to satisfy an auditor, you get tidy paperwork and zero new insight.
Confusing failure modes with causes or effects. The failure mode is how the step fails (the seal leaks). The cause is why (wrong torque spec). The effect is what the customer feels (product arrives empty). Mixing these three collapses the whole logic and makes the scores meaningless.
Gaming the RPN. Risk Priority Number is severity times occurrence times detection. Teams quickly learn they can lower a number by nudging a rating, so the action list looks short. You are not managing risk then — you are managing the appearance of it.
Letting detection do all the work. A high detection rating feels reassuring, but catching a defect late is not the same as preventing it. A failure that is severe and frequent deserves attention even if you are confident you will spot it.
Writing it once and shelving it. Processes drift. A new supplier, a remote handoff, a changed material — each can introduce a failure mode the original analysis never saw. An FMEA that is never revisited is describing a process that no longer exists.
How to keep it honest
Start from the process map, not a blank template, so every step is accounted for. Rate severity, occurrence, and detection against agreed definitions written down in advance, so the numbers mean the same thing to everyone in the room. Treat the RPN as a conversation-starter rather than a verdict — a high severity alone can justify action regardless of the product.
Anchor every rating to a published scale, not gut feel in the moment.
Assign each high-priority action to a named owner with a date — an FMEA with no action plan is a list of worries.
Re-score after the fix and confirm the risk actually moved, rather than assuming it did.
Revisit the analysis whenever the process, supplier, or environment changes.
The point is never to produce a perfect document. It is to spend an hour failing on paper so you do not spend a month failing in front of a customer. That trade is almost always worth making.
When the stakes are high and the process is new, a facilitated risk review pays for itself many times over — XNM's strategic advisory can help your team run an FMEA that actually changes what you do next.