Torres operationalizes what Cagan describes. Weekly customer touchpoints, opportunity-solution trees, assumption testing — this is the most practical account of how discovery actually becomes a habit rather than a quarterly exercise. Pairs directly with Inspired as the how to its what.
Torres, a product discovery coach, wrote a practical method for how product teams should decide what to build, aimed at replacing occasional research projects with a continuous weekly practice.
Her central structure is the opportunity solution tree. At the top sits a single outcome the team is trying to achieve, expressed as a behaviour change in customers rather than as a business metric or an output. Below it sit opportunities, meaning the customer needs, pain points and desires discovered through interviews, organised into a structure that shows how they relate. Below each opportunity sit candidate solutions. Below each solution sit the assumptions that must hold for it to work, which are what tests are designed against. Torres argues that teams jump from outcome to solution without mapping the opportunity space, which means they compare a solution against nothing rather than against alternatives.
The practices she prescribes are specific. Interview at least one customer every week, conducted by the trio of product manager, designer and engineer together rather than delegated to a researcher. Ask for stories about specific past instances rather than for opinions or generalisations, because people describe what they actually did more accurately than what they generally do. Generate at least three solutions for any opportunity before evaluating any of them. Identify the assumptions behind each solution and test the riskiest first with the smallest possible experiment.
She also covers how to select which opportunity to address, using a structured comparison rather than a scoring formula, and how to avoid the confirmation bias that follows from testing an idea a team is already committed to.
The book is craft advice from practice rather than research, and it is written for software product teams in companies with dedicated product functions. Its interviewing method overlaps with Fitzpatrick's The Mom Test, also in this reference.
Product managers, designers and engineers who want a weekly operating practice for deciding what to build rather than an occasional research process.
Chosen by shared topics, the entries that hold them, and the people who recommended both.