Data Gathering Challenges

Abstract

Enrico and Fred discuss a listener’s question about data gathering challenges.
ᐅ Play Episode

2 HALT Objections

Abstract

Kirk and Fred discuss the value of HALT for a product late in a new product development process.

ᐅ Play Episode

Clarifying a Point About HALT

Abstract

Kirk and Fred discuss the continued meaning of the acronym HALT, which was originally coined by Gregg Hobbs, Ph.D., P.E., to stand for Highly Accelerated Life Test, which is a misnomer.

ᐅ Play Episode

Dealing with No Failures

Abstract

Mojan and Fred tackle the common engineering dilemma of what to do when a test concludes with zero failures. They discuss how to “artificially” assume a failure to benchmark against existing models and how to determine if your product is actually better than expected or if your test was simply flawed.

ᐅ Play Episode

Reasons to Model

Abstract

Mojan and Fred discuss the strategic shift from modeling as a checkbox exercise to using RAM (Reliability, Availability, and Maintainability) models as a driver for proactive decision-making. They explore how modeling forces teams to confront “the weakest link” and align resources where they can have the most impact early in a program
ᐅ Play Episode

Timely Reliability Thinking

Abstract

Fred shares insights from consulting with over 150 organizations on the perennial struggle between reactive “heroism” and proactive design. Mojan and Fred discuss the measurable benefits of investing in reliability early—such as reduced development time and lower warranty costs—and why 80% of companies still find themselves trapped in a “build-test-fix” cycle. ᐅ Play Episode

Modeling and Testing

Abstract

Mojan and Fred discuss the benefits of using failure models with testing. They explore the delicate balance between theoretical analysis and physical testing. While robust design starts with analysis, they discuss how testing serves as the ultimate “insurance policy” for decision-makers and why understanding the “Confidence Stack-up” is essential for a product’s success.
ᐅ Play Episode

One Sample Statistical Paradox

Abstract

Enrico and Fred discuss a listener’s question about using a single sample for testing.
ᐅ Play Episode

Reliability Engineering Competencies

Abstract

Enrico and Fred discuss the essential or basic skills necessary to be a good reliability engineer.
ᐅ Play Episode

Why Your Product Requirements are Slipping (and How to Fix Them)

Abstract

Mojan and Dianna explore the often-murky transition from vague product “needs” to actionable engineering requirements. They discuss where the communication gap typically develops between product management and engineering and how to close it using tools like System and Concept FMEAs. By defining failure as the “loss of key characteristics,” teams can better understand customer impact and “lift the fog” of ambiguity early in the design process.

ᐅ Play Episode

Reliability in Start-up vs. Established Businesses

Abstract

Dianna and Mojan discuss reliability in start-up vs. established businesses.
ᐅ Play Episode

Assume Bugs

Abstract

Enrico and Fred discuss the idea that no design or development project is perfect.
ᐅ Play Episode

Effective Leadership

Abstract

Carl and Fred share their experiences and advices about leadership, and why it is essential to accomplishing reliability objectives.
ᐅ Play Episode

Writing Skills

Abstract

Carl and Fred discuss the role of writing skills in conveying information to others and influencing the reliability of products and processes.
ᐅ Play Episode

Customer Expectations

Abstract

Dianna and Fred discuss the “fuzzy and shadowy” world of customer expectations, discussing how to set reliability requirements that actually keep customers coming back.
ᐅ Play Episode