Podcast insights
Teresa Torres on Continuous Discovery Habits — From the Source
Continuous discovery is easy to name-drop and hard to practice. On All Things Product, Teresa Torres and Petra Wille go beyond the book: interviewing customers every week, synthesizing each interview into a snapshot, rolling learnings into an opportunity solution tree, and testing assumptions before writing code. These verbatim moments from the transcripts capture the core habits — and the most common ways teams get them wrong.
From 4 episodes on PodLearn
The ideal cadence is concrete: interview weekly, synthesize each interview the same week, and refresh the opportunity solution tree every three or four interviews.
a product team would interview every week. They would synthesize that interview every week. They would do it again. They would do it again every three or four interviews. They would update their opportunity solution tree and everything would be great.
Customer Interview Analysis · All Things Product with Teresa and Petra
Synthesis is per-interview, not a bulk dump. Each conversation gets its own structured pass before anything is aggregated.
one of the things I teach is you need to synthesize each interview separately.
Customer Interview Analysis · All Things Product with Teresa and Petra
An interview snapshot has defined parts: opportunities, key story moments mapped to an experience map, a memorable quote, and quick facts for segmenting.
I basically was trying to teach an LLM how to create an interview snapshot. So identify opportunities, key moments in the story to generate an experience map, maybe a memorable quote, some quick facts to like do segmenting and understand where the story, the context in which the story occurred.
Customer Interview Analysis · All Things Product with Teresa and Petra
Story-based interviews reveal what people actually did — which surfaces solutions users would never request and gives you assumptions to test before building.
if I conduct a story based interview and I hear your story about what you actually did now I can start to look at, oh, I can get rid of this stuff altogether because I can automate it for you. Or, hey, would it work if we had you do this instead? Why don't we have you try that before I build it into software and I can start running some assumption tests.
Product Discovery with Internal Customers · All Things Product with Teresa and Petra
Requirements-gathering meetings are the anti-pattern continuous discovery replaces: asking people what to build produces a list, not understanding.
we're gonna have a meeting and you're gonna give me all your requirements and I'm gonna write them down and then I'm gonna go build all that. And it doesn't work.
Product Discovery with Internal Customers · All Things Product with Teresa and Petra
Discovery cannot be outsourced to synthetic users or one-click generated trees — the learning comes from real humans observing real humans.
If you're building a product for humans, do discovery with humans, full stop.
AI-Generated Opportunity Solution Trees · All Things Product with Teresa and Petra
Episodes this draws from
- Customer Interview Analysis
All Things Product with Teresa and Petra
- Product Discovery with Internal Customers
All Things Product with Teresa and Petra
- AI-Generated Opportunity Solution Trees
All Things Product with Teresa and Petra
- Product Discovery: B2B vs. B2C
All Things Product with Teresa and Petra
Full transcripts are free to read with a PodLearn account.
FAQ
What is continuous discovery?
Continuous discovery, as practiced by Teresa Torres, means product teams maintain a weekly habit of talking to customers rather than doing research as a one-off phase. The team interviews every week, synthesizes each interview separately into a snapshot, and updates its opportunity solution tree every three or four interviews.
What is an opportunity solution tree?
An opportunity solution tree is a visual map that connects a desired business outcome to the customer needs, pain points, and desires (opportunities) discovered in interviews, and then to the solutions and assumption tests that address them. Torres recommends updating it every three or four interviews so it reflects what customers actually say.
How often should you interview customers?
Weekly. In Torres's ideal cadence, a product team interviews every week and synthesizes that interview the same week. She acknowledges most teams fall behind — which is exactly why she frames discovery as small recurring habits rather than a big research project.
Read every word — free
Every quote above links to its full, searchable transcript on PodLearn. Create a free account and read, search, and turn any episode into a lesson.