Aakash GuptaThe #1 Skill PMs Need in 2025: AI Product Discovery Masterclass by World’s Leading Authority
At a glance
WHAT IT’S REALLY ABOUT
How AI reshapes product discovery: interviews, assumptions, prototypes, evals, ethics
- Torres argues that as AI makes prototyping and delivery cheaper, discovery becomes more important to prevent feature bloat, customer change fatigue, and incoherent products.
- Many product features fail because teams conduct unreliable interviews focused on solutions and hypotheticals rather than story-based interviewing that excavates real past behavior and unmet needs.
- Continuous Discovery Habits centers on weekly customer interviews, mapping opportunities in an Opportunity Solution Tree, selecting a target opportunity, and comparing multiple solutions through assumption testing.
- AI can augment discovery work via thought partnership, faster prototyping, and partial synthesis, but outsourcing interviewing/synthesis risks losing empathy, context, and differentiated insights.
- Building AI products requires additional discovery-oriented loops around context engineering, orchestration, observability (trace logging), error analysis, evals, and ongoing maintenance of non-deterministic behavior.
IDEAS WORTH REMEMBERING
5 ideasWhen delivery gets cheaper, discovery becomes more valuable—not less.
AI prototyping can flood products with “easy” features; discovery is what prevents feature bloat, incoherence, and customer change fatigue by ensuring you ship what matters.
Stop asking customers to predict the future; anchor interviews in the past.
Questions like “Would you use this?” generate polite, optimistic, unreliable answers; instead ask for the last time they solved the problem and excavate the full narrative.
Good interviewing is less about open-endedness and more about excavation.
Even with a story prompt, PMs often start guessing (“Did you look at recommendations?”); use temporal prompts (“What did you do first/next?”) to reconstruct real behavior and friction.
Use interviews to understand customers; use assumption tests to evaluate solutions.
Interviews should reveal needs, pains, and desires, while assumption testing breaks solutions into what must be true and tests those pieces quickly before heavy design/engineering.
AI prototypes should test assumptions, not validate whole ideas.
Even if you can prototype three full solutions in a day, whole-idea testing creates long, unstructured sessions; prototype specific elements to pinpoint where a workflow breaks down.
WORDS WORTH SAVING
5 quotesYou know, I've been getting asked a lot, like when delivery is free, do we still need to do discovery? And I actually think when delivery is free, discovery becomes more important.
— Teresa Torres
Nothing in their backlog changes. They don't kill any ideas. There's a lot of discovery theater out there.
— Teresa Torres
But when you're building a product, the prompt can't be refined by you. Once it's live in your product, there's no refinement. It's a one shot.
— Teresa Torres
It's, like, 60 to 80% good, and I worry about what we lose in that 20 to 40%.
— Teresa Torres
If you're doing what your company expects you to do, you are a product manager.
— Teresa Torres
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome