Systems Playbook

Continuous Discovery Habits (Teresa Torres)

Main Argument

Product discovery should be a continuous habit, not an upfront phase: a product trio (product manager, designer, engineer) staying in weekly contact with customers and letting that steady evidence shape what they build. The book supplies the operating rhythm and tools, structured customer interviews for needs, the opportunity-solution tree, and assumption testing, that make "decide what to build, and validate it, before building" sustainable week over week. It is the methodical "how" beneath Inspired's "what and why," and the second source that turns continuous discovery from a stance into a practice.

Key Takeaways

  • Discovery is continuous and owned by the product team, woven into the delivery cadence, not a separate research phase that ends before building begins.
  • Anchor discovery on a clear outcome, then explore the opportunity space, customer needs, pains, and desires, before jumping to solutions.
  • The opportunity-solution tree makes the reasoning visible: outcome at the top, branching into opportunities, then candidate solutions, then assumption tests.
  • Interview for needs by collecting specific stories of past behavior, not opinions or hypotheticals; what people did is evidence, what they say they want is not.
  • Generate several solutions per opportunity rather than committing to the first idea, to make a real comparison possible.
  • Test the riskiest assumptions behind a solution quickly and cheaply, rather than building and testing whole solutions.
  • The product trio decides together, sharing context across product, design, and engineering instead of handing research between functions.

Concepts Extracted

Enriched