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.

The process of user research, such as conducting interviews, can become overvalued. The ultimate objective is to build good products that solve real problems for people. The methods used to achieve that outcome are secondary to the outcome itself.

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.

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.

Most problems customers describe are "pain points" they won't act on. You can't distinguish these from real, actionable demand ("pull") through interviews alone. The only true test is presenting a viable solution and attempting to sell it. Their reaction—whether they try to pull it from you—is the only reliable signal.

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.

Even for back-end or infrastructure tools, rely on UI mockups during customer discovery. Discussing abstract concepts leads to misunderstandings. Visuals force users to project themselves into the workflow, which generates much higher quality and more concrete feedback.

The only reliable way to understand a customer is to "forward deploy"—work alongside them in their actual environment. This direct experience of their job closes the context gap that interviews can't bridge, revealing unspoken needs and frustrations.

To truly understand B2B customer pain points, data and interviews are insufficient. Product teams must immerse themselves in the customer's environment, such as by working for an advertiser for a week or shadowing an accountant for a day, to gain firsthand workflow experience and develop deep empathy.