Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Product development's most valuable activity is iteration. The goal isn't to avoid failure, but to achieve it quickly and cheaply to maximize learning. A good failure uses the simplest possible prototype (e.g., duct tape and a 2x4) to answer a key question and inform the next step.

Related Insights

Not all failures are equal. Innovation teams must adopt a framework for evaluating failures based on their cost-to-learning ratio. A 'brilliant failure' maximizes learning while minimizing cost, making it a productive part of R&D. An 'epic failure' spends heavily but yields little insight, representing a true loss.

The job of an early founder isn't to be right, but to discover the truth about the market. This requires shipping imperfect products quickly to test assumptions, gathering harsh feedback, and being humble enough to accept when you are wrong.

This quote inverts the traditional view of failure. It argues that the real mistake is the opportunity cost of inaction—the products that are never tested in the market. A failed launch provides invaluable learning, whereas a product that never ships provides none, encouraging a bias for action.

As articulated by Eric Ries in 'The Lean Startup,' raw speed of shipping is meaningless if you're building in the wrong direction. The true measure of progress is how quickly a team can validate assumptions and learn what customers want, which prevents costly rework.

Foster a culture of experimentation by reframing failure. A test where the hypothesis is disproven is just as valuable as a 'win' because it provides crucial user insights. The program's success should be measured by the quantity of quality tests run, not the percentage of successful hypotheses.

Instead of starting with a blank slate, Nike's team prototypes new ideas by physically cutting and modifying existing products. This "cobbling" method enables rapid, low-cost testing of core concepts before investing in new designs and expensive molds, allowing them to fail fast and forward.

For ambitious 'moonshot' projects, the vast majority of time and effort (90%) is spent on learning, exploration, and discovering the right thing to build. The actual construction is a small fraction (10%) of the total work. This reframes failure as a critical and expected part of the learning process.

The popular tech mantra is incomplete. Moving fast is valuable only when paired with rapid learning from what breaks. Without a structured process for analyzing failures, 'moving fast' devolves into directionless, costly activity that burns out talent and capital without making progress, like a Tasmanian devil.

To truly learn from go-to-market experiments, you can't be half-hearted. StackAI's philosophy is to dedicate significant, focused effort for 1-3 months on a single idea. This ensures that if it fails, you know it's the idea, not poor execution, providing a definitive learning.

A high production rate is a core R&D tool for SpaceX, not just a manufacturing goal. By creating a "hardware rich" environment with abundant, cheaper prototypes, it enables an aggressive build-test-learn cycle. Failure becomes a low-cost data-gathering exercise, not a catastrophic setback.