We scan new podcasts and send you the top 5 insights daily.
Jeff Patton's concrete advice is to find someone using what you built and watch or talk to them directly. He says not to have AI go talk to customers instead; firsthand observation often shocks product managers into empathy and shows them what they missed.
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.
Users often don't know what they want. Instead of direct questioning, create live prototypes or social experiments. Observing how people naturally use these tools in a real-world context provides more honest and insightful data than traditional interviews.
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.
To truly understand customers, go to their natural environment—their home or shop. Observing their context reveals far more than sterile office interviews. This practice, internally branded "Listen or Die," ensures the entire team stays connected to the user's reality.
Don't just rely on surveys or direct feedback. The most powerful insights come from observing user behavior. For the Savannah Bananas, watching fans leave games early—unprompted—revealed the core problem wasn't the sideshow entertainment but the slow pace of baseball itself.
Don't wait for post-launch metrics to validate an idea. The essential evidence for whether to build something is gathered through direct, face-to-face conversations with users about their problems. This pre-build signal is far more reliable than any data collected after shipping.
To truly understand customer problems, product managers must practice 'gemba'—a Japanese term for 'go where the work is happening.' Physically visiting customers in their environment is crucial for uncovering genuine needs that lead to better products.
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.
To identify hidden friction points, directly experience your product or service as a customer would. This is exemplified by a Nashville sheriff who slept in a jail cell to test heating complaints. This firsthand experience is the most effective way to build empathy and uncover issues.