MENU

 

28-Jun-2017

Risk Mitigation in Product Design: Part 1

By Doug Harriman (Chief Technology Officer)


During product development, you must take risks to achieve market success. To also achieve business success, it’s critical for a design firm to assess and address risks as early and affordably as possible. At Simplexity, we’ve spent our careers helping a wide variety of companies do just that, and view risk mitigation as an integral part of the stages of product development.

Why is product development risky?

For a product to have market appeal, it must either be differentiated from existing products in its category, or it must create an entirely new category. In either case, the successful product offers something new to the market. That “something new” requires a design that’s never been done before. And if it’s never been done before, it’s inherently risky.

The more customer “wow” you pack into your product, the greater the risk in the product development process. The upside is that it will also bring higher potential for market success. If you take no risk with your product, the chances of success are low, thus mapping the risk/reward space is a helpful component of brainstorming.

Product development risk categories

Just like any business, product development has many types of risk. There are market-based risks such as commercial viability, consumer acceptance, competitors, and the product introduction window timing. There are organizational risks like availability of funding, availability of management sponsorship, staff loading, and capability of project management. There are risks associated with building your product, including the technical and logistical capabilities of your supply chain and manufacturing partners, as well as the business stability of each.

At Simplexity, we believe that the product design team must be heavily involved with the selection, assessment, and interactions with supply chain and manufacturing partners during development. However, I’m going to focus on the different areas of technical risk in the design portion of product development.

Technical risk centers around what is both technically possible and financially feasible for the product and its market segment. A successful design team must find a way to answer yes to both “Can we do it?” and “Can we afford to do it at our price point?” Developing new product features that meet the required specifications, technicality, and quality, with a viable cost structure, is the overarching risk for an engineering design team.

Mapping and weighing risk assessment

The classic tool for the assessment of technical risk of a product is the failure modes and effects analysis (FMEA). Essentially, one looks at a product, assesses all the different ways the product can fail, and the effects of those failures on the product, the customer, and the manufacturer. When applied in the design phase of product development, we add a “D” to front of the acronym, and perform the analysis on the design options under consideration.

At Simplexity, the DFMEA process involves getting a broad team to do a design review. It’s important to get fresh eyes on the design, and bring in a broad experience base. After the team has conducted their individual design reviews, we conduct a brainstorming session to list all the design’s potential failure modes. We then assess each item in the list for both the probability of the given failure mode and the severity of consequence of that type of failure. Finally, we map those assessments to a risk category with this matrix:

Discover a product design’s potential risk with a risk assessment matrix.

From this mapping, we can sort the failure modes by risk category and prioritize our mitigation efforts accordingly. Note that we do not apply weightings to these categories and attempt to generate a numerical risk value. This is intentional. Over the years, we’ve found that applying weightings just shifts the debate over the categorization to a debate over the weighting of the category, doing nothing to move the analysis forward. Our DFMEA process has proven itself to strike the proper balance between effort (and cost) expended, and value provided.

For more resources and support for topics related to product design, prototyping, 3D motion, and more, follow Simplexity’s product development blog.

 


Subscribe For More

To receive more articles like the one above in your inbox, sign-up to our newsletter below.

Blog Posts


Ossia Cota Forever Battery: Collaborative Design

13-Dec-2018

Better Firmware Faster

19-Nov-2018

Demystifying What it Takes to be a CEO

18-Oct-2018

Considerations for Code Refactoring

24-Sep-2018

American Association for Clinical Chemistry Annual Meeting

30-Aug-2018

Simplexity's Answer to Growing Pains

09-Aug-2018

Consumer Electronics Show 2018 | Part Three | So, What is a Robot?

29-Jan-2018

Consumer Electronics Show 2018 | Part Two | CES 2018 and IoT

22-Jan-2018

Consumer Electronics Show 2018 | Part One

15-Jan-2018

Why on earth are heavy weights being suspended from this printer?

22-Dec-2017

10 Best Places to Buy Parts for Product Development

29-Nov-2017

Robust Firmware Stack Sizing

08-Nov-2017

Senaptec Strobe: A Study in Simplification

19-Oct-2017

Treatment, Prevention, and Medical Engineering Solutions

04-Oct-2017

Options in Product Development Models: Internal, CDM, or Design Specialist

20-Sep-2017

Designing Thermal Control Systems

30-Aug-2017

Simplexity’s 7 Steps to Simplification©

15-Aug-2017

Battle of the Buttons: UCSD vs. PSU

02-Aug-2017

Considerations For Medical and Biotech Designs

13-Jul-2017

Risk Mitigation in Product Design: Part 2

11-Jul-2017

Risk Mitigation in Product Design: Part 1

28-Jun-2017

San Diego's Biotech Consortium

09-Jun-2017

Appropriate Models for 3D Motion Analysis: Part 3

25-Apr-2017

University of Oregon’s Product Design Program Is One of a Kind

19-Apr-2017

Appropriate Models for 3D Motion Analysis: Part 2

14-Apr-2017

From Engineer to Leader: How Do You Get There?

12-Apr-2017

Appropriate Models for 3D Motion Analysis: Part 1

06-Apr-2017

Why Engineering Still Matters in Product Development

29-Mar-2017

How Mechatronics Improve Drone Technology

16-Feb-2017

Why You Need a Gyro to Measure Position

20-Jan-2017

Why I, As The CEO, Get The Same Bonus As All My Other Employees

13-Dec-2016

Mechatronics Aids In Embedded System Design

07-Dec-2016

Top 10 Tips for Designing Injection Molded Plastic Parts

22-Nov-2016

British school kids and car hackers: the widespread appeal of open source

14-Nov-2016

When should you consider designing custom gears?

07-Nov-2016

Conference Report: Open Source Hardware Summit

31-Oct-2016

What is a Motion Control System?

20-Oct-2016

The Top 10 Questions to ask a Product Development Firm

05-Oct-2016

The Potential of the Apple AirPods To Disrupt A Whole Industry

12-Sep-2016

How to Use Open Source Hardware in Product Development

01-Sep-2016

What is the mech in mechatronics?

16-Aug-2016

3 Tips for IoT Product Success

02-Aug-2016

When Should I Start Designing For High-Volume Manufacturing?

19-Jul-2016

Designing a 3D Printer for the Home

29-Jun-2016

It Turns Out That EMC Is Not Black Magic

22-Jun-2016

Selecting the correct motor type and size

06-Jun-2016

When brainstorming fails, throw an imaginary cat

18-May-2016

Five Tips for Mechatronic System Integration

09-May-2016

Three Tips for Designing High Volume Mechatronic Products

28-Apr-2016

What Is Mechatronics?

18-Apr-2016

If I could only do 3 things to simplify a design, what should they be?

06-Apr-2016