Quality during Design is the podcast for engineers and product developers navigating the messy front end of product development. Each episode gives you practical quality and reliability tools you can use during the design phase — so your team catches problems early, avoids costly rework, and ships products people can depend on.
You'll hear solo episodes on early-stage clarity, risk-based decision-making, and quality thinking, along with conversations with cross-functional experts in the series A Chat with Cross-Functional Experts.
If you want to design products people love for less time, less cost, and a whole lot fewer headaches — this is your place.
Hosted by Dianna Deeney, consultant, coach, and author of Pierce the Design Fog. Subscribe: newsletter.deeneyenterprises.com.
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
0:00
|
10:22
Once we've decided to control something (think of our prevention and detection controls), we then need to decide how to measure it. Different controls may need different measuring requirements, which can give us discrete or continuous data. We treat these data types differently when collecting it, determining sample sizes, and analyzing it for results. Tune-in to learn more about how to take the next step in defining controls: figuring out how to measure it and considering the data.
Work with Dianna I help product development teams build quality into the front end when it's cheap and easy, not late when it's expensive and painful.
Book a 20-minute discovery call with Dianna's calendar. Whether you're navigating the "fuzzy front end" of product development and want to explore a workshop or advisory partnership, or you'd like to be a guest on this podcast. You'll leave with a summary, relevant resources, and a clear path for next steps within 24 hours.
Pierce the Design Fog(piercethedesignfog.com): my book on aligning cross-functional teams, defining clear design inputs, and accelerating product success. NIEA Finalist Award, reviewed by PDMA. "Great for fans of Tony Fadell’s Build, David H. DeWolf and Jessica S. Hall’s The Product Mindset."-BookLife Reviews (Publishers Weekly)
Free Resources for Subscribers Subscribe to the Quality during Design digest — https://newsletter.deeneyenterprises.com — for monthly actionable highlights, plus access to the Strategic Quality Integration Checklist (a free self-assessment download) and my Swipe File Vault.
Speaker 1
You're listening to an installment of the quality during design versus series. In this series, we're comparing concepts within quality and reliability to better understand them and how they can affect product design engineering. We have eight episodes in this series, which means we'll be reviewing at least 16 topics. Let's get started. Hello and welcome to quality during design the place to use quality thinking to create products others love for less. My name is Diana D . 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. Visit quality during design.com and subscribe. Hi, welcome to quality during design for products, others love for less. I am your host, Diana DNY . We are in a quality during design versus series where we can hearing at least two different quality topics and learning how we can apply those two product design. In the previous episode, we talked about controls, specifically prevention and detection controls the kind of things that we want to implement within our design in our users' process that will help detect or prevent potential failures and reduce the risk of our product has on its own performance on usability and other safety measures. Well , once we've defined a control, we then need to figure out how to measure it. So today we're talking about two different types of, of data that we can use for measurement to verify the effectiveness of our controls. Today, we're specifically talking about discreet data and continuous data. Now as design engineers, we need to handle and deal with and translate a lot of different data. Our data could be coming from our own formative or summative studies about our users with our product, or it could be coming from a third party about our users. We need to be able to analyze that data and translate that into customer needs or requirements. We also have data from bench, top testing, and from our test lab, we could also be looking at data that our suppliers are giving us. If we're evaluating a component for our design and they give us data, we need to be able to interpret and look at it properly so that we understand if it's going to be appropriate for our device. And also we are setting specifications and limits and tolerances that are important to the functionality and safety and performance of our design. What type of data we might need to properly monitor our design controls needs to be considered because we also need to communicate that to others. Now, why do we need to categorize our data, the type of data that we're going to be collecting. I asked you to categorize your controls for your designs last week . And now I you to think about what category your data lies in well categorizing. These things helps us plan ahead, and it makes us pay attention to the details that matter if not now, when we're working on our design specs, then definitely later when we're deciding on next steps or passing it off for somebody else to measure for control, choosing the right kind of data, be it discrete or continuous. It affects a few things about our data. It affects how, and when we collect it and it also determines sample sizes, how many do we need to be able to make a certain confidence statement about the results? And it'll also dictate what type of analysis that are capable of being performed. So let's go ahead and define what discreet data is versus continuous data. Discreet data can be thought of, of counts of categories, like number of failures in a given time period number cycle until the first failure or number of defects on a part discrete data could be proportion like proportion nonconforming. It can also be binary. Yes, no good bad pass. Fail attribute. Data is a type of discrete data. Discreet data is also known as qualitative because we're collecting information about the quality of our product. Usually discreet data is easy and quick to collect. Think of check sheets, Continuous data. On the other hand is measured using a continuous scale, like time to failure, length, weight, or diameter, or even temperature. Continuous data is also known as variable or quantitative because it's a measure of a quantity of something. Continuous data usually requires the use of measurement tools or equipment. When we're collecting data to measure the effectiveness of the controls that we put in place to control a risk or a failure, we need to take a closer look at our control and its purpose. Are we preventing something or detecting it? And that might determine when it is going to be measuring our control. What's the criticality associated with that control? Is it really severe or is it high? And that could affect the precision and the confidence that we want in the results discreet data is usually associated with low precision measurements, think of visual standards and visual inspections for a quality of a product , uh , visual quality standards are those things that are pictures or diagrams that explain to all users and all inspectors what's acceptable. And what's not anything that is qualitative is usually a low precision data measurement because of that, it also requires a higher sample size so that we can achieve the desired confidence and statistical significance that we want when we're analyze the data . On the other hand, continuous data is considered high precision. We are using equipment and tools to measure something about our product because of its high precision nature. We usually need less samples in order to claim the confidence and statistical significance that we'd want when we're analyzing the data, no matter what we're measuring, if it's discreet or continuous, we need to ensure that our test methods are validated and that any gauge R and R studies are performed. Now, those are some of the things we can start to think about as we're designing measures for our controls. But now let's look forward a little bit into how we wanna analyze the different data types to visualize discrete data. We can plot it on a bar chart, a bar chart or categories on the XIS and frequency on the YIs. A chart uses a bar chart. Our discreet data can be further analyzed using a probability mass function or PM F the output of this is a probability at a specific value binomial and poison distributions are common with discrete data for continued data. We can visualize it using a histogram. A histogram is different from a bar chart. A bar chart has categories. A histogram has intervals of data. We can further analyze our continuous data with the probability density function To get a probability of an outcome. We can calculate the area under a curve between two points. If you remember calculus and integrals, that's the method that we use for continuous data, normal yal log normal and exponential are types of distributions with continuous data. No matter if we're looking at discreet or continuous data, both can use a cumulative distribution function. It plots a cumulative probability from zero to one along the Y axis for any given value Alon . The X something to watch for is if our discreet data happens to have digits, it would not be appropriate for us to treat that as continuous data. For example, we have a survey from one to five, we would not want to report the analysis as a mean and standard deviation. We could report it as 13% of respondents answered one and 20% respondents answer two and et cetera . So what is today's insight to action? And what can you do with what we've been talking about today? When we're creating design specifications, we're are thinking how it links back to our controls. And we think forward to how someone is going to measure it, no matter which method that we choose to collect data, we need to verify that the controls are judged or measured consistently that equipment and tools are capable with the correct level of significance. And if it's a qualitative measure , different people will come to the same conclusion. 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 Dean enterprises. Thanks for listening.
.jpg)
