3 Best Practices for Adopting Continuous Product Discovery

Teresa Torres argues that many product teams believe they already practice discovery, but they run interviews, usability tests, and A/B tests too infrequently and mostly to validate decisions already made. She defines continuous discovery as weekly customer touchpoints by the whole product team, conducting small research activities aimed at a specific product outcome. Using a case study of two product teams at Arity, a subsidiary of Allstate, she shows how a consumer team and an enterprise team adopted weekly interviews, rapid prototyping, and experiments despite starting with no customer contact. The piece matters because it offers a practical, team-level benchmark and shows that organizational obstacles can be chipped away at incrementally.

01Key takeaways

• Talk to customers every week, even informally, rather than waiting for formal research cycles.
• Try many recruiting methods, then automate the ones that work so interviews appear on the calendar without effort.
• Prototype with the cheapest medium available, such as whiteboards, slides, or simple wireframes, and change it every week.
• Design experiments around the riskiest assumption and ask what can be learned this week.
• When interview and experiment results conflict, treat the gap as a new research question rather than picking one signal.
• Chip away at organizational obstacles with stakeholders by explaining methods and running small successful tests.

02Key sections

Defining continuous discovery

Discovery is the set of activities deciding what to build, while continuous discovery means the whole product trio talks to customers weekly in small research activities tied to an outcome. Research should be bite-sized rather than big-project work.

The Arity case study

Torres introduces a company in a regulated, slow-moving culture and two product teams, one consumer and one B2B, both new to regular customer contact. Their contrasting contexts show the approach applies across settings.

Continuous customer interviews

Teams began with informal 'research in the wild' conversations and brief interviews, then automated recruiting through screeners, support triggers, and sales pipelines. Doing things that don't scale comes first.

Continuous rapid prototyping

Teams split interview time between generative questions and testing prototypes, starting low-fidelity such as whiteboards, Balsamiq, or pitch decks, and iterating weekly. A prototype is any artifact that yields qualitative feedback, including what-if scenarios.

Continuous product experiments

Experiments start from explicit predictions targeting the riskiest assumption, such as desirability, feasibility, or viability. Landing page tests and data feasibility checks let teams learn in weeks rather than months, and overcoming internal objections is part of the work.

03From the post

“It’s easy to think you already do continuous product discovery. Most of the teams that I work with come into coaching thinking that they don’t need help. They’ve read the industry books, they attend the popular product conferences, and they follow all the leading blogs. They’ve”

04Frameworks mentioned

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