Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • CMMSradio
    • Way of the Quality Warrior
    • Critical Talks
    • Asset Performance
    • 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
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Maintenance 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
      • RCM Blitz®
      • ReliabilityXperience
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • 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
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • Your Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
      • FMEA Introduction
      • AIAG & VDA FMEA Methodology
    • Barringer Process Reliability Introduction
      • Barringer Process Reliability Introduction Course Landing Page
    • Fault Tree Analysis (FTA)
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
    • Accendo Reliability Webinar Series
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
Home » Podcast Episodes » Quality during Design » QDD 129 The Strategic Gamechanger: Quality during (Product) Design

by Dianna Deeney Leave a Comment

QDD 129 The Strategic Gamechanger: Quality during (Product) Design

The Strategic Gamechanger: Quality during (Product) Design

 

Ever wished you could ace the art of product design using quality frameworks? Your wish is just about to come true!

We unravel the ADEPT framework, your magic wand for creating products that are not just satisfactory,  but loved by users. We’ll also be discussing how to lead a team effectively, conduct hands-on meetings, and choose the right participants. These handy tips will enable you to develop top-notch products using cross-functional collaboration.

We’re also unveiling how quality itself can be a strategic gamechanger in product design. The ADEPT framework, applicable to any quality tool, will bring alignment, discovery, examination, prioritization, and teamwork to your concept development process.

With Quality during Design’s unique approach and with these resources at your fingertips, you’re ready to step up your product design game.

 

View the Episode Transcript

Use ADEPT to help you Design & Create Early Concepts

 

We’ve reviewed the ADEPT framework and how you could use that for early concept development with your team. The ADEPT framework can really be used for any quality tool that you think is going to fit the need of whatever it is that you’re trying to learn more about. It’s a way that you can apply quality during design with your cross-functional team in early concept development.

When we’re thinking about using quality in early concept development, we’re thinking of ways to use quality strategically. ASQ studies how quality is implemented in organizations, and they report that only about one quarter to one third of our organizations view quality as a strategic asset, as a way to differentiate ourselves from our competitors. The rest of us see quality as a compliance activity or for continuous improvement or as just a way to fix problems and mitigate risks.

We should shift our thinking to think that quality is a strategic asset to product development, and we can use it proactively to help us improve the development process. We can use quality engineering and reliability engineering to add more concept development and provide information to help us make decisions during the development so we can have those products that others love for less.

 


Previous Quality during Design podcast episodes in this series:

Exploring the Problem Space: A Key Principle for Robust Product Design and Project Success

Understanding Cross-Functional Collaboration

Leveraging Proven Frameworks for Concept Development

 


Visit the workshops page to link to the recorded webinar.

Quality during Design Workshops


Episode Transcript

You’re listening to the Quality During Design podcast. This is Dianna. Over the last few weeks, we’ve been exploring more about the foundations and frameworks of Quality During Design. We started talking about the engineer’s role in early concept development and how we want to stay in the problem space a little longer. We then talked about cross-functional collaboration and then using some of those quality frameworks with our teams in concept development to be able to generate ideas and get design inputs. In this episode, I want to dive a little bit deeper into how we can use these frameworks specifically for concept development for product design. I’ll be sharing some practical tips on how to apply these frameworks to get those design inputs and priorities that you need for your project. Listen in, after this brief introduction.

Hello and welcome to Quality During Design, the place to use quality thinking to create products others love for less. Each week, we talk about ways to use quality during design and product development. I’m your host, Dianna Deeney. I’m a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. I consult with businesses and coach individuals and how to apply quality during design to their processes. Listen in and then join us. Visit qualityduringdesign.com.

In the previous episode, I shared a little bit of a webinar that I had previously given and I’m going to do a bit of the same today. I gave a talk a couple of weeks ago to technical communicators for flowcharts. I teamed up with Scott Abel and The Content Wrangler and Hereto to give that webinar. As part of that webinar, I introduced a framework that could be used that explained how quality tools could be used in early concept development, what they could be used for. It also lists activities that you can do to ensure that you’re having the most effective cross collaboration teamwork in early concept development that you can get.

The system is called ADEPT and it’s short for Align, Discover, Examine, Prioritize and Teamwork. In this episode I go through each one of these steps and I share with you the best practices that I’ve found have worked best for me and what I’ve found other people say worked best for them also. So let’s get into it. Let’s talk more about how we can customize these quality frameworks for product design.

I don’t want to confuse this kind of teamwork with the typical brainstorming. Typical brainstorming is more free and it’s an expansion of ideas and creative prioritization and it raises a lot of questions the quality tool and quality during design framework and teamwork that I’m talking about. We do pre-work in preparation for a meeting. We discover with our team, but it’s very prompted. We have criteria against which we can prioritize. We do creativity, but with co-work and it drives actions.

I’m going to give you some tips for teamwork to do with a cross-functional team using quality tools. The first one is probably one of the most important. I’m probably going to say that about all of these.

Pre-work: you do, or plan the pre-work. You should have a goal in mind and you should have a quality tool or some other framework that you know you want to use with your cross-functional team. I have done it both ways. I have tried to be clever and call the team and say, “Hey, let’s create something together in a design!” and it has never worked for me. And if you do a lot of research online, they’ll also say that, yeah, this doesn’t really brainstorm me, doesn’t really work for me either – to really come up with something solid for me to design against. But the other way that I’ve done it is that I’ve done my research. If I’m responsible for a particular design of something, like you’re responsible for technical communication product, you know the kind of initial work that you need to do to start to figure out how you’re going to design something. So go ahead and do that. Do your research, try to figure out the users, create a high-level basic flow chart and get something going for your team to be able to look at and adapt. I’ve had a lot of success in doing things this way.

Lead: The other thing is that you want to lead. You lead the team meetings. You lead the facilitation. This is your product that you’re designing, so you need to be confident in your capabilities to lead. Now that doesn’t mean that you can’t ask for help. If you don’t feel like you’re good at facilitating or you want to share that responsibility with somebody, you can. You’re the leader. You can decide that I want help with facilitating this meeting and find somebody to help you do that. Another thing that some people find useful is a scribe or somebody that can help take meeting minutes or notes during the meeting. If you feel like you need that help so that you could focus on leading your team through an analysis, then go ahead and enlist somebody to be a scribe.

Keep it hands on: I have sat through meetings and I’m embarrassed to say that I’ve done meetings where we’re trying to fill in an Excel table with information during the meeting as we’re trying to figure out things, or we open up a Visio flow chart or some other online flow chart creation. We’re trying to create a flow chart in the software as we go. Just don’t do it. It just gums up everything because you’re trying to make something pretty while you’re working and it just doesn’t work. It slows down the team momentum, it slows down the process, the whole reason why you’re getting your team together in the first place. So keep it hands on and don’t worry about it being pretty during the meeting. You can clean it up later. And by hands on I mean use a whiteboard, use flip charts virtual or real. Use Post-it notes virtual or real. Here I’m showing a whiteboard where I use virtual flow, virtual Post-it notes for flow chart. I just used red for the start and end, yellow for the process steps and then green for the decision points. You can do it simply like that.

Invite the right people: There’s a spectrum of experience and a spectrum of familiarity of the people in your world with your project. If you can, it would be good to get a mix of both someone really experienced and or familiar and somebody inexperienced and not so familiar. The experienced and familiar people are going to have good backgrounds, good historical information, ways to do things that have worked in the past. The inexperienced and the unfamiliar people are going to be able to challenge those assumptions of the experienced people or to ask questions that maybe everybody else thinks might be obvious, but maybe they’re not. The other thing is a functional focus, and I spent some time on this earlier, just inviting different people from different functional groups that are going to be part of producing this product. Finally, the decision maker. If you’re creating a product where a decision maker needs to make the final decision, make sure they are involved somehow. They either should be part of the meeting or, if they can’t be, then another option is for you to create one or two options with different priorities that you resulted from the team, that you got out of your activity with the team, but just make sure that the decision makers involved. It is their responsibility to make a decision, so make them make it. Don’t let them see their authority.

Pizza rule: And we all know if you get a whole bunch of people in the room and you’re trying to make decisions about stuff and work on things, that doesn’t work either. So a lot of people say three to seven. I’ve seen up to nine, but I liked this point of reference that my friend gave me. If you decide you’re having a meeting and you tell them it’s a pizza party, you should only have to order one pizza and that’s it. If you can’t feed the people at your meeting with one pizza, then you have too many people, but a general rule of thumb is seven.

So this ADEPT framework, it is not only what you get out of doing it, but it’s also the types of activities that you follow to lead your team, and this is sort of a stepwise approach.

When I was looking at the latest poll, it looked like I create too many different versions of my product before it’s finally done was pretty much neck and neck with. I have a hard time getting feedback from my team, so I want to tell you that the answers to the quiz that I had you take in the beginning sort of line up with this. They not sort of they do line up with this ADDEPT system.

So what is your biggest challenge with designing products?
If you chose I create too many different versions of my product before it’s finally done, then you may need to work better on your alignment.
If you chose I have a hard time getting feedback from my team, you may want to work more on discovery.
If you think my work is nearly done and it gets picked apart, you may need to focus more on examining options.
And then, finally, my products fail many validation tests with users – you may need to work more on prioritizing.

Let’s take a look at each one of these.
A – With aligning is the first thing that you do when you’re working using a flow chart with your team With a goal. You always want to have your goal because you did the pre-work and you always have it visible. It’s at the top of the whiteboard, it’s at the agenda when you send it out. It’s at the top of whatever work surface. It should always be visible during the meeting. Everyone understands the scope and that you’ve picked a quality tool so that it’s a visual representation of what it is you’re trying to figure out. You can align around the quality tool to have discussions, to get information.

D – Now D does anybody remember what D is? It’s Discover. Now we want to work alone, together and have it time bound. This is something that’s heavily emphasized in a book called Sprint by Jake Knapp and a lot of Harvard business reviews and mirror articles. They also focus on this type of method too, and it does work. In this case, we are doing creation, we are discovering ideas about other people. We’re all working alone, but we’re doing it together in the same room and we’re limited with how much time we have to do this. It varies from 5, 10, or 15 minutes, depending on how complicated of a question that you have and if you can try to keep the discovery of new ideas anonymous, and that’s going to play into some of the later steps that we have here. Doing things this way when you can. It combats a lot of the problems that many of us may have experienced with the typical brainstorming type of activities that we’ve done.

E – Examining is where we take all those ideas and we group them, we define them, we refine them and we want to be positive about it, instead of saying, well, that’s a dumb idea, we don’t want to use that or that’s not going to work, that stinks. Instead, we say what is it about this idea we can use when we do have discussions? We’re doing it to clarify the ideas so that everybody can assess the different ideas by understanding the same thing about them. We don’t really want to have debates and we don’t want to have people presenting their idea, because that’s getting away from the anonymous part of it. If we do group activities, so group activities meaning we have a bunch of ideas and we want to take them aside and put them into different groups so we can learn more from them. We’re going to do that without talking, not going to clarify the different ideas, we just do it silently. That help assess, examine the ideas that people have created.

P – Then we can prioritize them. We want to have predefined criteria. Now sometimes that’s defined by the quality tool. Our critical to quality analysis has criteria to prioritize the different steps, and so does our value added analysis. The other things you can do to prioritize is use multi voting. For example, you give everyone five stickers and then everyone can put those stickers on different ideas that they like. They can put it all in one idea, it doesn’t matter. A two by two chart is another way to prioritize ideas and that could be like an urgent, important matrix. The key that would be helpful for your team is to always keep yes as the most desirable, not mixing it up, but yes is always a thing that people want the most.

T – And finally, teamwork we want to get consensus on one to two options with pros and cons Remember it’s a decider’s job to decide to let them and you want to gather the action items and follow up on it so you can use this model to help you design and create early concepts with quality tools.

So just imagine your results, your product design results, questioning and investigating within the problem space when you do that with your team, and imagine the teamwork when we use the ADEPT model, which is a mix of quality tools and some best practices learned from brainstorming.

Remember that we can design and create with quality tools. They’re not just something that we can use to check the quality at the back end. They’re actually a very useful visual tool for people to design around and you can use quality tools to focus on the user for early concept work before we even have any product design stuff done.

With all of this, you can hopefully see how you can use quality as a strategic asset, not just a check before things go out the door.

We’ve reviewed ADEPT and how you could use that for early concept development with your team, and the ADEPT way of thinking or the ADEPT system can really be used for any quality tool that you think is going to fit the need of whatever it is that you’re trying to learn more about. The ADEPT system is a way that you can apply quality during design with your cross-functional team in early concept development.

I had ended that webinar with a statement about using quality as a strategic asset, which is what we’re trying to do here when we’re thinking about using quality in early concept development. ASQ studies how quality is implemented in organizations and they report that only about one quarter to one third of our organizations view quality as a strategic asset, as a way to differentiate ourselves from our competitors. The rest of us see quality as a compliance activity or for continuous improvement or as just a way to fix problems and mitigate risks.

We should shift our thinking to think that quality is a strategic asset to product development and we can use it proactively to help us improve the development process. We can use quality engineering and reliability engineering to add more concept development and provide information to help us make decisions during the development so we can have those products that others love for less.

If you’d like to view the webinar, go to the website QualityDuringDesigncom. There is a picture link there that you can click and register onto BrightTalk. After you register, which is free, you’ll be able to view that webinar and lots of other ones, including the other webinars that were produced by Scott and the content Wrangler.

Qualityduringdesign.com is also filled with a lot of blogs that are associated with this podcast. It’s extra information and transcripts, extra links. There’s also access to free training and ways to subscribe to the weekly newsletter. Visit QualityDuringDesign.com and do some exploring and you’ll see that we’ve covered some specific quality tools and their application to product development in the blog history. This has been the production of Deeney Enterprises. Thanks for listening!

Filed Under: Quality during Design

About Dianna Deeney

Dianna is a senior-level Quality Professional and an experienced engineer. She has worked over 20 years in product manufacturing and design and is active in learning about the latest techniques in business.

Dianna promotes strategic use of quality tools and techniques throughout the design process.

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 168: Brighten Your Creative Spark

QDD 167: Redux: Choosing a Confidence Level for Test using FMEA

QDD 166: AI in Design: Coming Full Circle

QDD 165: Redux: 5 Aspects of Good Reliability Goals and Requirements

QDD 164: Supplier Agreements: The Good, The Bad, and The Quality

QDD 163: Practice Makes Improvement in Subjective Probability Estimations

QDD 162: Redux – Quality Tools are Legos of Development (and Their 7 Uses)

QDD 161 Cultivating a Culture of Craftsmanship within Quality Systems

QDD 160 The Mighty Power of Mini Reports

QDD 159 Celebrating a Year of Insights

QDD 158 Social Dynamics with Yakira Mirabito (A Chat with Cross-Functional Experts)

QDD 157 How Engineers Changed Thanksgiving

QDD 156 Predictive Analytics, Machine Learning, AI, and VR in Design Engineering

QDD 155 Improving Communication and the Workplace with Meagan Pollock (A Chat with Cross-Functional Experts)

QDD 154 Myths of Product Development – Part 2

QDD 153 Myths of Product Development – Part 1

QDD 152 Engineering Careers: A Panel Discussion with ‘Brilliant!’ and ‘How to Win Friends and Influence People’’

QDD 151 Revolutionize Your Technical Presentations: Mastering the Assertion Evidence Model and the Six P’s Framework

QDD 150 Prioritizing Customer Satisfaction in Product Design (the Kano Model)

QDD 149 Maximizing Meeting Value and Participation

QDD 148 Data Visualization Tips to Improve Analysis Skills

QDD 147 Effective Team Meetings: From Chaos to Cohesion

QDD 146 Unraveling QA, QC, Quality Assistance, and Quality 4.0

QDD 145 Simplifying Probabilities for Better Decision Making

QDD 144 From Solo to Collaboration: Lessons from Nobel Laureate Shuji Nakamura and Dale Carnegie

QDD 143 Bridging Triumph and Trial: A Panel Discussion about Engineering with ‘To Engineer is Human’ and ‘The Wright Brothers’

QDD 142 What is DFSS and How does Quality during Design Relate?

QDD 141 Exposing The Hidden Flaws of FMEA and Risk Matrices: Advancing Your Risk Assessment

QDD 140 Getting Information for Product Design with Fred Schenkelberg (A Chat with Cross-Functional Experts) – Part 2

QDD 139 Getting Information for Product Design with Fred Schenkelberg (A Chat with Cross-Functional Experts) – Part 1

QDD 138 Harnessing Team Insights for Risk Analysis using Probabilities

QDD 137 From “Fall-Through” to “Follow-Through”: A Proactive Strategy for Design

QDD 136 Welcome Back! New, Upcoming Opportunities with FMEA and Quality during Design

QDD 135 Taking a Brief Pause: Reflecting on Quality During Design’s Journey and Preparing for What’s Next

QDD 134 Timing Reliability in Product Design, with Jeffrey Lewis (A Chat with Cross-Functional Experts)

QDD 133 Driving Effective Conversations-Prioritizing and Decision Making at Concept Development and Beyond

QDD 132 Driving Effective Conversations-Three Major Aspects to Consider for DfX

QDD 131 Driving Effective Conversations-Taking the Lead in Working Meetings

QDD 130 Supply Chain Management during Design, with Kevin Bailey (A Chat with Cross-Functional Experts)

QDD 129 The Strategic Gamechanger: Quality during (Product) Design

QDD 128 Leveraging Proven Frameworks for Concept Development

QDD 127 Understanding Cross-Functional Collaboration

QDD 126 Exploring the Problem Space: A Key Principle for Robust Product Design and Project Success

QDD 125 Exploring Product Development and AI Through Literature

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

QDD 123 Information Development in Design, with Scott Abel – Part 2 (A Chat with Cross-Functional Experts)

QDD 122 Information Development in Design, with Scott Abel – Part 1 (A Chat with Cross-Functional Experts)

QDD 121 Crafting Effective Technical Documents for the Engineering Field

QDD 120 How to use FMEA for Complaint Investigation

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

QDD 118 Journey from Production to Consumption: Enhancing Product Reliability

QDD 117 QDD Redux: Choose Reliability Goals for Modules

QDD 116 Reliability Engineering during Design, with Adam Bahret (A Chat with Cross-Functional Experts)

QDD 115 QDD Redux: 5 Options to Manage Risks during Product Engineering

QDD 114 The Instant Glory of Projects

QDD 113 What to do about Virtual Meetings

QDD 112 QDD Redux: How to self-advocate for more customer face time (and why it’s important)

QDD 111 Engineering with Receptivity, with Sol Rosenbaum (A Chat with Cross-Functional Experts)

QDD 110 Don’t Wish for Cross-Functional Buy-in on Product Designs – Plan to Get It!

QDD 109 Before You Start Engineering Solutions, Do This

QDD 108 QDD Redux Ep. 4: Statistical vs. Practical Significance

QDD 107 QDD Redux Ep. 3: When it’s Not Normal: How to Choose from a Library of Distributions

QDD 106 QDD Redux Ep. 2: How to Handle Competing Failure Modes

QDD 105 QDD Redux Ep. 1: How Many Do We Need to Test?

QDD 104 The Fundamental Thing to Know from Statistics for Design Engineering

QDD 103 What to do for Effective and Efficient Working Meetings

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

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

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

Book the Course with John
  Ask a question or send along a comment. Please login to view and use the contact form.
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.