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.What is the difference between these two FMEAs?How do they relate to one another?Should we do both of them?What do we do with the information?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 PlanChoosing a Confidence Level for Test using FMEARemaking Risk-Based Decisions: Allowing Ourselves to Change our Minds.Prevention Controls vs. Detection ControlsThe Designer's Risk Analysis affects Business, Projects, and SuppliersA big failure and too many causes? Try this analysis. (FTA)Ready to apply this to your project?→ Schedule a free discovery call: Dianna's calendarWant insights like this?→ Subscribe to my newsletter: qualityduringdesign.substack.comLearn the full framework:→ Get the Book: Pierce the Design Fog ABOUT DIANNADianna 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 and people improve engineering design.

Ver todos los episodios