We're in the middle of our design process and we're getting some of the first parts in hand, either from prototyping or benchtops, or our manufacturing cell. Let's test them and finish our verification testing! Maybe we shouldn’t.

We talk about the concept of production equivalent: what it means and when it's important to consider.

For a transcript and extra links, see the podcast blog.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

"A picture is worth a thousand words" is an old saying, and it holds true! Visual standards, visual aids, and quality standards are a great tool, especially in design when communicating the limits of acceptability. This episode explores areas to capture this type of information and how it can be used not just for Quality Assurance and Production, but also for FMEA, root cause analysis, and future field defect investigations (to name a few).

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

The likeness of the Pareto Principle can be compared to Murphy's Law and the Peter Principle: it's a curious phenomenon. So, how did it make its way into quality? If using it to make decisions, there are some common pitfalls which can lead to delays in fixing a problem or even misdirect our efforts. So, what is it, and how can we use it for design?

Get to know the Pareto Chart. If it's built and applied properly, it can help us prioritize: root cause analysis, new design features based on user input, or to help us tackle a problem that just seems too big to even start (just to name a few examples).

We review the Pareto Principle, what a Pareto Chart is, what we need to consider when building one, and how we need to be careful when interpreting its results.

Get extra graphics, links, and articles at this podcast blog, at www.qualityduringdesign.com.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

Part of being an effective team member is knowing what the other teammates are responsible for doing. It's important because we need to know who to ask or interface with at certain points in our design process. This episode introduces (or reintroduces) some of our quality friends in design: Quality Engineer, Reliability Engineer, Supplier Quality, Calibration Technician, Quality Technician, and Quality Inspector.

The podcast blog discusses more about cross-functional teams.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

When trying to fit a probability distribution to quantitative results, sometimes the normal probability doesn't fit. Minitab has a wealth of distributions to pick from. Do you just pick whichever one Minitab tells you fits the best? Maybe not. Just because the distribution fits your data doesn't mean it's a good one to use. We review my top 3 distributions for product testing and some other ones that come up but may not be appropriate to use. We'll also share what you need to think about when picking a distribution.

The podcast blog includes useful links.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

You may have heard of QMS (Quality Management Systems) but are not sure how your activities fit in. Or, you’ve heard of QFD, ISO 9000, Six Sigma, Lean...these cryptic names that you’re not sure what they’re about. You may be doing activities under one of your company’s procedures and asking, “Why am I spending time on this?"  Sometimes it’s good to re-orient to the big picture. That’s what we’ll be doing in this episode: reorienting to the QMS.

We'll also talk about some of the standard Quality Management System philosophies:

• TQM (Total Quality Management)
• ISO 9000
• QFD (Quality Function Deployment)
• Six Sigma
• Lean
• Malcom Baldrige National Quality Award 

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

Because of your role as a designer in product development, you have great input into the planning for what field (or real-use) data should be monitored for your product. We talk about this as post market surveillance, which is a typical term used for medical devices. This episode talks about how the post market surveillance engine follows the PDSA (plan-do-study-act) continuous improvement cycle, some expectations of post market surveillance systems, and what inputs designers have in its planning. 

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

If we're not careful with or ignore failure modes, we can choose the wrong reliability model or statistical distribution. If our product performance is close to the required limits and/or we need a very accurate model, this could be a big problem.

We talk about the importance of failure modes and step-through a tensile-test example to explore these other topics:

• competing failure modes
• suspensions
• independent vs. dependent
• reliability block diagrams

The podcast blog includes extra useful information/links.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

A danger of using slide decks for technical design reviews is loss of important technical information. In order to summarize something in a slide or slide deck, the presenter thins-out information without its raw data and divorces it from the plots, graphs, and other technical analyses.

Slide decks are useful to the presenter to pull together a meeting. Slide decks are terrible for the reviewers who need to review technical information and make decisions from it.

In this episode, I review some alternatives.

The podcast blog includes extra information, links, and citations.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in. 

Recent news highlights an accident involving a product with tragic results. This podcast explores this as cautionary tale and example outside of our own design house. The goal is to shift our perspectives to let us gain a better understanding of risk-based decisions. We also talk about allowing ourselves room to change our minds about risk acceptability when we learn new information, both during the design process and from the field.

The podcast blog includes extra links and updates.

Send us a message

If your team is still catching problems too late — let's talk.
→ Schedule a free discovery call: Dianna's calendar

Get the full framework.
→ Pierce the Design Fog 

ABOUT DIANNA
 Dianna Deeney is a product development process strategist with over 25 years of experience in regulated industries. She is president of Deeney Enterprises, LLC, where she helps product development teams make better decisions upstream — before costly design mistakes get built in.