Product Strategy – Insights

Marty Cagan argues that the insights forming the foundation of a product strategy are the hardest but most valuable part of product work, and they cannot be produced by a template or framework. He says strong insights come from rigorous preparation: studying company objectives, dashboards, and vision, while staying open to ideas from anywhere. He identifies four consistent sources: quantitative data from live tests, qualitative user research (both evaluative and generative), enabling technology (often surfaced by engineers), and industry analysis. He also stresses that insights must be shared across the organization, with the head of product aggregating and communicating learnings, since insights rarely reach the right people through written reports alone.

01Key takeaways

• Do the homework on objectives, metrics, and vision before expecting a strategic insight to emerge.
• Build the habit of running live-data tests so the organization can quickly validate ideas and spot important learnings.
• Treat user research as a source of generative insights, not only validation of the current solution.
• Pay attention to engineers who identify new enabling technologies, and invest in learning those technologies.
• Don't rely on written reports to share learnings; use conversations, weekly 1:1s, and all-hands to spread insights.
• Have the head of product aggregate and summarize key insights across teams so the broader organization benefits.

02Key sections

Why strategy insights are hard

Cagan says there is no paint-by-number playbook for product strategy. Insights only emerge after serious preparation with company objectives, metrics, and vision, and they can come from any source.

Quantitative and qualitative sources

Data analysis and live-data tests can reveal important patterns, while user research yields evaluative learning about solutions and generative learning about new opportunities.

Technology and industry insights

New enabling technologies can unlock long-standing problems, and engineers often spot them first. Industry trends and analysts add context, though outside consultancies often lack product-strategy depth.

Sharing learnings across the organization

Insights stay trapped inside teams unless leaders actively connect and distribute them. Leaders often receive the data they request rather than the data they need.

The head of product's role

Cagan recommends the head of product aggregate learnings from all teams and summarize key ones at regular all-hands, which broadens understanding and helps leaders truly absorb insights.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.