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.

Key Points

Join Mojan and Dianna as they discuss the critical alignment needed between product vision and technical execution, and how shifting the perspective on failure can lead to more robust requirements.

Topics include:

Strategic FMEA: Utilizing System and Concept FMEAs in the concept space to guide early decision-making while the design is still fluid, rather than waiting for a final check.
Failure as Benefit Loss: Shifting to a “benefits approach” where failure is redefined as the loss of key characteristics. This focuses the team on the specific features and value a customer loses when a product underperforms.
Lifting the Fog: Bringing cross-functional teams together to trace how the loss of these characteristics leads to technical causes, ensuring requirements are clear, data-driven, and aligned with customer impact.

Enjoy an episode of Speaking of Reliability. Where you can join friends as they discuss reliability topics. Join us as we discuss topics ranging from design for reliability techniques to field data analysis approaches.