The Rise of Modern Product Discovery

Torres argues that product delivery has matured through Agile, continuous integration, and story mapping, while product discovery, the work of deciding what to build, has lagged behind. She contrasts the traditional requirements-gathering model, built on assumptions of predictability, certainty, and business-centered thinking, with modern discovery approaches like design thinking, Lean Startup, and jobs-to-be-done that start from customer needs and assume ideas are wrong until tested. Her central point is that teams often adopt modern discovery tools such as A/B tests and usability studies without adopting the underlying assumptions, which leaves most of the value unrealized. She closes with diagnostic questions for readers to test whether they are truly doing modern discovery.

01Key takeaways

• Separate discovery (deciding what to build) from delivery (building it), and invest in discovery practices with the same rigor as delivery.
• Question the assumptions behind your process, such as predictability and certainty, not just the tools you use.
• Test ideas early with prototypes or concierge experiments instead of only running A/B tests after building.
• Co-create with customers frequently, ideally weekly, and observe their behavior rather than relying only on their stated wishes.
• Measure success by delivered value rather than hitting committed features and dates, and be willing to scrap ideas that fail experiments.

02Key sections

Delivery has matured faster than discovery

Agile, continuous integration, and user story mapping have made building software far more iterative and efficient. Discovery, deciding what to build, has adopted new philosophies much more slowly and unevenly.

Limits of the traditional discovery process

The traditional model of collecting ideas, funding projects, and gathering stakeholder requirements rested on faulty assumptions that software is simple, the future is predictable, and outcomes are certain. These assumptions caused delays, scope creep, and products that missed customer needs.

New assumptions behind modern discovery

Modern approaches center the customer, assume initial ideas will be wrong, test ideas iteratively with prototypes or concierge experiments, and invest further only as evidence warrants.

Adopting tools without the mindset

Teams often copy the tools of modern discovery while keeping feature roadmaps, fixed dates, late-stage A/B tests, and reliance on what customers say rather than what they do. This yields only a fraction of the benefit.

Self-assessment questions

Torres offers diagnostic questions about roadmaps, experimentation timing, co-creation frequency, and whether ideas get scrapped based on evidence, to help readers gauge how modern their discovery really is.

03From the post

“I love that Marty Cagan and Jeff Patton have long been advocates of dual-track development. Their efforts have helped to shape the ongoing conversation about the evolution of product discovery. If you aren’t familiar with dual-track development, it’s the separation of product discovery from product delivery.”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.