The power of failure

A very common mantra in product development and specifically Design Thinking is to “fail early and often.”

While the headline – The Power of Failure – suggests that I was poised to reiterate this well-understood strategy for innovation, I instead feel inspired to share my perspective on the value of an old-school methodology known as Failure Mode & Effects Analysis (FMEA).

Really, this blog should have been titled, The Power of Failure Mode & Effects Analysis, but that is undoubtedly less catchy, and you may not have actually read this far. Stick with me, I hope you find it worth the read. FMEAs are a systematic technique for identifying and mitigating potential failure modes in a product or process (service). To be clear, I’m not suggesting utilizing a FMEA methodology as an alternative to a Design Thinking approach, it’s more about highlighting that at a certain point in the new product development process your technical risk mitigation activities may need to step up a level and having a proven process to guide those activities can have distinct advantages.

Eventually in the iterative Design Thinking process, it is time to pick your lead horse and chart a path to realization. While failing early when the stakes are lower is a key tenet of Design Thinking that helps push the envelope, it doesn’t mitigate the damage of one-star reviews on Amazon for a clunky consumer product, or the cost of lost market share for a commercial product that’s performance doesn’t stack up against the competition, or the increased development cost and time for a medical device that struggles to perform in verification testing. These are all clear examples of why at a certain point, failure is no longer an option.

Most engineers are hard wired to think about all of the things that can go wrong and quickly identify what they believe are the biggest technical challenges to realize a new product. At Design Concepts, we use that to our advantage by staffing even our earliest conceptualization projects with engineers that can both flex their creative muscles and help identify what technical risks may benefit from early prototyping. In product development there is an inflection point where the focus goes from what should the product be to whether it will actually work. Despite repeated pleading from those in charge, seldom can an engineering team proclaim success is guaranteed. More often than not, if a development team is really moving the needle, there will be technical risks.

FMEAs originated in the 1950s by reliability engineers in the U.S. military, eventually making their way into NASA in the '60s and into automotive design in the '70s. Today, FMEAs are still a common methodology for risk mitigation and are quite prevalent in medical device development and more broadly in healthcare for de-risking processes. I’m just guessing, but I would bet that a FMEA may have led to the practice of a surgeon visiting you in pre-op prior for your knee surgery, during which he or she circles and initials the knee to be operated on as your mind races thinking about the potential implications if that step wasn’t taken.

06 Article Kent Failuremodeschart @2X
Example of an FMEA.

Let’s talk about how we can help move your business forward.

Contact us today →
Sketch of a phone
Delve has merged with Bresslergroup. Learn more →