The Reliability FM network

The Reliability FM network

Download on the App Store

All The Reliability FM network episodes

  • SOR 912 Using Outside Labs
    Using Outside Labs Abstract Kirk and Fred discuss the use and tradeoffs of using external environmental testing and failure analysis labs versus having in-house equipment Key Points Join Kirk and Fred as they discuss the advantages and drawbacks of a independent test and or failure analysis lab, versus stetting up an internal lab. Topics include: […]
    30 min
  • Timing Reliability in Product Design, with Jeffrey Lewis (A Chat with Cross-Functional Experts)
    Timing Reliability in Product Design, with Jeffrey Lewis (A Chat with Cross-Functional Experts)

     

    Dianna Deeney interviews Jeffrey Lewis about new product development: how timing the right activities can lead to product success.

    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.

    About Jeffrey

    Jeff is a senior director of corporate quality at Globus Medical. He’s a quality, reliability, risk management and product development professional. He is experienced at building quality into products, manufacturing processes and all business processes. Jeff is an accomplished executive with experience directing design and development and quality staff to meet company goals and objectives.

    Jeffrey and Dianna talk about:
    • The delicate balance between knowing what you know and discovering what you don’t.
    • Incorporating reliability tools like Design FMEA (failure mode and effects analysis) and TAFT (test-analyze-fix-test) into the design process to improve designs and make products more reliable and manufacturable.
    • Signs that a product development process needs improvement.
    • How, by fostering a collaborative environment, product designers can balance the pressures of completing a project within a given timeframe and still ensure the quality and reliability of their work.
    • Jeff’s wealth of experience and insights provide a roadmap for quality and reliability in product design, making it a must-listen for all in product development and design.

       

      View the Episode Transcript

      What can you do today?

      To improve the project you’re on today, remember to step-back to gain perspective of where you are on the product development journey. Do we have the right focus right now? Do we have the right understanding? Are we likely to besuccessful with this step? Is there something that we can bring to this early on? What are the biggest risks?

      Understand the knowns and the unknowns; what we have learned and what we still need to learn.

      Contact Jeff

      Jeff invites you to email him or find him on Linked-In under Jeffrey P. Lewis.

      Jeff mentioned:

      Effective FMEAs: Achieving Safe, Reliable, and Economical Products and Processes Using Failure Mode and Effects Analysis by Carl Carlson

      Reliability and Maintainability Symposium, rams.org/

       

      Other Quality during Design podcast interviews you might like:

       

      Product Design from a Marketing Viewpoint, with Laura Krick (A Chat with Cross Functional Experts)

      Product Design from a Data Professional Viewpoint, with Gabor Szabo (A Chat with Cross Functional Experts)

      Product Design with Brainstorming, with Emily Haidemenos (A Chat with Cross Functional Experts)

      Crucial Conversations in Engineering, with Shere Tuckey (A Chat with Cross-Functional Experts)

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

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

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

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

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

      Episode Transcript

      Thanks for listening.

      The post QDD 134 Timing Reliability in Product Design, with Jeffrey Lewis (A Chat with Cross-Functional Experts) appeared first on Accendo Reliability.

      0 min
    • WQW 009: JiuJitsu Style Quality
      JiuJitsu Style Quality
      The names of Six Sigma certifications were taken from martial arts. Green Belt and Black Belt sound sexy.

      But there are other things in the martial arts that could be adopted to drive continuous improvement. In particular, the idea of the “yielding art” of Jiu Jitsu where the opponents’ energy is used to defeat them. This episode discusses applying that idea in several contexts when solving problems.

      Paul O’Neill, CEO of Alcoa from 1981 to 1999 is referenced. After listening to this episode, check out these videos on YouTube. This is a leader who demonstrates how to use organizational energy to overcome obstacles and attain excellence.

      Paul O’Neill explain why safety was his leadership focus

      Paul O’Neill talking to Healthcare CEOs

      Way of the Quality Warrior podcast is hosted by Keith Fong, a Six Sigma Master Black Belt, Shainin Red X Master, and Robust Engineering Coach who has over 20 years as a continuous improvement practitioner, trainer, and coach.

      The post WQW 009: JiuJitsu Style Quality appeared first on Accendo Reliability.

      0 min
    • SOR 911 Dealing with Data
      Dealing with Data Abstract Philip and Fred discuss the first basic steps when confronted with a pile of data. What do you do with a stack of data – can you make any sense of this – please? Can you believe the analysis results? Designing systems to capture the data you need, not the data […]
      32 min
    • SOR 910 Consumable Product Reliability
      We often focus on the components and subsystems of our product when it comes to system reliability modeling. But what about consumables? The batteries, lubricants, gaskets and other things that we are going to routinely replace to keep our product going. Do we need to think about these when it comes to system reliability analysis? Hint ... yes you do.
      24 min
    • Driving Effective Conversations-Prioritizing and Decision Making at Concept Development and Beyond
      Driving Effective Conversations-Prioritizing and Decision Making at Concept Development and Beyond

      What if you could shift your approach in product design to focus on what really matters, and thereby create products that truly resonate with your customers?

      We’ve been discovering the importance of considering a variety of inputs early in the design process. Now, we navigate the challenge of prioritizing these inputs to make the crucial trade-off decisions that can make or break your product.

      We journey through the world of early concept development, discussing how setting priorities can ensure we deliver what’s truly important. We look at how these priorities can guide the product development process and how they can be adjusted when new information arises. From surprising test failures to unexpected customer issues, we explore how to reassess our priorities based on these fresh insights.

      Along the way, I’ll be sharing more tools and techniques from previous episodes to help you prioritize your ideas effectively. Get ready to enhance your approach to product design and development and create products that your customers will love!

       

      View the Episode Transcript

      Using quality tools is a powerful way to gather and prioritize design inputs. We elaborate on the importance of prioritizing design inputs to make trade-off decisions, focus efforts, and ensure that what we’re designing delivers what’s important. We also emphasize the need to reprioritize as we uncover something new in the product development process.

      When faced with an unexpected failure, going back to the priorities set can provide guidance on the next steps. I encourage allowing room to change our minds or reprioritize once we learn something new. This flexibility is key to successfully navigating the often complex product development process.

      This episode is a treasure trove of insights for anyone looking to enhance their approach to product design and development. Quality during Design’s emphasis on early prioritization and the iterative process of adjusting priorities as we learn more about the product offers a valuable framework for creating products that resonate with customers. By incorporating these insights into the design process, businesses can ensure they are delivering products that truly meet customer needs.

       

      Other Quality during Design podcast interviews you might like:

      After the ‘Storm: Compare and Prioritize Ideas

      Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds

       

       

      Episode Transcript

      Hi, I’m Dianna Deeney. We are talking about product design and new product development and working early with our cross-functional teams to be able to get the design inputs that we need when we’re actually designing things and making decisions. Now we have so many inputs and I’m asking you to expand that a little bit and get a little more inputs. Well, which ones are important? Is it the most technical input? Is it the features that our competitors have that we don’t yet? How do we prioritize all these different kind of inputs? Let’s talk more about that after the 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 on how to apply quality during design to their processes. Listen in and then join us Visit qualityduringdesign.com.

      At Quality During Design, we talk about early concept development and using quality tools in order to explore the concept space with our cross-functional team to be able to get those design inputs. Using quality tools is a way to self-advocate and enable ourselves, the product design engineers, to be able to get those inputs at the time that we need it, the time that we’re making decisions about the product design, along with being able to have a framework to work against when we don’t even have a product design yet, which is something that quality tools do. And they’re also visual, so it is easier to facilitate a discussion with a group and focus on a particular area of our concept space when we’re using quality tools.

      The other benefit of using quality tools in this space is that they have a built-in way to help you prioritize those different inputs that you’re gathering. Now, why would we want to prioritize ideas in concept development?

      • Well, we want to be able to prioritize design inputs to make trade-off decisions. We can have this or we can have that. We can’t have both, so which one is more important? Being able to prioritize can help bring clarity to that kind of decision.
      • It will also help us focus our efforts. We only have so much limited time, effort and resources to be able to accomplish tasks. Maybe we don’t have enough of those kind of resources to be able to develop all the things. So having a priority of design inputs that we want to focus on helps us focus our efforts.
      • It also helps ensure that whatever we’re designing delivers what’s important. We may have a lot of customer inputs. Prioritizing will help us understand which of those is most important for our customer.
      • These kind of priorities also helps us set up reliability goals, because we’ll understand the use environment, the use space, we’ll understand what the expectations are and we can set up reliability goals appropriately based on the priority.
      • And understanding the priority of things also helps us communicate with the manufacturing, production or the suppliers. It can help us choose the manufacturing method or the production method that will help us meet the requirements.
      • We can prioritize these things really early in concept development, when we’re still exploring the problem space for design inputs. When we’re looking at customer experiences in the concept space.

        • When we’re looking at benefits, potential benefits that this new product could give to our customers, we can prioritize those benefits based off of a customer satisfaction rating.
        • When things don’t go right, when we have a potential problem our customers might be experiencing a potential symptom based off that problem, we can start to prioritize those kind of design inputs based on risk, the severity of the impact to our customer and the likelihood that it could occur.
        • And when we’re examining the use process in the concept space, which is the task that our user is trying to take to get from point A to point B all the different steps and interactions they potentially have with their product we can prioritize those process steps in other ways. What is critical to quality? What is value added? Who is doing what when? And can we make that easier? Are there mistake-proofing things that we could do?
        • I’m promoting making priority decisions early, but what if we make a mistake in setting a priority early in concept development? What if we uncover something new? Well then, we need to reprioritize. Product development processes aren’t a static thing. We do want consistency throughout the product development process. That makes things easier, but we also need to allow ourselves room to change our minds or reprioritize once we learn something new.

          As an example, we do a product test and we get a phone call from the lab to investigate a failure which was really unexpected. We didn’t expect this kind of failure. It’s something new. We haven’t seen it before.

          So what do we do in that case? We don’t want to ignore it. We need to do something about it, understanding what action we want to take or what we want to do. It really depends, doesn’t it? Going back to the priorities that we’ve set, it helps. Why was it given the priority that it had, and now that we’ve learned something new, does that change its meaning?

          If we get to a point where we’re comparing ideas against each other, there are other methods of prioritizing and I covered those in a previous episode called After the Storm: Compare and Prioritize Ideas. In that episode I talked about Paired Comparison Prioritization Matrices and DMRCS, another systematic way that we can evaluate options.

          What’s today’s insight to action? We can start prioritizing design inputs and ideas at concept development and then we iterate and adjust as we learn more about our product through the product development process. At least setting a starting point at concept will help us do all those things that prioritizing helps with to help us make trade-off decisions and focus our efforts and deliver what’s important. Using quality tools to help explore concept development not only helps us work with our cross-functional team on ideas, they also help us prioritize those ideas so that we can work appropriately. I did mention a previous podcast episode that related, called After the Storm, and I will link to that in the podcast blog for this episode. This has been a production of Deeney Enterprises. Thanks for listening.

          The post QDD 133 Driving Effective Conversations-Prioritizing and Decision Making at Concept Development and Beyond appeared first on Accendo Reliability.

          0 min
        • SOR 909 Assumptions and Analysis
          Assumptions and Analysis Abstract Philip and Fred discuss a fundamental element of all statistical analysis. Key Points Join Philip and Fred as they discuss Topics include: Every analysis or model has assumptions – understand them first Check the assumptions Assumptions are not true because we wish they were Enjoy an episode of Speaking of Reliability. […]
          25 min
        • SOR 908 Why is Reliability a Process?
          Why is Reliability a Process? Abstract Carl and Fred discuss the process of reliability, which also happens to be the name of their new book. They answer the question “why is reliability a process”? and discuss what happens if reliability is only approached as a series of methods. Key Points Join Carl and Fred as […]
          24 min
        • Driving Effective Conversations-Three Major Aspects to Consider for DfX
          Driving Effective Conversations-Three Major Aspects to Consider for DfX

          Gain insights into working effectively with cross-functional teams, collecting invaluable design inputs without succumbing to the overwhelming flow of information.

          We’ll discuss the magic behind the ‘concept space’, an efficient approach to dissect potential customer experiences, streamlining concept development at the start.

          What about after that high-level concept development, when we begin our engineering design?

          Early engineering diagrams can prove instrumental in evaluating modularity, layout, and interactions in product design with a team. Dianna guides us through part of a Quality During Design course lesson, shedding light on how these diagrams can be used. Each function has a different reason to look at these three aspects of product design, and it’s worth asking to help us achieve Design for Excellence.

          Learn how the collective wisdom of these teams can influence design choices, ensuring that the final product appeases both the internal and external customers. So, buckle up for this enlightening episode as we demystify product design and stress the crucial role of a synchronized team effort.

           

          View the Episode Transcript

          Product design is an intricate, complex process that demands effective collaboration. Engineering concept diagrams can help in evaluating modularity, layout, and interactions in product design. These diagrams help visualize the different components and interactions of a product design. Collective inputs from teams can significantly influence these design choices. It ensures that the final product appeals to both internal and external customers, leading to a more successful product in the market.

          This episode demonstrates that successful product design is not just about the individual designer’s creativity but also about effective teamwork and the collective wisdom of the team. It shows that a synchronized team effort is crucial in navigating the complex web of product design.

          Whether you are a product designer, a quality professional, or anyone interested in the field of product design, the insights and strategies shared in this podcast episode can significantly enhance your understanding and practice of product design. It’s a journey through concept and collaboration, unraveling the intricacies of product design, and highlighting the power of teamwork in navigating product design.

          Other Quality during Design podcast interviews you might like:

           

          Foundations-Understanding Cross-Functional Collaboration

          Driving Effective Conversations-Taking the Lead in Working Meetings

          Video background designed by Freepik.com

          Episode Transcript

          Welcome back to the Quality During Design podcast. I’m Dianna Deeney. Product designers have a lot of customers, internal and external. What are ways to approach concept development that helps us work with our cross-functional team and get design inputs without getting overwhelmed and without it taking forever? 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 and 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 on how to apply quality during design to their processes. Listen in and then join us. Visit qualityduringdesign.com.

          We’ve been talking about staying in the problem space longer for concept development, working with our cross-functional team to develop design inputs the information that we’ll use to actually design against. There are many ways to design for external customers. Quality during design uses a concept space to help you focus on one customer aspect at a time. When things go right with our product, what are the benefits that our customers see and experience? When things don’t go right, what are the symptoms that our customers experience and when they’re using our product, what’s it like? Where are the hangups? Where could mistakes be made? What are ways that we can streamline and make things better Within this concept space? We’re using ideas like benefits, symptoms and the potential use process to evaluate a concept, an idea. We haven’t started engineering design yet. We are really working with some of the what-ifs, but also some of the targets the things that we want to go for, the competitive advantages that we want to target, the things that we’ve noticed about our old versions of products that don’t work out so well, the things that our cross-functional team sees or understands from existing customers or from our new customer base that affect the way that we design the product. Designing to a concept space with our cross-functional teams helps us to develop those design inputs early in concept development.

          Those are some of the first steps that we can take with our cross-functional team to develop those design inputs. We don’t just leave those ideas or those concepts at concept development. We take what we’ve learned and we iterate on them throughout the product development process. In this way, we’re able to continue the conversation with our cross-functional team and we’re able to continue to get decisions based off of good information that early, fact-based concept development will help us throughout product development and we’ll be able to evaluate things based on our customers’ experience and the priorities that we want to target for those.

          Once we start designing, to really design for excellence, we need to continue to check in with our team specifically about our designs, modularity, layout and the interactions that it has with itself, with the different modules and also with the external environment. I’m going to share with you a little bit of one of the Quality During Design courses. This course talks about using specific types of diagrams, specifically a schematic, a geometric layout and an incidental interactions diagram to look at these three aspects of any new product design its modularity, its layout and its interactions. Engineers will create these kind of diagrams. The idea is to review them with our cross-functional team.

          The part of this course that I wanna share with you today is what kind of input or what kind of effect the cross-functional team’s opinions might have on these three things, these three aspects of our new product design. By understanding why we might want to change our design depending on our cross-functional viewpoints and their input, we’ll gain a better understanding of what kind of questions to ask and what kind of open-minded learning we want to maintain when we’re working with our cross-functional team on our new product design. Let’s get into sharing part of that lesson.

           

          What kind of design choices are we really making from these diagrams? These diagrams really explore three aspects. It’s exploring the modularity of a design. It’s layout of components and parts and the interactions that we have with them. Interactions are coming from our schematic the first drawing that we create and the incidental interactions are the things we’re considering after a geometric layout. With those two diagrams, we’re considering both the fundamental interactions and the incidental interactions.

          Why is it so important for us to use these diagrams to develop engineering designs at a concept phase early? Because it takes a team to deliver a product. Our goal is to guide them through working meetings to get their input into the design itself. We’re using these three concept development tools to talk more about specific parts of the product’s features and characteristics, but doing it in a way that lets us explore design choices before we go too far down the path of engineering solutions. Sometimes that learning is an aha moment. Other times it will bring up more questions. It’s our responsibility to ask, because they are the internal customers of our design choices or they represent our end users, which are our external customers. They are going to be giving us input into the product design, what needs to happen for the customers and to be able to make this be made with a certain level of quality.

          When we create these three diagrams and look at these three areas modularity, layout and interactions and we work with our team, we can think of each of our teammates and think of what each can provide us in terms of design inputs.

          First, let’s start with our customer-facing teammates. This could be sales and marketing, customer service field operations anyone that has an understanding of the customer themselves and also where it is they are working in the use environment. With modularity, something they may come to the table with or have thoughts about is product variety. Are you designing and developing something where the customers are expecting to be able to upgrade or to have a different level of product, like a bronze, silver and a gold, where they can upgrade different modules of the product design in order to get different benefits from it? Modularity could also affect the interchangeability of things too, if you think of disposables and service, repairs and other upgrades. What kind of capabilities do we want to offer the customers there? Our customer-facing teammates may have some strong opinions about that. Regarding the layout of this design concept, they come to the table knowing a bit about the competitive products. How do the competitive products meet the customer needs? That might affect what users expect to be able to do, and is there an existing difference between what they currently do and what they really wish they could do? Our customer-facing teammates may also look at layout and think about the interfaces of our user human and maybe other products within the use space and as far as interactions, they may be very familiar with the use environment, with the extremes that this product is going to be working in, or with service and handling and delivery. They want to be able to deliver it easily, not need a refrigerated truck, for example. These are some of the perspectives that our customer-facing teammates may have about this new product design and definitely design inputs that we want to be able to capture and design against.

          Let’s next look at reliability. They do a lot of tests to learn and they verify that the product is reliable. With our schematic and its modularity, they’ll be thinking about what are the risks, what’s new, what’s different and what’s unknown. What are the reliability goals for the whole system and are there particular modules that need to be more reliable than others and what are trade-offs? Reliability engineers may help with redundancy and apportionment, which are things that are affected by the modularity With interactions. Reliability engineers are going to be looking at the use environments. They’ll want to be able to plan reliability analyses and testing that may affect the modularity and layout of the product.

          Next, let’s talk about our cross-functional teammates involved with production. This is manufacturing and procurement. They’re working with suppliers. They’re making sure that the product can be made. Our production teammates are thinking about design for manufacturing how might it be manufactured in modules and what manufacturing processes would be needed. They also think about the capability of this being able to be produced. What tolerances would be needed, what kind of resources would be needed and do we have them or do we not have them? Would we need to outsource them and what risk would that introduce? And they also look at costs. Even with the incidental interactions, they’re going to be looking at what’s new and different and unknown and seeing if there’s any special handling and storage requirements or maybe even manufacturing environmental needs. An example of that would be clean rooms for cleanliness, rf shielding for electronic assemblies.

          Our quality teammates are going to be looking at our new product design concept with respect to quality, processes and transfers, controlling variation and controlling risks, and they bring knowledge about production benchmarks and capabilities. Some quality teammates take a very broad approach to product development and they’re looking at the transfers of information and parts between development and production and the business. They’re interested in learning what the overall quality goals for this new product are and about how we’re going to meet them. Things like what quality measure is defined by a module, where are natural breakpoints to assess the quality of the product, where might we have new suppliers and where might we be stretching the limits of our current suppliers, where our user interface is with this system and what quality measures are the users themselves defining. They may also be thinking about how to design with testing in mind, either in process testing or final testing, or even testing that happens in the field after release. These are a few of the things that the quality person on your cross-functional team might be thinking about with new product development.

          And finally, project management. Someone has to coordinate everybody to get the project done. They bring knowledge about the development capabilities what are the resources and the costs and the timelines and those are usually constrained. The product design modularity may affect project management. Maybe different teams need to be working on different modules in order to meet the market need in the time the company needs to meet it. Project management decisions are also affected by the product layout and the interactions of the product.

          And finally, we share and then we iterate these diagrams for design, for excellence.

          I hope this episode today gave you a different appreciation for the kind of values your cross-functional team might have toward your product design decisions.

          If you want to learn more about these three different kind of diagrams and how to work with your team on them or with any of the other quality and reliability tools we talk about in early concept development, contact me at QualityDuringDesigncom. This has been a production of Deeney Enterprises. Thanks for listening.

          The post QDD 132 Driving Effective Conversations-Three Major Aspects to Consider for DfX appeared first on Accendo Reliability.

          0 min