We scan new podcasts and send you the top 5 insights daily.
During user research, avoid direct questions like 'What do you do?' which prompt idealized answers. Instead, make observational statements like 'I see you are doing this.' This prompts users to correct your assumption with their actual behavior, revealing breakdowns and true user needs more effectively.
Asking prospects "what do you think?" yields vague, polite feedback. Instead, try to sell them on a tangible outcome for a specific price. Their willingness or hesitation to buy provides much more direct and honest feedback on the value of your proposed solution.
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.
A simple tactical language shift can completely change the tone of a feedback conversation. Asking "Why did you do that?" immediately puts people on the defensive. Instead, asking "What were the reasons that led to you doing this?" frames the inquiry as curiosity, leading to a more open discussion.
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.
Instead of asking direct questions like 'what's important?', prompt customers to recount specific, recent experiences. This storytelling method bypasses generic answers, reveals the 'why' behind their actions, and provides powerful narratives for persuading internal stakeholders.
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.
Asking "what" or "how" questions can create cognitive load. Instead, use labels like "It seems like..." or "It sounds like..." to make an observation. This prompts the other person to elaborate and reveal information without feeling interrogated.
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.
Asking "What did you think?" often leads to polite but unhelpful responses. By reframing the question to "What can we do better?", you explicitly invite constructive criticism, signaling an openness to improvement and making customers more comfortable sharing honest, valuable feedback.
While AI efficiently transcribes user interviews, true customer insight comes from ethnographic research—observing users in their natural environment. What people say is often different from their actual behavior. Don't let AI tools create a false sense of understanding that replaces direct observation.