R&D departments often receive reactive briefs from commercial teams, leading to generic products. The goal should be to 'leapfrog the brief' by conducting deep user research independently. This allows R&D to proactively propose innovative solutions based on future user needs, rather than just executing marketing's requests.

The most valuable product use cases are often discovered not through surveys, but through deep, intellectually curious immersion into the customer's world. This means observing their environment and processes firsthand to understand latent needs they cannot articulate, as proven by the karaoke company story.

This dedicated role studies end-users in their environment to understand needs and constraints before development begins. This preempts building features that are easy for developers but wrong for users, mitigating the risk of creating unused or ineffective software, framing user research as a key risk mitigation strategy.

Tock rejected traditional focus groups and instead embedded its software engineers directly into restaurants to work shifts as hosts. This forced immersion gave the engineering team firsthand experience with the end-user's pain points, leading to a far more intuitive and effective product than surveys could produce.

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.

The CGO role merges marketing, e-commerce, R&D, and analytics, ensuring product development is guided by marketing insights from the beginning. This prevents the common scenario where marketing must create a story for a product it had no input on.

By embedding product teams directly within the research organization, Google creates a tight feedback loop. Instead of receiving models "over the wall," product and research teams co-develop them, aligning technical capabilities with customer needs from the start.

Observing users in their own environment reveals truths that surveys miss. A consumer might claim they never buy a certain brand, but a look in their cupboard proves otherwise. This direct observation is crucial for uncovering real user habits, moving beyond claimed data to understand actual behavior.

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.