To get unbiased user feedback, avoid asking leading questions like "What are your main problems?" Instead, prompt users to walk you through their typical workflow. In describing their process, they will naturally reveal the genuine friction points and hacks they use, providing much richer insight than direct questioning.
Prospects often describe wants (e.g., "a more efficient system"), which are not true problems. Asking about the motivation behind their desire forces them to articulate the underlying pain that actually drives a purchase decision.
Asking users for solutions yields incremental ideas like "faster horses." Instead, ask them to tell detailed stories about their workflow. This narrative approach uncovers the true context, pain points, and decision journeys that direct questions miss, leading to breakthrough insights about the actual problem to be solved.
Customers, like founders, have a gap between their stated beliefs and actual behaviors. Instead of relying on discovery interviews, watch them work. Observing their actions reveals their true operating philosophy—what they genuinely value—which is a more reliable guide for product development than what they say.
Customers describe an idealized version of their world in interviews. To understand their true problems and workflows, you must be physically present. This uncovers the crucial gap between their perception and day-to-day reality.
Users aren't product designers; they can only identify problems and create workarounds with the tools they have. Their feature requests represent these workarounds, not the optimal solution. A researcher's job is to uncover the deeper, underlying problem.
Standard discovery questions about 'pain points' are too broad. Instead, focus on concrete 'projects on their to-do list.' This reveals their immediate priorities, existing attempts, and the specific 'pull' that will drive a purchase, allowing you to align your solution perfectly.
Users often develop multi-product workarounds for issues they don't even recognize as solvable problems. Identifying these subconscious behaviors reveals significant innovation opportunities that users themselves cannot articulate.
Instead of asking broad, open-ended questions about pain, provide prospects with a multiple-choice list of the common problems you solve. This steers the conversation toward your solution's strengths and prevents wasting time on issues you can't address.
Standard questions like 'What's your biggest pain point?' often yield poor results. Reframing the question to what work a customer would offload to a new hire bypasses their pride or inability to articulate problems, revealing the tedious, high-value tasks ripe for automation.
When designing for kids, the founder learned not to take feature requests literally. A child asking for a bike basket to hold rocks isn't just asking for a rock holder; they're expressing a deeper need for a versatile container for their adventures. The key in user research is to infer the underlying problem from their specific examples.