Failure Mode and Effects Analysis (FMEA) is a structured risk method for identifying how a product, process, or system can fail, evaluating effects and causes, and prioritizing prevention or detection actions.
Definition
Failure Mode and Effects Analysis (FMEA) is a structured method for anticipating failure before it reaches the customer, user, patient, process, or next operation. It identifies functions, possible failure modes, effects, causes, current controls, risk ratings, and actions to reduce risk.
FMEA is prevention-oriented. The value is not the form itself; the value is the cross-functional thinking that improves design, process controls, mistake proofing, detection, validation, and response before failure becomes expensive or harmful.
History
FMEA originated in high-reliability fields such as military, aerospace, and nuclear applications, then spread into automotive, medical device, manufacturing, service, and quality-management systems. Automotive quality planning made Design FMEA and Process FMEA especially common.
Modern FMEA practice includes traditional RPN scoring, severity/occurrence/detection thinking, and AIAG/VDA-style Action Priority. Organizations adapt the format, but the core logic remains: identify risk early and reduce it systematically.
When to Use
Use FMEA for new products, new processes, design changes, process changes, customer complaints, recurring defects, supplier risks, safety-critical work, regulatory-sensitive processes, and launch planning. It is especially useful when failure effects are severe, detection is difficult, or prevention controls are weak.
FMEA should be started early enough to influence design and process decisions. A late FMEA used only to satisfy documentation requirements usually has little practical value.
Step-by-Step
- Define scope. Clarify whether the FMEA covers design, process, equipment, service, software, supplier, or system risk.
- Build the team. Include people from design, process, production, quality, maintenance, supplier, customer, safety, and service where relevant.
- List functions or steps. Define what each design element or process step is supposed to do.
- Identify failure modes. Ask how each function or step could fail to meet requirements.
- Describe effects. Capture the impact on customer, safety, compliance, next operation, cost, delivery, or field performance.
- Identify causes. Determine why the failure could occur, including design weakness, process variation, human factors, material, method, equipment, or environment.
- Review current controls. Separate prevention controls from detection controls.
- Prioritize risk. Use severity, occurrence, detection, RPN, Action Priority, or local risk rules.
- Assign actions. Reduce risk through design changes, error proofing, process controls, validation, training, standard work, or improved detection.
- Verify and update. Confirm actions are complete and revise risk ratings based on evidence.
Examples
- Design FMEA: Engineers identify that a component could crack under vibration and add design changes plus durability validation.
- Process FMEA: A team identifies that an assembly part can be installed backward and adds poka-yoke fixturing.
- Service FMEA: A claims process identifies missing documentation as a failure mode and adds intake validation.
- Supplier FMEA: A launch team reviews supplier process risks before approving production parts.
- Maintenance FMEA: A team identifies failure modes in a critical pump system and improves inspection and spare-parts strategy.
Common Pitfalls
- Filling out the form after decisions are made. FMEA must influence design and controls early.
- Vague failure modes. Generic entries like "bad quality" do not guide prevention.
- Confusing effects, modes, and causes. Clear structure improves action quality.
- Over-focusing on RPN. Severity and action priority matter; RPN alone can hide serious risks.
- No action follow-through. Risk is not reduced until actions are implemented and verified.
- No linkage to control plan. Important process risks should flow into controls, checks, and reaction plans.