We scan new podcasts and send you the top 5 insights daily.
Translating user research from abstract "need states" into direct "help me" statements fundamentally changes a product team's perspective. This simple linguistic shift forces the team to adopt the user's point of view and positions them as helpers solving a personal problem, leading to more user-centric solutions.
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.
When teams get bogged down in technical or financial challenges, they can lose sight of the customer. AI-powered personas offer an immediate way to "chat with the user," serving as a quick empathy check to re-ground the team in the original problem they are solving.
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.
During customer discovery, don't just ask about current problems. Frame the question as, 'If you had a magic wand, what would the perfect solution be?' This helps users articulate their ultimate desired outcome, revealing profound insights beyond tactical feature requests.
A common misconception is that user research involves asking customers to design the product. This is wrong. The process is a clear division of labor: customers articulate their problems and pain points. Your team's role is to then use its expertise and resources to devise the best solution.
Product teams excel at using tools like empathy maps to understand customer feelings and behaviors. However, they often fail to apply this same rigorous curiosity to their internal peers and stakeholders. Using these tools internally can build stronger relationships, improve communication, and foster better collaboration.
The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.
The true power of UX research is aligning the entire product team with a common understanding of the user. This shared language prevents working at cross-purposes and building a disjointed product that users can feel.
Instead of focusing on tactical issues, ask potential customers what they would wish for if they had a magic wand. This prompts them to describe their ideal, transformative solution, revealing the deeper, more valuable problem you should be solving.