Your Reliability Engineering Professional Development Site
Quality during Design is the place for product designers to use quality thinking throughout the design process to create products others love, for less.
In product development, we often get caught up in the technical specifications and features we’re creating, forgetting the fundamental reason we’re building products in the first place: to provide benefits that improve users’ lives. This foundational concept of benefits versus features deserves revisiting regularly, especially when we’re deep in the weeds of development work.
In product development, the “fuzzy front end” of concept development often represents both tremendous opportunity and significant challenge. During this critical phase, teams are tasked with defining problems, understanding customers, and generating solutions—all before any engineering begins.
How we navigate this phase dramatically impacts bottom-line results, market share, customer satisfaction, and whether projects even launch at all.
What makes concept development particularly difficult is that teams typically lack something concrete to discuss. Without prototypes or developed products, conversations can become abstract and unfocused. This challenge is compounded when cross-functional team members approach problems from vastly different perspectives, sometimes unknowingly working to solve entirely different issues altogether.
The traditional approach of gathering everyone in a room for open brainstorming sessions has proven remarkably ineffective. Research confirms what many of us have experienced: teams engaged in unstructured brainstorming typically generate fewer ideas, and those ideas are often of lower quality compared to more structured approaches.
The solution lies in using visual models and templates—structured frameworks that guide the creative process and facilitate meaningful team collaboration.
Have you ever watched a promising product idea slowly die in the fuzzy space between “great concept” and “actual development”? You’re not alone.
The journey from product idea to market-ready solution contains a critical yet often overlooked phase: concept development. This is where cross-functional teams must align their diverse perspectives to create a solid foundation for design. But as many product developers discover, this is precisely where communication frequently breaks down.
In this episode, we dive deep into why cross-functional teams struggle to communicate effectively during early concept development and how to fix it.
The hidden costs of poor product development can devastate your project timeline, budget, and ultimate market success. Drawing from Dr. Robert Cooper’s research, this episode reveals how skipping proper concept development—the critical “fuzzy front end” of product design—leads many teams into a costly “ready-fire-aim” approach.
Ever hit that wall where your creative tank feels bone dry? That moment when you’ve been grinding away at your projects, head down for so long that when someone asks for innovation, you come up empty? You’re not alone.
Creative slumps happen when we get too immersed in our specialized domains. As engineers and designers, we develop expertise through consistent application of familiar tools and techniques. But that same specialization creates mental echo chambers where we recycle the same ideas and follow habitual thought patterns. The result? When innovation is needed most, we feel frustratingly blocked.
The solution lies in cross-pollination – deliberately exposing ourselves to diverse inputs that spark unexpected connections.
We’re developing requirements for our product, including setting reliability requirements. Or we’re setting acceptance criteria for our test plans.
What confidence levels do we choose? We don’t have to blindly set them – we can base it off the risks of failure, using our FMEA (failure mode effects analysis).
As a Generation X engineer, I’ve witnessed remarkable shifts in how we approach design engineering.
Recently, I saw an article suggesting Gen X is frustrated because the skills we learned early in our careers no longer apply in today’s technological landscape. This characterization made me pause and reflect. While our tools have certainly evolved dramatically, I believe we’re experiencing something more nuanced than obsolescence.
With AI in design, we’re coming full circle, with artificial intelligence and machine learning enhancing rather than replacing the fundamental skills we developed.
Good reliability requirements are going to drive our design decisions relating to the concept, the components, the materials, and other stuff. So, the moment to start defining reliability requirements is early in the design process. But, what makes a well-defined reliability requirement? There are five aspects it should cover: do you know what they are?
We’ll describe what makes a good reliability requirement and examples of common (but not good) requirements.
In today’s fast-paced manufacturing landscape, the link between product quality and supplier agreements is more critical than ever.
Custom product development can be complex, and regarding suppliers, we can uncover hidden challenges. These come up when suppliers are not aligned with the quality standards necessary for our products to be successful.
Join us as we discuss various types of supplier agreements commonly encountered in new product launches. They are important, but do they have what you need to ensure quality?
Tune in to learn how to transform your supplier partnerships into an invaluable asset in your quest for quality excellence.
Does the phrase “Subjective Probability Estimation” make you feel uncomfortable? If you’re a data-driven professional, you’re likely wary of each of those terms on their own, let alone combining them into one thing.
But we sometimes need to do it. And we can practice to get better at it.
In this episode, we emphasize the importance of subjective probability estimations in decision-making, especially in situations where concrete data may be unavailable or impractical.
We talk about:
How are quality tools Legos of development?
We talk about two philosophies of brick building and our use of the family of quality tools.
We also talk about seven uses of quality tools in product development.
Tradespeople bring expertise, innovation, high quality, and leadership to product development. If we’re lucky enough to be able to work with them, they’re an invaluable part of the engineering team.
What about when we’re working without them? How can we create a culture of craftsmanship in a company that uses a quality system?
In this episode, we talk about the crafts’ and trades’ relationship with quality systems, and steps toward creating a culture of craftsmanship.
When you perform analysis and share it with others to make a decision, do you sometimes just send the file with a blurb in an email? Only to not quite remember what you did later, when you need it most.
There’s a simple, relatively fast thing to do: a Mini Report. And it provides so much more than just jogging a memory.
Mini reports are a valuable tool for communication in engineering. By using them, engineers can enhance team collaboration, streamline decision-making, and provide mentorship opportunities to junior colleagues.
We talk about:
Celebrating a year of insights and community growth, this episode reflects on key moments, popular episodes, and the future direction of the Quality During Design podcast.
2024 included episodes focused on actionable insights, deep-dive series, expert interviews, and insightful book reviews.
With gratitude for listeners and a commitment to quality, we look ahead to new topics and collaborations for 2025.
Dianna Deeney interviews Yakira Mirabito about social dynamics within engineering and how it affects decision making. The episode focuses on improving design reviews and making them more inclusive.
Yakira explains how things like personalities and power dynamics can really affect decisions made by design teams. She gives advice to engineers on how to prepare for these reviews, such as how to give presentations effectively and encourage helpful feedback from team members. She also highlights useful tools, like the “Identity Wheel,” to help people understand each other’s backgrounds and avoid biases when making decisions. The episode is a great resource for anyone who wants to improve teamwork and create better products!
This interview is part of our series, “A Chat with Cross Functional Experts”. Our focus is speaking with people that are typically part of a cross-functional team within engineering projects. We discuss their viewpoints and perspectives regarding new products, the values they bring to new product development, and how they’re involved and work with product design engineering teammates.
Yakira Mirabito is a postdoctoral researcher at MIT whose work falls within design theory and engineering management. Her research examines how sociotechnical factors influence design decisions using quantitative and qualitative research methods. Her research interests include design behavior, cognitive biases, and social dynamics within engineering contexts. Yakira’s work enhances current design methods and tools, empowering engineers to build more innovative and equitable systems. She received her BS in Materials Science and Engineering from Northwestern University and her MS and PhD in Mechanical Engineering from the University of California, Berkeley.
Yakira’s suggestions involve awareness and evaluating our decision making, including stopping to consider if the feedback we want to accept really links back to the objective results of our projects.
