At NASA, the design process involves building multiple quick prototypes and deliberately failing them to learn their limits. This deep understanding, gained through intentional destruction, is considered essential before attempting to build the final, mission-critical version of a component like those on the Mars Rover.

Instead of focusing on the happy path, start design by asking, 'What is the absolute worst thing that could happen to a user?' This 'disaster thinking' approach forces you to work backward from the highest stakes, revealing critical failure points and ensuring you build a more resilient and safe service.

Synchrony Medical discovered a major flaw in their vest not in a lab, but by watching people try to put it on themselves. Observing this unassisted, real-world task revealed the air tubes were a tripping hazard, prompting a crucial redesign that would have been costly to fix later.

The principle of universal design argues that solving for extreme use cases uncovers fundamental problems that benefit all users. Curb cuts made for wheelchairs help people with strollers, and lighter body armor designed for female soldiers proved superior for many male soldiers.

Beyond gathering user feedback, a key purpose of a physical prototype is destructive testing. Winnebago's PM intentionally pushed their prototype to its limits on harsh terrain, causing failures that revealed critical weaknesses that could then be engineered out before full production.

For connected products like Apple's AirTag, traditional testing for functionality and accidental misuse is insufficient. A critical new dimension is testing for intentional, malicious use, such as stalking. This requires product teams to adopt an adversarial mindset and build safeguards against ways their products could be weaponized by bad actors.

Drawing from service dog training, building trust requires designing for the edge scenario, not the average use case. A system's value is proven by its ability to handle what goes wrong, not just what goes right. This is where user confidence is truly forged.

A powerful engineering motivation is the fascination with how complex systems fail. By studying failure modes, especially in safety-critical devices, you can design more resilient and fail-safe products. This perspective treats engineering as a "language" for understanding and improving system behavior, rather than simply building things.

A pilot program for a new product or service that runs perfectly is a failure because it has not uncovered the real-world vulnerabilities that need fixing before a full-scale launch. The goal of a pilot should be to actively seek out and document these "intelligent failures" to ensure the final launch is a success.