Lenny's PodcastBuild better products with continuous product discovery | Teresa Torres
CHAPTERS
- 0:00 – 1:10
Backlog as bets: discovering and delivering in parallel
Teresa frames every backlog item as a bet, whether or not a team does discovery. She argues against treating discovery and delivery as sequential phases, advocating instead for building discovery as an ongoing habit that improves decision quality over time.
- •Everything in the backlog is a bet; discovery improves the odds
- •Avoid “stop building until we research”—it kills momentum and buy-in
- •Discovery and delivery should run continuously in parallel
- •A steady discovery habit leads to better bets over time
- 1:10 – 6:00
Teresa’s background and why she’s influenced so many PMs
Lenny introduces Teresa Torres and highlights her impact through teaching, coaching, and her book Continuous Discovery Habits. Teresa shares the scale of her reach through Product Talk Academy and reflects on how surreal it feels to be recognized by early industry influences.
- •Teresa’s roles: speaker, teacher, consultant, product coach, author
- •Continuous Discovery Habits as a highly recommended PM book
- •~11,000+ students plus hundreds coached; ~12,000 total impacted
- •Credibility context: among the most widely-reaching PM educators
- 6:00 – 6:41
Where to follow Teresa’s work and what this conversation will cover
Teresa shares where to find her writing and courses, then Lenny sets the agenda. The episode centers on two pillars: the Opportunity Solution Tree framework and the practical system of continuous discovery through regular customer conversations.
- •Product Talk website and blog for ongoing writing
- •Courses focused on discovery practices
- •Episode focus: Opportunity Solution Tree + continuous discovery system
- •Goal: help teams align on outcomes and learn from customers continuously
- 6:41 – 9:35
Opportunity Solution Tree: turning outcomes into structured product decisions
Teresa explains the Opportunity Solution Tree as a visual scaffold that helps teams move from outcome-first thinking to what to build. She emphasizes that while the tree looks simple, teams struggle most with defining opportunities (problem space) versus solutions.
- •Tree structure: outcome → opportunities → solutions → assumption tests
- •Built to help teams shift from outputs/features to outcomes
- •Core difficulty: defining “opportunities” as unmet needs, not solutions
- •Most teams accidentally populate the opportunity space with solutions
- 9:35 – 12:12
Netflix example: structuring opportunities with an experience map
Using streaming entertainment, Teresa shows how to structure the opportunity space around the customer journey rather than feature ideas. She walks through experience-map steps (trigger, deciding, evaluating, watching, post-viewing) and illustrates how opportunities emerge as needs and pain points inside those moments.
- •Use experience mapping to organize the opportunity space
- •Opportunities are needs/pain points (e.g., can’t tell if a show is good)
- •Avoid embedding solutions; different companies share similar human needs
- •Mapping clarifies where to play and improves customer-centric strategy
- 12:12 – 14:18
How detailed should a tree be? Keeping it cognitively usable
Teresa discusses practical guidance for the top-level branches and how opportunity size changes down the tree. She explains that decomposition is key: big evergreen problems become solvable when broken into smaller, specific opportunities that still ladder up to the desired outcome.
- •Top level often mirrors experience-map steps; keep it to ~3–7 branches
- •Opportunities get smaller and more actionable as you move downward
- •Decompose evergreen problems into specific evaluable opportunities
- •A well-formed tree supports strategic focus and continuous cadence
- 14:18 – 17:58
Why teams struggle: interviewing for stories, not opinions
Teresa explains that opportunities come from customer stories, but most teams don’t collect rich narratives. She contrasts shallow, contextless questions with story-based prompts (“tell me about the last time…”) that reveal nuance, behavior, and unmet needs teams wouldn’t think to ask about directly.
- •Opportunities emerge from stories, not decontextualized Q&A
- •Direct questions produce fast but unreliable answers about behavior
- •Story prompts recreate context: who/where/sequence and real constraints
- •Interviewing is an underestimated skill that determines discovery quality
- 17:58 – 21:54
Feature factory reality: change your own habits before changing the org
Asked how to apply outcome thinking in a feature-driven company, Teresa advises individual contributors to avoid forcing organizational change. Instead, she recommends carving out personal practice: talk to customers anyway (even via personal networks) and use business-model context to make better daily decisions.
- •Don’t try to force org change as an IC; focus on how you work
- •You can often talk to customers without formal permission
- •Recruit in personal networks (consumer or B2B via acquaintances)
- •Understanding outcomes and customers improves decisions even on fixed roadmaps
- 21:54 – 24:09
Continuous discovery defined: customer feedback loops at product cadence
Teresa defines discovery as deciding what to build and argues all companies do it—just with varying customer input. Continuous discovery emerges from two shifts: customer-centricity (include customers in decisions) and the reality that digital products are never done, requiring continuous decisions and learning.
- •Discovery = work to decide what to build; delivery = build/ship
- •Trend 1: outcomes/customer-centric decision-making
- •Trend 2: digital products are continuously evolving (no ‘done’)
- •Continuous discovery = continuous customer feedback loops
- 24:09 – 26:50
“No time for discovery”: reframing discovery vs project-based research
Teresa tackles the common leadership objection that there’s no time for research. She argues the real issue is the legacy expectation of large, project-based studies; continuous discovery can start small (e.g., one interview a week) while still delivering, since delivery and discovery must coexist.
- •Leaders often equate discovery with slow, project-based research
- •Continuous discovery can start with as little as one interview per week
- •Assumption testing blends into delivery—hard to draw a strict boundary
- •Keep shipping; add discovery in parallel to make progressively better bets
- 26:50 – 29:58
Automating weekly customer conversations: opt-in + scheduling workflows
Teresa shares a practical system to make customer interviews a recurring default. She recommends embedding opt-in prompts in-product (like NPS, but for interviews) or using sales/support/account teams for recruiting buyers—then using scheduling tools so the product team only needs to show up and talk.
- •Apply “nudge” thinking: make interviewing easier than not interviewing
- •Turn interviews into recurring calendar events via automation
- •Recruit via in-product opt-in prompts + scheduling links
- •For buyers/decision makers, recruit through sales/support/account teams
- 29:58 – 32:13
Staying unbiased and avoiding solution fixation: manage risk and create options
Teresa explains that not every problem requires deep discovery; effort should match risk and strategic importance. For high-stakes areas, she recommends countering bias by developing multiple solution options and comparing tradeoffs, while instrumenting releases to calibrate how risky bets actually are.
- •Discovery depth should match risk; not every area needs heavy discovery
- •Instrument and measure releases to learn where risk truly exists
- •When stakes are high, generate multiple solutions for the same opportunity
- •Comparing options reduces over-commitment to the ‘obvious’ solution
- 32:13 – 36:20
PM decision-making and the product trio: collaboration over territory
Teresa critiques the ‘PM as CEO/decider’ framing as a byproduct of siloed, political business culture. She argues for empowered product trios (PM, designer, engineer) working from shared understanding through discovery, using disagreements as a signal to keep searching for a better option.
- •‘PM as CEO’ mindset fuels office politics and weak collaboration
- •Well-functioning trios jointly decide: PM + design + engineering
- •Shared discovery reduces disagreement by aligning on reality
- •When you disagree, it often means you haven’t found the best option yet
- 36:20 – 41:05
Interviewing best practices: natural conversations grounded in real behavior
Teresa gives concrete interviewing guidance: avoid long scripted question lists and instead run interviews as relaxed, story-driven conversations. She demonstrates a single-question approach (“tell me about the last time…”) and stresses focusing on what people actually did, not what they would do.
- •Avoid 50-question protocols that break conversational flow
- •Aim for a ‘beer with a buddy’ tone to elicit richer stories
- •Use timeline prompts: set the scene, then ‘what happened next?’
- •Prioritize actual behavior over hypothetical intentions
- 41:05 – 48:17
Discovery at scale: what changes in big companies + experiments vs research
Teresa argues the core unit of empowered continuous discovery should stay the same from startups to enterprises; what changes is coordination across adjacent teams and shared design systems. She also addresses skepticism about small-sample research and clarifies her model: qualitative interviewing for opportunities, assumption testing for solutions, with tests small and frequent enough to sustain continuous learning.
- •Ideally the empowered trio model doesn’t change with company size
- •Bigger orgs add dependencies, coordination, and shared design libraries
- •Small data is valid within iterative feedback loops; one is better than zero
- •Use interviewing to map opportunities; use assumption tests to evaluate solutions
