This workshop guide expands the FMEA New Ideas pocket guide into a practical page for experienced quality professionals who want their FMEAs to identify more relevant risks and drive stronger prevention actions.
Overview
FMEA is one of quality's most important prevention tools, but many organizations use it poorly. Teams fill in spreadsheet cells, debate ratings, calculate RPNs, and produce documents that satisfy audits while missing the failure modes that later hurt customers.
The AIAG-VDA FMEA revision addressed several long-standing weaknesses: inconsistent process discipline, incomplete structure and function analysis, overreliance on RPN, and confusion between prevention and detection controls. This workshop helps participants apply those improvements and think more expansively about failure modes.
If your FMEA review never creates an 'I never thought of that' moment, the analysis probably did not go deep enough.
Who This Workshop Is For
Quality engineers, manufacturing engineers, design engineers, and process owners who already know FMEA basics.
Teams transitioning from traditional RPN-based FMEA to AIAG-VDA style thinking.
Organizations where FMEA exists mainly as an audit artifact.
Practitioners responsible for DFMEA, PFMEA, control plans, launch readiness, or risk reviews.
Leaders trying to prevent field failures, customer escapes, and high-severity risks.
Learning Objectives
Explain why traditional FMEAs often underperform.
Describe the AIAG-VDA seven-step approach at a practical level.
Use structure and function analysis to improve failure-mode completeness.
Explain the limitations of Risk Priority Number prioritization.
Apply the Action Priority concept to high-severity and high-risk items.
Distinguish prevention controls from detection controls.
Use boundary condition, use-abuse, similar-system, and DFMEA-PFMEA interface analysis to find missed failure modes.
Core Concept: Prevention, Not Paperwork
The goal of FMEA is prevention. A complete-looking document that does not change design, process, controls, or launch decisions has not done its job. The workshop repeatedly brings participants back to that purpose: what failure are we preventing, how do we know it could happen, and what action reduces the risk?
The AIAG-VDA concepts matter because they force better thinking before rating begins. Structure analysis asks what elements exist. Function analysis asks what each element must do. Failure analysis asks how those functions can fail. Risk analysis evaluates the seriousness and control strength. Optimization drives action.
RPN Limitations
Traditional RPN multiplies Severity, Occurrence, and Detection. That simplicity hides important risk differences. Different combinations can produce the same number while representing dramatically different risk profiles. Teams can also game ratings to keep RPNs below arbitrary thresholds.
The most dangerous failure is underweighting high-severity risks because occurrence appears low or detection appears strong. The Action Priority system addresses this by treating the interaction of Severity, Occurrence, and Detection more explicitly.
AIAG-VDA Improvements
The workshop introduces four practical improvements from AIAG-VDA style FMEA thinking: a disciplined seven-step approach, explicit structure and function analysis, Action Priority, and separation of prevention and detection controls.
Seven-Step Approach
Planning, structure analysis, function analysis, failure analysis, risk analysis, optimization, and results documentation.
Structure Analysis
A hierarchy of systems, subsystems, components, process steps, work elements, inputs, and interfaces.
Function Analysis
Clear verb-noun functions and measurable characteristics before failure modes are brainstormed.
Action Priority
Risk prioritization that avoids the false confidence and gaming problems of simple RPN thresholds.
Control Separation
Prevention controls reduce cause occurrence; detection controls find failures or causes after they occur.
Structure and Function Analysis
Many FMEAs miss failure modes because teams skip directly to failure brainstorming. If a function is not named, its failure mode is unlikely to be discovered. Structure and function analysis build a more complete inventory of what must work.
For DFMEA, the team maps the system, subsystems, components, and interfaces. For PFMEA, the team maps process steps, work elements, 4M/5M+E inputs, and produced characteristics. Functions should be written in precise verb-noun language such as seal fluid, locate component, transmit torque, verify barcode, or maintain temperature.
Expansive Failure-Mode Thinking
Even strong FMEA teams can miss failure modes because experience limits imagination. The workshop teaches four practical expansion techniques that help teams find risks they have never personally encountered.
Boundary Condition Analysis
Ask what happens at specification limits, environmental extremes, and worst-case interface combinations.
Use-Abuse Analysis
Study how customers actually use, misuse, maintain, install, and dispose of the product.
Similar System Mining
Search lessons learned, warranty, complaints, recalls, supplier issues, and prior FMEAs.
DFMEA-PFMEA Interface
Trace design characteristics into process steps and process assumptions back into design risk.
Workshop Flow
The source guide is intended for a 4-hour session. This flow assumes participants already understand basic FMEA columns and ratings.
0:00-0:20 Opening and FMEA Pain Points
Discuss why FMEAs become paperwork and what prevention should look like.
0:20-0:50 Rapid FMEA Refresher
Review function, failure mode, effect, cause, controls, Severity, Occurrence, Detection, and RPN.
0:50-1:20 RPN Limitations and AP
Compare equal RPNs with different risk profiles and introduce Action Priority logic.
1:20-2:00 Structure and Function Practice
Teams decompose a product or process and write measurable functions before identifying failures.
2:00-2:15 Break
Facilitator checks whether functions are precise enough to support analysis.
2:15-2:55 Expansion Techniques
Apply boundary, use-abuse, similar-system, and interface thinking to generate missed failure modes.
2:55-3:25 Prevention vs. Detection Controls
Classify controls and identify whether risk reduction needs prevention, detection, or both.
3:25-3:50 FMEA Improvement Plan
Teams identify one change to their current FMEA process and one high-risk area to revisit.
3:50-4:00 Commitment
Participants select one FMEA they will improve using the new method.
Facilitator Notes
Assume participants know basic FMEA, but do not assume they trust their current FMEA process.
Use examples where RPN produces misleading priority to make the AP conversation concrete.
Require clear functions before allowing failure modes. This is where FMEA quality improves.
Ask teams what evidence supports their ratings. Unsupported ratings are opinions with numbers attached.
Keep the purpose visible: the FMEA should change actions, controls, designs, or decisions.
Discussion Questions
Which AIAG-VDA steps were skipped or shortchanged in your last FMEA?
What field failure or customer escape might a more thorough FMEA have anticipated?
How does your organization handle Severity 9 or Severity 10 risks today?
Which expansion technique would generate the most value in your current work?
How would Action Priority change the priorities on your most recent FMEA?
What would it take to implement the full seven-step approach?
Participant Takeaways
FMEA exists to prevent failures, not to satisfy spreadsheet completion.
Structure and function analysis improve failure-mode completeness.
RPN can hide unacceptable risk; Action Priority gives more defensible prioritization.
Prevention and detection controls must be separated because they reduce different parts of risk.
Expansive thinking techniques help teams find failure modes experience alone would miss.
Related Learning Resources
Closing Message
The failures that will hurt customers tomorrow often already exist as latent design or process risks today. FMEA is the disciplined practice of finding them before the field does.
Better FMEA is not more paperwork. It is better prevention thinking, better evidence, and better action.