Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
    • Asset Reliability @ Work
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • Quality Engineering Statistics
    • An Introduction to Reliability Engineering
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Dianna Deeney Leave a Comment

QDD 066 5 Options to Manage Risks during Product Engineering

5 Options to Manage Risks during Product Engineering

 

We’re uncovering risks during our new product development, about our design. How do we manage risks? What options do we have?

There are at least 5 options we can take to manage risks. We talk about each, and how quality and reliability methods and techniques may help us with the next steps to be able to make decisions with our team.

 


View the Episode Transcript

Our 5 options:

  1. Prioritize risks and address the riskiest submodules/components first.
  2. Test subsystems/submodules/components and test them to failure.
  3. Try to avoid risks. Be mindful about risk avoidance during development.
    • reuse proven submodules or components
    • mistake-proof the user process
    • reverse a decision
  4. Consider redundancy.
    • redundant components in the design
    • redundant development of another design option
  5. Risk/Reliability Apportionment: focus risk on one or two submodules/components instead of spreading it out among all the submodules/components

Citations:

These other QDD podcast blogs get into more details about each of these concepts. Give them a listen to explore more. Comment on the blog if you have an idea or question.

1. Prioritize risks

  • A big failure and too many causes? Try this analysis
  • Getting Started with FMEA – It All Begins with a Plan

2. Test

  • ALT vs. HALT
  • When to use DOE (Design of Experiments)?

3. Avoid risks

  • How many controls do we need to reduce risk?
  • Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds
  • The Poka-Yoke of Usability

4. Consider redundancy

  • Risk Barriers as Swiss Cheese?
  • Overlapping Ideas: Quality, Reliability, and Safety

5. Risk/Reliability Apportionment

  • Getting Comfortable with using Reliability Results
  • How Does Reliability Engineering Affect (Not Just Assess) Design?

Episode Transcript

We’ve identified a risk with our product and new product design. Now, what do we do? Let’s talk about five different options to manage risk in new product development after this brief introduction.

Hello, and welcome to Quality during Design, the place to use quality thinking to create products others love for less. My name is Dianna. I’m a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. Listen in and then join the conversation at qualityduringdesign.com.

So, we’re doing all these risk analyses and we’re coming up with risks. Well, now what do we do about it? Let’s consider what we’re developing. Let’s think about it as a product architecture point of view. We have a system and subsystem and components, and I would even go so far as to say that you would think of our whole packaged product as its own system. So, you have the actual product, but then also it’s packaging and it’s instructions for use. These are all part of our product design that we’re intending for our customers to be able to use together to properly use the product that we’re developing. We can also think of the new product development process as a learning process: as we’re developing the product, we’re learning new things about what’s working, what’s not working, and we may have to adjust for that.

Considering product architecture and that we’re continuously learning more about it through the new product development process, what are five ways that we can manage the risks that we happen to uncover during the development?

One of the things that we can do when managing risks is to prioritize them and address the riskiest items first. That could be the subsystem that has the riskiest or the highest severity risks or the thing that happens the most often. It could be components and other submodules of things that seem to be introducing a lot of risks. If we address these risks early, then it makes our project more predictable down the line. So that’s number one: we can look at the risks and evaluate them and prioritize them based on the riskiest things first.

And then that leads into our number two, which is to test the subsystems, the components, and test them to failure. If we’ve identified some of the riskiest components or subsystems, then we can test them. We can also test to find out which components or subsystems are the riskiest. Things like HALT or ALT, which is highly accelerated life test or accelerated life test. And finite element analysis is another method that we can use to test and evaluate our components. And we want to test them to failure so that we can learn more about our product so we can fix it, make it less risky. Even though we can test those components and subsystems earlier to understand how they’ll individually fail, we don’t want to lose sight of their interface and their function in the entire system. But testing those subsystems and components and submodules earlier may lead us to understand better those individual risks that that could contribute to an overall system problem.

So number one is to prioritize risks. And number two is to test subsystems and components to failures so we learn more about them. Our third option to manage risk in new product development is to avoid it. We can reuse components or use standard parts, proven designs that we already understand the risks about or how they’ll perform or their capabilities. There is risk in the unknown, in developing something new and savvy. And it’s okay and it might be a good thing for our project. If we reuse some of the components that we already have by reusing standard parts or standard components, we avoid adding new risk to our new product development. We can also avoid risk by mistake proofing the user process. (We talked about mistake, proofing the user process and how to do that in an earlier episode of the quality during design podcast and to avoid risk.) Another way to do that is to reverse a decision that we’ve made. Maybe we have a concept design that we’ve evaluated for risk, and we’ve determined that it’s too risky. So we need to do something different.

Our fourth option for managing risks is: consider a redundancy. We can add redundancy in a couple of ways. It can be an actual part of the system design, where we have redundant components in our system in case one fails, the other one would kick in. There’s also a redundancy effort that we could do during the new product development process. We could be working on design A and in parallel be working on a backup design B. Maybe design A has some new things or nuances that we’re not quite sure how it’s going to pan out, but it’s our target design. And it’s one that we really want to pursue. If it’s a high risk design, then in parallel we may want to consider design B. Maybe it’s our second choice because it’s more expensive or maybe it wouldn’t perform as well as design A, but it has less risk. So we could consider redundancy in our design development efforts to manage the risk in new product development.

The last option to manage risk in new product development (that at least we’ll cover today in this podcast episode) is a risk or reliability apportionment. Going back to our product architecture idea of systems and subsystems and components – we may want to focus our risks on one or two subsystems or components instead of spreading the risk out over all the subsystems and components together. We can do this by our choice of components, in our concept design, too. We can choose to use components that are tried and true or very reliable, or have the least amount of risk compared to other more innovative components that we may want to do a design about that might carry more risk (it might not be as reliable). Focusing our efforts on a handful of components. We can do a deep dive during the design and its testing, and we can also more closely monitor those handful of components that are the riskiest. Considering it mathematically, if you consider a reliability block diagram, we are better off having a few components that are 99% reliable and one component that is 80% reliable than to have all of our components at 90% reliability. We’ll have a greater percent chance of achieving our design goal if we have just one component that has an 80% reliability rate.

To conclude, we talked about five options to manage risks in new product development. We can prioritize risk and address the highest risk items first. We can test the subsystems and components and test them to failures so that we can better understand their failure modes and their reliability and how we think they’ll perform. We can avoid risks together. We can reuse components and standard pars that are already proven. We can mistake proof the user process, and we can even backtrack some of the decisions that we’ve made, but throughout the new product development process, we can be mindful of the things we want to do to avoid risks in the first place. We can consider redundancy in the system and subsystems and components themselves, but also in the new product development process where maybe we develop more than one option at once. And we can evaluate the risk and reliability apportionment focusing the higher risk items on one or two components or subsystems that we can keep an eye on and monitor and work with while keeping the rest of the system at a high reliability and low risk.

These are just some ways that we can proactively manage risk within new product development and product engineering. There are previous Quality during Design podcast blog episodes that go into deeper detail about each one of these options, including walking through some examples.

What’s today’s insight to action? Identifying, analyzing, and managing risk could be a natural part of product design engineering. One of the keys of getting the best information about risk is working with your greater cross functional team and quality and reliability tools and frameworks can help product design engineers do just that. In the daily grind of making design decisions, stop and look up at the bigger picture – and I mean the big picture of the whole system, everything that a customer would receive when getting your product. Consider the architecture of the product that you’re working with now. Doing so once in a while may give you that reframe that you need to adequately assess the risk of your product.

If you like the content in this episode, visit Quality during Design.com, where you can subscribe to the weekly newsletter to keep in touch. This has been a production of Deeney enterprises. Thanks for listening.

 

Filed Under: Quality during Design

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Quality during Design podcast logo

Tips for using quality tools and methods to help you design products others love, for less.


by Dianna Deeney
Quality during Design,
Hosted on Buzzsprout.com
Subscribe and enjoy every episode
Google
Apple
Spotify

Recent Episodes

QDD 102 Get Design Inputs with Flowcharts

QDD 101 Quality Tools are Legos of Development (and Their 7 Uses)

QDD 100 Lessons Learned from Coffee Pod Stories

QDD 099 Crucial Conversations in Engineering, with Shere Tuckey (A Chat with Cross-Functional Experts)

QDD 098 Challenges Getting Team Input in Concept Development

QDD 097 Brainstorming within Design Sprints

QDD 096 After the ‘Storm: Compare and Prioritize Ideas

QDD 095 After the ‘Storm: Pareto Voting and Screening Methods

QDD 094 After the ‘Storm: Group and Explore Ideas

QDD 093 Product Design with Brainstorming, with Emily Haidemenos (A Chat with Cross Functional Experts)

QDD 092 Ways to Gather Ideas with a Team

QDD 091 The Spirits of Technical Writing Past, Present, and Future

QDD 090 The Gifts Others Bring

QDD 089 Next Steps after Surprising Test Results

QDD 088 Choose Reliability Goals for Modules

QDD 087 Start a System Architecture Diagram Early

QDD 086 Why Yield Quality in the Front-End of Product Development

QDD 085 Book Cast

QDD 084 Engineering in the Color Economy

QDD 083 Getting to Great Designs

QDD 082 Get Clarity on Goals with a Continuum

QDD 081 Variable Relationships: Correlation and Causation

QDD 080 Use Meetings to Add Productivity

QDD 079 Ways to Partner with Test Engineers

QDD 078 What do We do with FMEA Early in Design Concept?

QDD 077 A Severity Scale based on Quality Dimensions

QDD 076 Use Force Field Analysis to Understand Nuances

QDD 075 Getting Use Information without a Prototype

QDD 074 Finite Element Analysis (FEA) Supplements Test

QDD 073 2 Lessons about Remote Work for Design Engineers

QDD 072 Always Plot the Data

QDD 071 Supplier Control Plans and Design Specs

QDD 070 Use FMEA to Design for In-Process Testing

QDD 069 Use FMEA to Choose Critical Design Features

QDD 068 Get Unstuck: Expand and Contract Our Problem

QDD 067 Get Unstuck: Reframe our Problem

QDD 066 5 Options to Manage Risks during Product Engineering

QDD 065 Prioritizing Technical Requirements with a House of Quality

QDD 064 Gemba for Product Design Engineering

QDD 063 Product Design from a Data Professional Viewpoint, with Gabor Szabo (A Chat with Cross Functional Experts)

QDD 062 How Does Reliability Engineering Affect (Not Just Assess) Design?

QDD 061 How to use FMEA for Complaint Investigation

QDD 060 3 Tips for Planning Design Reviews

QDD 059 Product Design from a Marketing Viewpoint, with Laura Krick (A Chat with Cross Functional Experts)

QDD 058 UFMEA vs. DFMEA

QDD 057 Design Input & Specs vs. Test & Measure Capability

QDD 056 ALT vs. HALT

QDD 055 Quality as a Strategic Asset vs. Quality as a Control

QDD 054 Design Specs vs. Process Control, Capability, and SPC

QDD 053 Internal Customers vs. External Customers

QDD 052 Discrete Data vs. Continuous Data

QDD 051 Prevention Controls vs. Detection Controls

QDD 050 Try this Method to Help with Complex Decisions (DMRCS)

QDD 049 Overlapping Ideas: Quality, Reliability, and Safety

QDD 048 Using SIPOC to Get Started

QDD 047 Risk Barriers as Swiss Cheese?

QDD 046 Environmental Stress Testing for Robust Designs

QDD 045 Choosing a Confidence Level for Test using FMEA

QDD 044 Getting Started with FMEA – It All Begins with a Plan

QDD 043 How can 8D help Solve my Recurring Problem?

QDD 042 Mistake-Proofing – The Poka-Yoke of Usability

QDD 041 Getting Comfortable with using Reliability Results

QDD 040 How to Self-Advocate for More Customer Face Time (and why it’s important)

QDD 039 Choosing Quality Tools (Mind Map vs. Flowchart vs. Spaghetti Diagram)

QDD 038 The DFE Part of DFX (Design For Environment and eXcellence)

QDD 037 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 036 When to use DOE (Design of Experiments)?

QDD 035 Design for User Tasks using an Urgent/Important Matrix

QDD 034 Statistical vs. Practical Significance

QDD 033 How Many Do We Need To Test?

QDD 032 Life Cycle Costing for Product Design Choices

QDD 031 5 Aspects of Good Reliability Goals and Requirements

QDD 030 Using Failure Rate Functions to Drive Early Design Decisions

QDD 029 Types of Design Analyses possible with User Process Flowcharts

QDD 028 Design Tolerances Based on Economics (Using the Taguchi Loss Function)

QDD 027 How Many Controls do we Need to Reduce Risk?

QDD 026 Solving Symptoms Instead of Causes?

QDD 025 Do you have SMART ACORN objectives?

QDD 024 Why Look to Standards

QDD 023 Getting the Voice of the Customer

QDD 022 The Way We Test Matters

QDD 021 Designing Specs for QA

QDD 020 Every Failure is a Gift

QDD 019 Understanding the Purposes behind Kaizen

QDD 018 Fishbone Diagram: A Supertool to Understand Problems, Potential Solutions, and Goals

QDD 017 What is ‘Production Equivalent’ and Why Does it Matter?

QDD 016 About Visual Quality Standards

QDD 015 Using the Pareto Principle and Avoiding Common Pitfalls

QDD 014 The Who’s Who of your Quality Team

QDD 013 When it’s Not Normal: How to Choose from a Library of Distributions

QDD 012 What are TQM, QFD, Six Sigma, and Lean?

QDD 011 The Designer’s Important Influence on Monitoring After Launch

QDD 010 How to Handle Competing Failure Modes

QDD 009 About Using Slide Decks for Technical Design Reviews

QDD 008 Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds.

QDD 007 Need to innovate? Stop brainstorming and try a systematic approach.

QDD 006 HALT! Watch out for that weakest link

QDD 005 The Designer’s Risk Analysis affects Business, Projects, and Suppliers

QDD 004 A big failure and too many causes? Try this analysis.

QDD 003 Why Your Design Inputs Need to Include Quality & Reliability

QDD 002 My product works. Why don’t they want it?

QDD 001 How to Choose the Right Improvement Model

© 2023 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy

This site uses cookies to give you a better experience, analyze site traffic, and gain insight to products or offers that may interest you. By continuing, you consent to the use of cookies. Learn how we use cookies, how they work, and how to set your browser preferences by reading our Cookies Policy.