It’s been said, “Hardware is hard.” There are obviously real challenges with component lead times, engineering resources, cash flow, and Murphy’s Law out to derail development at every turn, but can these difficulties be mitigated? Is “Murphy’s Law” actually due to a lack of defined requirements or foresight about what could go wrong?
In this session, two seasoned product development professionals will be looking at the hardware design cycle and how development risks can be mitigated through engineering analysis and testing during the early development phases. Attendees will walk away with ideas for how to approach their own physical product designs:
•How to effectively capture and communicate requirements
•How to uncover issues early to prevent late-state development derailments
•How to design in ‘hooks’ to more easily resolve late discovery of issues