By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres argues that effective product teams should pair two discovery activities every week: continuous customer interviewing to find opportunities, and assumption testing to evaluate solutions. Visualizing this work with an opportunity solution tree, anchored to a clear outcome, links customer value to business value. Most teams still work in a project mindset, prototyping or A/B testing whole solutions too late. She advocates testing the individual assumptions behind an idea before building it, and aligning the team on what a solution means so its hidden assumptions surface. The post also announces two new courses built around this solution-discovery approach.
01Key takeaways
- Pair continuous customer interviewing with assumption testing every week, since one generates opportunities and the other evaluates solutions.
- Anchor discovery to a clear outcome so that the work you do stays tied to measurable business impact.
- Test the assumptions behind an idea before prototyping or building the whole solution.
- Align your team on what a solution actually means before generating assumptions, since individual interpretations differ.
- Prioritize the riskiest assumptions and match each one to the right research method.
- Define what success looks like before running a test to guard against confirmation bias.
02Key sections
- The opportunity solution tree
- Discovery starts from a clear outcome, with continuous interviewing surfacing opportunities and assumption testing identifying which solutions work. Together they create customer value that drives business value.
- Why teams struggle to change
- Years of output-focused work and deadline pressure make new discovery habits hard to adopt, requiring new skills, mindsets, and practice rather than an overnight switch.
- Discovering solutions quickly
- Testing whole prototypes or building before testing is slow and risky. Teams should instead test the assumptions that must hold true, as Eric Ries suggested in The Lean Startup.
- Surfacing hidden assumptions
- Assumptions are easy to miss because they feel obviously true, and team members often interpret solutions differently. Aligning on meaning and generating assumptions together comes first.
- The new courses
- The post announces Identifying Hidden Assumptions and Assumption Testing, covering story mapping, assumption prioritization, method selection, and defining success upfront.
03From the post
“Visualizing discovery work with an opportunity solution tree has been a game-changer for both me and the teams that I work with. It’s a simple visual that packs a lot of power. At the top, we start with a clear outcome. This sets the scope for our discovery.”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.