In this episode I review the Anchoring Methodology. It is a method to ensure teams get the best ROI from reliability tools by creating specific points for tool outputs that connect with eh higher-level program objectives.

In this episode I discuss the tool Strategy Bounding.  Strategy Bounding allows us to make quantitative decisions regarding balancing major program and product factors like time to market, cost point, reliability, new feature development

There are so many places to find inspiration for invention and improved design. This episode starts with a story about how one of the largest companies in the world today started by finding a solution to a problem in a separate industry. I then discuss a few simple ways to use innovation to improve products early in your development process.

The earliest documented customer complaint that has been discovered is from 1750 BC. It was very specific in the issue with the product and was written and delivered in a manner that indicated the customer was very upset.  What can we learn from this dynamic of customer and merchant that has been a staple of business since the dawn of man?

I discuss the concept of "Time to Reliability."  Time to Reliability is considered the total time from design concept up until the moment when a product is in the customer’s hands performing to the standard of its reliability goals. In a traditional design process, this is often not the same as "Time to Market." A low-reliability product release will require a "Recovery" phase after the initial release.  This post-release phase demands engineering resources and great expenses to both the manufacturer and the customer. The recovery phase concludes once the product is performing to its intended reliability goals. In a highly mature product development process, Time to Reliability and Time to Market is the same and the recovery phase is rendered unnecessary.

Guests Frank Bruno and Bill Kennedy, along with myself, discuss the benefits of patenting innovations that were specifically created to increase product safety. Not only can these patents provide the documentation necessary to defend against litigation, but they can also be sufficient in deterring litigation altogether.

Frank A. Bruno is a partner at White and Williams in Philadelphia and chair of the Intellectual Property Practice Group. He is a technology lawyer who focuses on patent law.

William D. Kennedy is a partner at White and Williams. He is a trial and appellate litigator and defends companies against complex claims of injury and damage.

Bill Kennedy, from White and Williams law firm, joins me to talk about the benefits of patenting safety features. If litigation occurs from failures and consequently causes injury or property damage, the result all comes down to proving intent. If features were created specifically to enhance safety, why not patent them so that they are fully documented. This is a great foundation for building a defense case. More info on Bill at the White and Williams website.

Why are we so passionate about reliability engineering?  More specifically, why am I so passionate about it? Great question, in this episode I dive into my love for reliability engineering. As a preview, it all started at a cocktail reception. I had an interesting conversation with an executive who had no experience in product development. He asked about what I do for work and, as I described it, he saw how excited I was about reliability engineering. He even stopped me at one point just to express such.  It got me thinking afterward, "Why do I love it so much?” and “Could I explain it in a simple statement?" I think I have, listen to find out!

Mark Wirth returns to continue our discussion (from episode 7) on how to apply the best problem-solving techniques to any situation. There were so many great topics up for discussion, we just couldn’t fit it all in one episode. More on Mark at solverellc.com

Mark Wirth, a problem-solving expert, and I have a great conversation about how a complex technique should be applied to an individual problem. It's a Goldilocks situation; not too much and not too little. But how can we know before we start?  Mark describes four critical factors that can't be compromised. More on Mark at solverellc.com