Product Discovery
You know discovery matters. The question now is how - and teams tend to answer it with a reflex: book some interviews. But interviews are one tool among several, and reaching for them by habit is like using a hammer on every job. "How many people hit this problem?" and "why do they hate the current tool?" are different questions, and they need different methods.
Learn on the move: press play and turn your commute, walk or drive into time that grows your design career.
Listen to the full Product Discovery course on DesignPath
This module is the toolkit. It covers the main ways to learn from users - talking, watching, asking at scale, and reading what's already known - and, first, how to pick the right one for the question you're stuck on.
Choosing a Discovery Method
The first move in any discovery isn't picking a tool - it's naming what you're actually trying to learn. Get that clear and the right method usually picks itself. This article is how to match the two, and how to combine methods so you can trust what they tell you.
Match the Method to the Question
Each method answers a different kind of question. Pick by what you need to know, not by what's easiest to run.
Talk - interviews.Best for why: motivations, frustrations, the story behind a behavior. You get depth, not numbers.
Watch and test - observation and prototype showing.Best for what people actually do, which is often not what they say. You catch the workaround and the moment of confusion.
Ask at scale - surveys.Best for how many and how often: measuring how widespread a pattern is once you've found it.
Read - desk research.Best for what's already known: existing reports, reviews, and data you can use before spending a minute on primary research.
Depth vs Scale
There's a trade-off running through all of this. Talking and watching give you deep understanding from a few people. Surveys and desk research give you breadth from many, but shallow. You usually want to move from depth to scale: interview a handful to understand the problem, then survey to check how common it is.
Pro tip: If you can't say what decision a piece of research will change, don't run it. Method choice starts from the decision you're stuck on, not from "we should do some research."
Combine to Be Sure
No single method gives you the full picture. The strongest discovery triangulates - it lines up two or three methods and looks for where they agree.
If interviews suggest a pain, observation shows people hitting it, and a survey says 60% feel it too, you have something solid. If only one method points to it, treat it as a lead, not a fact. Agreement across methods is what turns scattered signals into confidence.
Where AI Helps
Prompt: "I need to learn [specific question] about [users]. Recommend which discovery methods fit best, in what order, and what each one will and won't tell me."
AI suggests the method mix; you match it to your real constraint.It can map questions to methods quickly, but it doesn't know your timeline, budget, or access to users. Use its suggestion as a menu, then pick what you can actually run this week.
