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.

A failure results from ambitious, planned efforts that don't succeed—a noble outcome. A mistake, conversely, is a rash, sloppy decision made without self-awareness that typically leads to regret. This distinction allows for learning from failure while systematically avoiding simple mistakes, reframing how we view setbacks.

Koch Industries encourages risk-taking by defining a "good experiment" not by its success, but by its learning outcome. A failure is considered valuable and is rewarded if what the company learns from it is worth more than the cost of the experiment itself, fostering a culture of true innovation.

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.

In a new technological wave like AI, a high project failure rate is desirable. It indicates that a company is aggressively experimenting and pushing boundaries to discover what provides real value, rather than being too conservative.

Reflecting on his PhD, Terry Rosen emphasizes that experiments that fail are often the most telling. Instead of discarding negative results, scientists should analyze them deeply. Understanding *why* something didn't work provides critical insights that are essential for iteration and eventual success.

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.

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.