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.
Related Insights
To discover high-value AI use cases, reframe the problem. Instead of thinking about features, ask, "If my user had a human assistant for this workflow, what tasks would they delegate?" This simple question uncovers powerful opportunities where agents can perform valuable jobs, shifting focus from technology to user value.
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.
The goal of asking questions isn't just for you to gather information. It's a Socratic dialogue designed to help stakeholders think differently and arrive at the real need themselves. By guiding their thought process, you build deeper alignment and co-create a better solution, rather than just extracting requirements for yourself to fulfill.
Effective product development starts with internal alignment. Using exercises like Instagram's "Stories Mad Libs" creates a shared, candid understanding of the product's current state. This "organizational therapy" is a prerequisite for overcoming team biases and conducting successful user research.
Instead of waiting for features to build a story, develop the compelling narrative the market needs to hear first. This story then guides the launch strategy and influences the roadmap, with product functionality serving as supporting proof points, not the centerpiece.
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.
Truly innovative ideas begin with a tangible, personal problem, not a new technology. By focusing on solving a real-world annoyance (like not hearing a doorbell), you anchor your invention in genuine user need. Technology should be a tool to solve the problem, not the starting point.
To make research resonate, don't just present findings. Frame the readout as a narrative that begins with the stakeholders' known assumptions and concerns. This creates a compelling journey. Enhance impact by assigning 'homework,' like a curated podcast of interview clips, to foster direct empathy.
