Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value
Source: https://www.producttalk.org/continuous-discovery-habits/ ↗
Torres turns the vague practice of "talking to users" into a weekly rhythm: interviews every week, opportunity solution trees, assumptions framed as testable hypotheses, and a discipline for getting from conversations to decisions without romanticising either side.
The book is operational in the best sense — it is mostly about habits, cadence and the small rituals that make discovery survive the pressure of delivery.
For product direction it is one of the cleanest arguments against the false choice between discovery and delivery; Torres shows how a team runs them in parallel without either starving the other.
A useful companion to Blank's customer development in its more ritualised form, and a book to hand every PM on the team.
Central argument
Torres argues that product discovery should not be an occasional project or a pre-launch phase but a continuous weekly discipline built around three interlocking habits: interviewing at least one customer per week, mapping opportunities onto a structured opportunity solution tree, and treating assumptions as explicit hypotheses to be tested before committing to solutions. The central thesis is that discovery and delivery are not competing demands requiring a trade-off but parallel activities that a team can sustain simultaneously through cadence and ritual rather than heroic effort. The book's claim is essentially operational: the reason most teams do discovery poorly is not lack of intent but lack of repeatable structure.
Critique
The framework assumes a degree of organizational stability and team autonomy that many product teams do not have — weekly customer interviews require consistent access to users, a team with scheduling discipline, and a culture that tolerates inconclusive learning cycles, none of which Torres interrogates seriously as preconditions. The opportunity solution tree, while elegant, can also create a false sense of analytical rigour: the quality of the tree depends entirely on the quality of the underlying interviews, and the book is more prescriptive about the cadence of conversations than about what makes them epistemically sound. Teams in regulated industries, B2B enterprise contexts with limited user access, or organizations under intense delivery pressure may find the method coherent in theory but structurally difficult to instantiate without significant prior organizational change.
Why it matters for product
For a CPO, the book's most actionable contribution is its argument that discovery debt accumulates the same way technical debt does — invisibly, until it collapses into a strategic misjudgement — which reframes the case for continuous discovery as a risk management argument rather than a process preference. The opportunity solution tree gives product directors a concrete artifact for aligning teams around outcome-framing before solution-framing, directly addressing the common failure mode where squads optimize locally toward features while losing sight of the customer problem space. It also provides a practical structure for coaching PMs: instead of reviewing outputs, a CPO can review the tree and the underlying assumptions, making product thinking auditable without micromanaging execution.