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.

Standard "discovery interviews" are often a form of "playing founder." It's arrogant to believe a few 30-minute conversations can yield the deep insights needed to build a game-changing product. True understanding comes from immersing yourself in the customer's work, not just casually interviewing them.

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.

Relying on customer interviews creates a false sense of understanding. The context gap between an interviewer and a customer living their job is too massive to bridge with questions alone. This leads to building products based on flawed, incomplete information.

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 design firm Herbst Product operates on the principle that elegantly solving an irrelevant problem is a total failure. This emphasizes the supreme importance of the discovery and definition phases in product development. Before building, teams must ensure they are addressing a genuine, high-value customer need.

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.

Directly asking customers for solutions yields generic answers your competitors also hear. The goal is to uncover their underlying problems, which is your job to solve, not theirs to articulate. This approach leads to unique insights and avoids creating 'me-too' products.