True innovation isn't about brainstorming endless ideas, but about methodically de-risking a concept in the correct order. The crucial first step is achieving problem clarity. Teams often fail by jumping to solutions before they have sufficiently reduced uncertainty about the core problem.

Forget the linear waterfall or even the classic design loop. Dylan Field sees today's best product teams using a non-linear process, 'hopping' between ideation, design, prototyping, and code in any order. The key is the ability to start anywhere and move fluidly between these stages.

Starting with limitations like budget and feasibility (convergent thinking) kills growth and leads to repetitive outcomes. You must begin with an expansive, divergent phase to generate a wide pool of ideas before applying any constraints.

Conventional innovation starts with a well-defined problem. Afeyan argues this is limiting. A more powerful approach is to search for new value pools by exploring problems and potential solutions in parallel, allowing for unexpected discoveries that problem-first thinking would miss.

Large companies often identify an opportunity, create a solution based on an unproven assumption, and ship it without validating market demand. This leads to costly failures when the product doesn't solve a real user need, wasting millions of dollars and significant time.

The common product development process is a sequential handoff model. A better approach is a "jazz band" model where cross-functional teams collaborate harmoniously from the start. This fosters creativity and reduces rework by including engineers in early ideation, rather than treating them as a final step.

Without a strong foundation in customer problem definition, AI tools simply accelerate bad practices. Teams that habitually jump to solutions without a clear "why" will find themselves building rudderless products at an even faster pace. AI makes foundational product discipline more critical, not less.

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.