By Daniel Croft
FMEA is a structured way to think through how something could go wrong before it actually does. It helps teams identify potential failures in a process or design, understand the impact of those failures, and decide where to focus effort to reduce risk. In simple terms, FMEA asks: “If this fails, what happens, and how can we stop it?”
The core problem FMEA is designed to solve is unmanaged risk. Many defects, breakdowns, and customer complaints are predictable in hindsight. FMEA provides a practical way to surface those risks early, compare them consistently, and prioritise actions based on impact rather than gut feel or the loudest voice in the room.
Prevention vs. Detection
Detection is fixing a bug after you write the code.
Prevention is designing the architecture so that class of bug cannot exist. FMEA is purely focused on prevention.
Not Just a Quality Tool While FMEA started in engineering, it is effectively a universal risk management tool used today in software deployment, healthcare patient safety, and business operations.
Understanding the theory of FMEA is important, but execution is where most teams struggle. Using a structured FMEA template ensures Severity, Occurrence, and Detection are assessed consistently and that risks are prioritised objectively using RPN.
Implementing FMEA during the early design or process development phase is the single most effective way to ‘front-load’ quality. By systematically identifying failure points before production begins, you avoid the exponential costs associated with fixing defects later. The ‘1-10-100 Rule’ proves that a dollar spent on prevention during design saves $100 in warranty claims and recalls later. FMEA transforms your strategy from reactive firefighting to proactive profit protection.
The "1-10-100 Rule" states that catching a defect in design costs $10. Letting it reach the customer can cost $10,000. FMEA is your filter.
Michael Anleitner, a veteran in industrial engineering with 50 years of experiance, emphasizes that while FMEA can be labor-intensive, its value lies in identifying critical failure points and mitigating significant risks. He underscores the importance of appropriate scope, focusing on new, unique, or difficult (NUD) elements to ensure efficiency. Anleitner’s extensive experience, particularly in HVAC systems at Lennox, demonstrates that a well-scoped FMEA can uncover and address crucial issues, ultimately preventing costly failures and enhancing product reliability (Livonia Technical Services).
| Process Step / Function | Potential Failure Mode | Potential Effects | SEV | Potential Causes | OCC | Current Controls | DET | RPN | Recommended Action |
|---|---|---|---|---|---|---|---|---|---|
| 10. CNC Milling | Drill Bit Fracture | Product scrapped; Production line halt. | 8 | Tool fatigue; Incorrect feed rate. | 5 | Visual inspection | 6 | 240 | Install automated torque sensor. |
| 20. Heat Treatment | Temp below spec | Reduced part hardness; Early field failure. | 9 | Controller sensor drift. | 2 | Continuous temp logging | 3 | 54 | Calibrate sensor weekly. |
| 30. Final Assembly | Missing O-Ring | Customer leak; Warranty claim. | 7 | Operator error; Distraction. | 4 | Final visual check | 7 | 196 | Implement pick-to-light system. |
FMEA transforms subjective worry into objective data. Use the sliders below to see how the Risk Priority Number (RPN) changes based on the three core factors.
No discernible effect on customer or process.
Failure is extremely unlikely.
Error is certain to be caught before reaching customer.
Download the industry-standard FMEA Template. Includes auto-calculating RPN logic, conditional formatting, and example data.
Get the FMEA Template
System FMEA (SFMEA):
These three types of FMEA offer an approach to risk management at various stages of product development and system integration.
The complexity of most processes, products, or systems often means that no single person has a complete understanding of all aspects. Therefore, a cross-functional team brings together different perspectives and expertise, leading to a more complete analysis.
To ensure that the FMEA remains focused and manageable, it’s crucial to clearly define what will be analyzed. This prevents the process from becoming too broad or overlooking critical areas.
At this stage, the goal is to identify all the potential ways the subject (be it a process, product, or system) might fail. This is the foundation of the FMEA, as understanding these failure modes is key to addressing them.
This step aims to further break down each identified failure mode by understanding its impact, root causes, and existing preventive measures.
The aim here is to quantify the risk associated with each failure mode. These three criteria help in understanding the magnitude of the problem and in prioritizing corrective actions.
The Risk Priority Number (RPN) provides a numerical value that represents the overall risk of each failure mode. It helps in prioritizing which failure modes should be addressed first.
Calculate RPN: For each failure mode, multiply the Severity, Occurrence, and Detection ratings:
Prioritize: Once RPN values are calculated for all failure modes, sort them in descending order. Those with the highest RPNs should be given priority for corrective action since they represent the highest risk.
The aim of this step is to design and plan corrective actions for the identified failure modes, particularly those with the highest RPN values. Addressing these failure modes will have the most significant impact on improving the process or product.
Join our email list below and for the next 28 days, we will send you exclusive tools, templates and guides unavailable on the website. We developed a short and simple 28-day program designed to develop your ability to implement Lean and Six Sigma methods daily.
After developing action plans, this step ensures that the corrective measures are put into practice and that their effectiveness is monitored over time.
To support you with your FMEA implementation feel free to download our free FMEA template from the template section.
Case Study: Automotive Industry In a major automotive company, FMEA was applied to the manufacturing process of brake systems. The analysis identified potential failure modes, such as brake fluid leakage and sensor malfunction. By implementing corrective actions, the company reduced defect rates by 40% and enhanced product reliability, leading to a significant drop in warranty claims.
Case Study: Healthcare Sector A hospital used FMEA to improve the medication administration process. The team identified risks like incorrect dosage and administration delays. After addressing these risks, medication errors dropped by 25%, improving patient safety and care quality.
FMEA is a useful tool that allows businesses to identify, assess, and address potential failures in processes, products, or systems.
By systematically evaluating each failure mode’s severity, occurrence, and detection, teams can quantify risks and prioritize corrective actions. Our guide walked through the essential steps of FMEA, from assembling a cross-functional team to calculating the RPN. We also illustrated the process with a tangible example from the plastic water bottle manufacturing industry.
A: FMEA stands for Failure Mode and Effects Analysis.
A: FMEA is a systematic and proactive method used to identify and analyze potential failures, their causes, and their effects in a system, product, or process.
A: Using FMEA offers several benefits, including:
A: The key steps in conducting an FMEA are as follows:
A: The Risk Priority Number (RPN) is a numerical value calculated by multiplying the severity, occurrence, and detection rankings assigned to each failure mode during the FMEA process. It is used to prioritize failure modes for further analysis and action.
A: Yes, FMEA can be applied to various industries and fields, including manufacturing, healthcare, automotive, aerospace, software development, and many others. It is a versatile tool for risk assessment and mitigation.
A: Yes, there are different types of FMEA, including:
Daniel Croft-Bednarski is a Continuous Improvement Manager with a passion for Lean Six Sigma and continuous improvement. With years of experience in developing operational excellence, Daniel specializes in simplifying complex concepts and engaging teams to drive impactful changes.