Innovation requires moving beyond a 'failure culture' to an 'anti-fragility' mindset. This means proactively pushing boundaries with the expectation that a percentage of work will fail, then using that failure to fundamentally adjust your thinking and become stronger.

True agility stems from a mindset that values lessons learned above successful outcomes. By adopting a bias for action and being willing to fail—especially when experimenting with new technology—individuals can adapt and grow faster. The goal becomes the lesson, not the win itself.

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.

In operations, failure is a problem to be eliminated. In innovation, where new ground is being broken, failures are expected and necessary. Instead of being viewed as mistakes, they must be reframed as valuable data points that provide crucial learnings to guide subsequent experiments and decisions.

Much like a failed surgery provides crucial data for a future successful one, business failures should be seen as necessary steps toward a breakthrough. A "scar" from a failed project is evidence of progress and learning, not something to be hidden. This mindset is foundational for psychological safety.

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.

Equating unexpected results with failure creates a culture where learning is impossible. Eric Reiss argues against the 'celebrate failure' mantra. Leaders should instead frame success as the efficient and scientific discovery of what works and what doesn't, viewing incorrect hypotheses as necessary steps toward a breakthrough.

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.

To validate core assumptions quickly, structure your first real-world test for speed, not success. Even if you're confident it will fail, the learnings from a rapid first attempt—on suppliers, regulations, and execution—are far more valuable than prolonged planning for a perfect launch.