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.
I’ve mentioned in previous episodes that it’s best to do FMEA early in the design concept phases of development.
Well, if we do FMEA early, then what can with do with it?
We explore a bit how to study any risk analyses (system risks, FMEA, hazard analysis) to help design-out problems, set-up design inputs, and help us figure out test methods. We also talk a bit about why a team is a necessary part of risk analyses.
We can develop a severity rating scale based on us: our company, our customer, our product… And we can relate the categories that we use to the quality dimensions that matter to us.
We talk about the 7 principal quality dimensions of goods and services, the 5 principal dimensions of quality in customer service, and how we might customize our severity scale based on these dimensions.
A force field analysis is a tool in the quality toolbox. Its typical use case is to help a team analyze a change by understanding the forces involved. We can also use it to help us solve a problem.
We can use a force field analysis to understand nuances or to get a handle on a change that involves many different people or departments.
We envision a force field analysis as a football field during a game. Listen-in and then gather your team and try it out for your next change!
There is a lot of use information about a new product concept that we can develop, even if we don’t have an engineering prototype. We want this information especiallybefore we start prototyping!
We talk about what type of information we can gather and a stepwise approach to get it with our cross-functional team.
Finite Element Analysis (FEA) is not a substitute for product test.
It can be used as a supplement to design and test.
There are lots of ways to use it during design: to evaluate differences in prototype options, as test inputs, and even to help with root cause analysis.
We talk about FEA and when to work with Quality Engineers and Reliability Engineers for next steps.
Cross-functional teamwork is so important for product design. Our team is integral in understanding all of our customer’s needs: internal and external customers.
Remote work and social distancing have affected how we do our work, and how we communicate with our cross-functional team. Now, we’re starting to get back into “normal’ routines.
There are important lessons learned about the way we work. We talk about just a couple of perspectives that could affect how design engineers work.
We don’t just rely on the numbers – we always plot the data!
We review how we use plots to look past the numbers, and to be aware of common gotchas!
Supplier control plans and design specs can go hand-in-hand in the quest for quality.
Control plans aren’t just for quality professionals! Learn how partnering with suppliers for a simple control plan can benefit your design process.
Our manufacturing friends are approaching us with a problem.
They want to test the product during manufacturing. The way the product is currently designed doesn’t let them do this, or not easily.
Can we make a design change so they can test?
Imagine that they’re coming to us with this question before we’ve completed the design. Can they really see the future?
Perhaps, with strategic use of FMEA. We talk through a scenario of how to do it.
We’re heading into pilot production.
We’ve got to finish those design specs and engineering drawings!
Before you pass it along, have you identified what features are critical? Does it align with managing risk? And are you communicating that effectively on your specs and drawings?
Creating design specs is an important part of engineering design. We review a way to choose critical design features, based on risk.
We can get stuck when trying to discover a solution to a problem.
We talk about a Nine Windows tool and TRIZ – more thought-provoking methods that we can use to get unstuck and move on to the next step.
We can get stuck when trying to discover a solution to a problem. Sometimes it helps to expand our thinking into other avenues. We can reframe our problem within its contradictions. What is it not?
We review an Is/Is-Not Matrix: how it’s built, its purpose, and how it can help us.
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.
As a design engineer, you’re tasked with translating vague customer statements into something technical and measurable. And you also need to identify what requirements are important: filtering the “must meet” requirements against the “should have” requirements. And, finally, you need to do this with your cross-functional team.
What if you miss something important?
It’s difficult. There is a method that we can use. Let’s talk about the House of Quality and how you can use it no matter where you work.
If you have quality friends, you may have heard of Gemba. What is Gemba and can it help with product design?
Gemba is an ideology.
And, yes, it can help with product design!
We explore how and talk about why you might want to adopt the term “Gemba” for product design engineering.