FMEA
Also known as: Failure Mode and Effects Analysis, FMECA, Process FMEA
A systematic method for identifying potential failure modes in a product, process, or system, analyzing their effects, and prioritizing actions to prevent or mitigate failures.
Quick Reference
Key Formula / Structure
RPN = Severity × Occurrence × Detection (each rated 1-10; max RPN = 1000)
Memory Aid
What could fail? (Mode) → How bad? (Severity) → How often? (Occurrence) → Can we catch it? (Detection) → Fix the worst first.
TL;DR
FMEA identifies potential failures in products or processes, scores them on Severity, Occurrence, and Detection (1-10 each), calculates a Risk Priority Number, and prioritizes corrective actions. Always prioritize high-severity items. Use cross-functional teams and update continuously.
What Is FMEA?
For each step in a process or component in a product, ask: 'What could fail? How bad is it? How likely is it? Can we detect it?' Then calculate a priority score and fix the highest-priority items first.
On Preventing Failure
Quality is not an act, it is a habit. FMEA embodies this by systematically building failure prevention into every design and process decision.
— Adapted from Aristotle, as applied to quality management by the AIAG FMEA Handbook (4th Edition)
FMEA systematically walks through each element of a process, product, or system to identify potential failure modes (what could go wrong), their effects (what happens if it fails), and their causes. Each failure mode is scored on three scales: Severity (how bad is the effect, 1-10), Occurrence (how likely is the cause, 1-10), and Detection (how likely are we to catch it before the customer, 1-10). The product of these three scores is the Risk Priority Number (RPN), which prioritizes corrective actions.
FMEA Scoring Matrix
The three scoring dimensions and their scales used to calculate the Risk Priority Number (RPN).
Origin & Context
Developed by the U.S. military to classify failures by their impact on mission success. Later adopted by NASA, automotive (AIAG), and manufacturing industries.
Core Components
Failure Mode
The specific way in which a process step or component could fail.
Example
Failure Mode: 'Customer address validation step fails to catch invalid postal codes.'
Severity (S)
Rating (1-10) of how serious the effect of the failure would be on the customer or downstream process.
Example
Severity: 8 — Invalid address causes order delivery failure, requiring customer service intervention.
Occurrence (O)
Rating (1-10) of how frequently the cause of the failure is likely to occur.
Example
Occurrence: 4 — Validation failures happen in approximately 1 in 1000 transactions.
Detection (D)
Rating (1-10) of how likely current controls are to detect the failure before it reaches the customer.
Example
Detection: 7 — Current controls catch only obvious errors; subtle invalid addresses pass through.
Risk Priority Number (RPN)
S × O × D score used to prioritize corrective actions. Higher RPN = higher priority.
Example
RPN: 8 × 4 × 7 = 224. Priority: High — implement improved address validation API.
Did You Know?
FMEA was originally developed by the U.S. military in 1949 (procedure MIL-P-1629), but it gained widespread recognition after NASA used it extensively during the Apollo program to ensure astronaut safety. After the Apollo 13 oxygen tank failure in 1970, NASA mandated even more rigorous FMEA processes. Today, FMEA is required by the automotive industry standard IATF 16949, making it mandatory for virtually all automotive suppliers worldwide.
When to Use FMEA
New product design
Problem it solves: Products launch with unknown failure modes that cause warranty claims and customer dissatisfaction.
Real-World Application
An automotive company conducts Design FMEA on a new braking system, identifying 47 potential failure modes and prioritizing 12 for redesign.
Process improvement
Problem it solves: Manufacturing or business processes have recurring quality issues.
Real-World Application
A pharmaceutical manufacturer uses Process FMEA to identify failure modes in their tablet coating process, reducing defect rates by 60%.
Software development
Problem it solves: Software systems have unidentified failure modes that cause outages.
Real-World Application
A fintech company conducts FMEA on their payment processing pipeline, identifying 23 failure modes and implementing monitoring and failover controls.
Focus on Severity First
Don't just chase the highest RPN. A failure with Severity 9 and low occurrence may be more important than one with a high RPN but low severity. Safety-critical failures always take priority.
How to Apply FMEA: Step by Step
Before You Start
- →Process map or product design documentation
- →Cross-functional team with relevant expertise
- →Historical failure and defect data
Scope and prepare
Define the process or product scope and assemble a cross-functional team.
Tips
- ✓Have the process map or design documentation available
- ✓Include people who work with the process daily
Common Mistakes
- ✗Scoping too broadly; FMEA works best on specific processes or components
Identify failure modes
For each step or component, brainstorm all the ways it could fail.
Tips
- ✓Ask 'What could go wrong?' at every step
- ✓Consider partial failures and degraded performance, not just complete failure
Common Mistakes
- ✗Only identifying complete failures; missing partial or intermittent failure modes
Score Severity, Occurrence, Detection
Rate each failure mode on the three 1-10 scales and calculate the RPN.
Tips
- ✓Use standardized rating scales for consistency
- ✓Reference historical data where available
Common Mistakes
- ✗Inconsistent scoring across team members; calibrate scales first
Prioritize and take action
Focus corrective actions on the highest-priority items (high RPN or high Severity).
Tips
- ✓Assign owners and deadlines for each action
- ✓Re-score after implementing actions to verify improvement
Common Mistakes
- ✗Completing the FMEA but never implementing corrective actions
Value & Outcomes
Primary Benefit
Systematically identifies and prioritizes potential failures before they occur, preventing quality issues and safety incidents.
Additional Benefits
- ✓Builds team knowledge of process/product vulnerabilities
- ✓Creates a documented knowledge base of failure modes
- ✓Satisfies quality management and regulatory requirements (ISO, IATF)
What You'll Learn
- →How to think systematically about failure modes
- →How to prioritize risk mitigation efforts
- →How to build prevention into designs and processes
Typical Outcomes
Best Practices
📋 Preparation
- •Gather historical failure and defect data before the session
- •Train the team on FMEA methodology and rating scales
🚀 Execution
- •Use a skilled facilitator to drive the FMEA session
- •Be thorough but time-box each process step
- •Challenge assumptions about detection capability
🔄 Follow-Up
- •Track corrective actions to completion
- •Re-score RPNs after actions are implemented
- •Update the FMEA when processes or designs change
💎 Pro Tips
- •The Detection score is often the most inflated — teams overestimate their ability to catch failures
- •Living FMEAs (continuously updated) are far more valuable than one-time exercises
FMEA is a team exercise, not a solo activity. The value comes from cross-functional perspectives identifying failures that no single person would see.
Toyota's Accelerator Pedal Recall
In 2009-2010, Toyota recalled over 9 million vehicles due to unintended acceleration issues linked to floor mat entrapment and sticky accelerator pedals. Post-incident analysis revealed that a more rigorous FMEA process could have identified the pedal mechanism failure mode earlier in design. Toyota subsequently overhauled its Design FMEA process, adding 'customer use environment' as a mandatory analysis factor and requiring that any failure mode with Severity 9 or 10 must have at least two independent preventive barriers — regardless of its RPN score.
Limitations & Pitfalls
RPN can be misleading — a 2×9×9 and 9×2×9 have the same RPN but very different risk profiles
Mitigation: Always consider Severity independently; never ignore high-severity items even with low RPN
Time-intensive for complex products or processes
Mitigation: Focus FMEA on critical-to-quality elements; not every minor step needs full analysis
Apply FMEA with Stratrix
Turn this framework into a professional strategy deck in under a minute. Stratrix applies FMEA automatically to your business context.
Try Stratrix Free