Build better products with continuous product discovery | Teresa Torres — Lenny's Podcast: Product | Career | Growth Summary

Build better products with continuous product discovery | Teresa Torres — Lenny's Podcast: Product | Career | Growth Summary | Galaxy of Podcasts

The Conversation Breakdown

Map the experience before choosing a solution

⏱ Untimed topic

Torres structures opportunities around steps in a customer's experience, such as deciding what to watch and actually watching. Decomposing a broad pain point can reveal smaller needs a team can address. Her Netflix example illustrates the method rather than documenting its internal process.

Collect stories rather than abstract preferences

⏱ Untimed topic

She recommends asking about the last time someone did a relevant activity, then exploring the setting and sequence. Direct general questions can omit important context. Her remarks about cognition are her explanation of the method, not independently verified psychological claims here.

Listen for needs in the sequence

⏱ Untimed topic

A story can expose friction, desires and workarounds the person would not mention as a general preference. Ask what happened next and follow a useful detail. Do not rush to the next prepared question and miss the experience already being described.

Treat discovery as deciding what to build

⏱ Untimed topic

Torres uses discovery for the work of making product choices, which every team does whether or not it calls it discovery. Customer feedback can make those choices better informed. The label alone does not establish that a team is learning.

Keep feedback continuous as the product changes

⏱ Untimed topic

She argues that digital products keep evolving with customer needs, so deciding what to build is ongoing. An interview a week can be one small recurring input into that work. It is not a complete substitute for every kind of research.

Connect assumption testing with delivery

⏱ Untimed topic

She calls assumption testing the start of delivery rather than a separate stage that must finish before every backlog item. Each idea is still a bet. The goal is to improve the bet and keep learning, not create a research gate that blocks all work.

Scale discovery to risk and measure releases

⏱ Untimed topic

Torres says not every solution needs extensive discovery. Give greater attention to core experiences and meaningful risks, then instrument and assess what you release. Evidence of actual impact helps improve future judgments about which ideas need more testing.

Build better products with continuous product discovery | Teresa Torres

Executive Summary (TL;DR)

Key Takeaways

Map the experience before choosing a solution

Collect stories rather than abstract preferences

Listen for needs in the sequence

Treat discovery as deciding what to build

Keep feedback continuous as the product changes

Connect assumption testing with delivery

Scale discovery to risk and measure releases

The Conversation Breakdown

Map the experience before choosing a solution

Collect stories rather than abstract preferences

Listen for needs in the sequence

Treat discovery as deciding what to build

Keep feedback continuous as the product changes

Connect assumption testing with delivery

Scale discovery to risk and measure releases

Core Frameworks & Ideas

Experience map and opportunity space

Story-based interview

Risk-based discovery

Actionable Next Steps

Notable Quotes

The One Thing to Remember