Building a Product Insights Team

Key Insights

• •

  Combining qualitative user research with quantitative analytics provides deeper, actionable product insights than either method alone.

• •

  User behavior changes detected in data often lack explanatory context without qualitative research, as Andrew's Spotify example shows.

• •

  Data analytics and UX research teams frequently operate in silos, missing opportunities for collaboration despite shared goals.

• •

  A shared hypothesis, such as focusing on the ideal customer profile (ICP), can align cross-functional teams and reduce redundant research work.

• •

  Relying solely on data for customer profiles can reinforce existing product biases and miss broader market opportunities.

• •

  Starting a BI practice often means navigating shifts from qualitative to quantitative emphasis, then settling into a balanced hybrid that works for the organization.

• •

  Three main organizational models for insights teams are embedded squads, centralized centers of excellence, and hybrid approaches, each with their own trade-offs.

• •

  Owning the research backlog and aligning work to company OKRs enables the insights team to deliver maximum business impact and say no to less relevant requests.

• •

  Cross-pollination of analysis between researchers and analysts during data collection and interpretation enhances the quality and buy-in of insights.

• •

  Existing documentation tools like Confluence are insufficient for managing research knowledge, inspiring new solutions like Everywhere to prevent data silos.

Notable Quotes