In my experience, the average FMEA lives in one of two states: it's either being frantically updated the week before a customer audit, or it hasn't been opened since the product launched. Neither is acceptable. Both are common.
The Failure Mode and Effects Analysis is one of the most powerful tools in a quality engineer's kit — a structured, proactive method for identifying what could go wrong, how bad it would be, and what you're doing about it. When built and maintained well, an FMEA is a living risk register that guides design reviews, informs control plans, and protects customers. When treated as a compliance checkbox, it's expensive paperwork.
"An FMEA that sits on a shelf isn't risk management. It's documentation theater."
Why FMEAs Become Shelf Documents
There are consistent reasons why FMEAs lose their usefulness after launch:
- They were built by one engineer in isolation, without input from production, maintenance, or the customer-facing team
- The RPN (Risk Priority Number) scoring was rushed or politically influenced to avoid triggering action items
- There's no defined owner and no process for keeping it updated when the process changes
- It's so long and complex that nobody wants to open it
- The recommended actions were never completed — they live in the document as "planned" indefinitely
Building an FMEA That Stays Alive
1. Build It With the Right Team in the Room
The most valuable FMEA insights don't come from the quality engineer — they come from the people who live with the process every day. Operators know which step always requires a second attempt. Maintenance knows which component fails first. The shipping team knows which packaging configuration gets damaged in transit.
A cross-functional FMEA session with 4–6 people who touch the process will surface failure modes that a solo engineer would never identify. Schedule it as a working session, not a review meeting. Bring a facilitator, a whiteboard, and the process flow diagram.
2. Be Honest About RPN Scoring
Risk Priority Numbers lose all value when teams game the scoring to avoid action items. If a failure mode has a Severity of 9 but the team rates Detection at 1 to bring the RPN below the threshold — that's not analysis, that's avoidance.
A better approach: separate your response logic from the RPN. Any failure mode with a Severity of 9 or 10 deserves a mitigation conversation regardless of the calculated RPN. Severity is not negotiable; it reflects the worst-case impact on the customer or end user.
Don't let teams focus exclusively on RPN thresholds. A failure mode with Severity=10, Occurrence=1, Detection=1 has an RPN of 10 — but it represents a catastrophic risk that deserves a serious conversation. Always review high-severity items regardless of RPN.
3. Connect the FMEA to Your Control Plan
The FMEA and the Control Plan should be siblings, not strangers. Every high-risk failure mode in the FMEA should have a corresponding control in the Control Plan. If the FMEA identifies "incorrect torque application" as a failure mode with high severity, the Control Plan should specify exactly how torque is verified, at what frequency, and by whom.
When the two documents are aligned, an operator following the Control Plan is automatically executing the risk mitigations identified in the FMEA. That's the system working as designed.
4. Define a Living Document Process
Every FMEA needs a designated owner and a defined trigger list for updates. At minimum, the FMEA should be reviewed and updated when:
- A new defect or field failure occurs that wasn't previously identified
- The process, material, or equipment changes
- A customer complaint reveals a failure mode that was missed or underscored
- An annual scheduled review is due
The review doesn't have to be a lengthy event. A 30-minute session with the process owner, a quality representative, and the operator is enough to confirm whether the document still reflects reality.
5. Keep It Readable
An FMEA with 400 rows and 22 columns is not a useful tool — it's a monument to process complexity. Consider breaking large FMEAs into sub-system documents. Use color coding to make high-RPN items immediately visible. Put the most critical failure modes on the first page. The goal is a document that an engineer can open, navigate, and act on in under five minutes.
Closing the Loop: From FMEA to Prevention
The ultimate purpose of an FMEA is prevention — stopping failures before they reach customers. That only happens when the recommended actions are completed, verified, and reflected in updated standard work and control plans. Track open action items from the FMEA in your standard corrective action system. Review them in your quality meetings. Close them with evidence.
The FMEA is only as valuable as the actions it generates. A document full of "planned" recommendations that never get implemented is worse than no FMEA at all — it creates false confidence that the risks are managed when they aren't.
— Scott Hacker, MBA | Quality & CI Manager | Kansas City, MO