Get your free personalized podcast brief
We scan new podcasts and send you the top 5 insights daily.
Instead of creating an intermediate, 'half-step' product, commit to the harder but optimal solution if a plausible path exists. This avoids the wasted effort and sunk cost fallacy of a circuitous development path, even though it requires more upfront investment and conviction.
Related Insights
To de-risk innovation, teams must avoid the trap of building easy foundational parts (the "pedestal") first. Drawing on Alphabet X's model, they should instead tackle the hardest, most uncertain challenge (the "monkey"). If the core problem is unsolvable, the pedestal is worthless.
To avoid accumulating sunk costs on doomed projects, solve the most difficult, uncertain part first (the "monkey"). Avoid easy tasks (building "pedestals") that create a false sense of progress. This framework, from Google's Astro Teller, forces an early confrontation with a project's core viability.
Instead of a full rewrite, identify the specific pain points of a legacy system (e.g., a command-line UX) and solve them with minimal development. This delivers immediate value, reduces risk, and validates the market need for a larger investment later, preventing a costly failure.
Founders resist necessary pivots due to sunk costs. To overcome this, use the 'Day Zero' thought experiment: If you were dropped into your company today with its current assets, what would you do? This clean-slate mindset helps you make the hard, fast pivots required to find a real problem.
Unlike software, hardware iteration is slow and costly. A better approach is to resist building immediately and instead spend the majority of time on deep problem discovery. This allows you to "one-shot" a much better first version, minimizing wasted cycles on flawed prototypes.
Aspiring founders often stall while waiting for a perfect idea. The most effective strategy is to simply pick a decent idea and build it. Each project, even a 'losing' one, provides crucial learnings that bring you closer to your eventual successful venture.
To de-risk a new idea, first anchor it in elements that are *Proven* to work in the market. Then, add a feature that is clearly *Better* for users. This isolates your *New* high-risk innovation, increasing the odds of success by not failing for the wrong reasons.
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.
For net-new products, begin with deep problem discovery. Once a product is introduced, shift to rapid, solution-based iteration and feedback. As the product matures, revert back to problem discovery to find the next growth engine while optimizing the current product.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.
