FMEA (Failure Mode and Effects Analysis) is a super-tool for a team, especially when developing concepts and requirements. Done early, iteratively, and treated as a "living" analysis helps teams throughout development and beyond.
Some people seem to either love it or hate it. I don't have a strong reaction like that, but I do think it can be a valuable option for teamwork and design - so much so that I've dedicated a few episodes to it (including this one). We touch on some of the objections to it, too.
FMEAs can have different focuses and can be built to suit the goals of the team. There are two FMEAs, in particular, that can be done in the early concept stages of development: “use” UFMEA and “systems design” DFMEA.
Visit the blog post for a VENN Diagram and additional info.
Visit these other blogs to explore these topics further:
Getting Started with FMEA: It All Begins with a Plan
Choosing a Confidence Level for Test using FMEA
Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds.
Prevention Controls vs. Detection Controls
The Designer's Risk Analysis affects Business, Projects, and Suppliers
A big failure and too many causes? Try this analysis. (FTA)
DISCOVER YOUR PRODUCT DEVELOPMENT FOCUS: UNLOCK YOUR IMPACT
Take this quick quiz to cut through the 'design fog' and discover where your greatest potential lies
BI-WEEKLY EPISODES
Subscribe to this show on your favorite provider and Give us a Rating & Review to help others find us!
SELF-PACED COURSE FMEA in Practice: from Plan to Risk-Based Decision Making is enrolling students now. Join over 300 students: Click Here.
MONTHLY DIGEST
Subscribe to the free monthly e-newsletter: newsletter.deeneyenterprises.com
Get the short version on Linked-In: Subscribe here.
About me
Dianna Deeney is a quality advocate for product development with over 25 years of experience in manufacturing. She is president of Deeney Enterprises, LLC, which helps organizations optimize their engineering processes and team perform...