The Role of Analytics

Marty Cagan argues that analytics has become a core competency for product leaders, driven by larger data volumes, better tools, and a growing belief that data can speed up learning. He identifies five uses of analytics in strong product teams: understanding user behavior, measuring progress against outcomes, proving whether ideas work through experiments, informing decisions with evidence rather than opinion, and inspiring new product opportunities. He stresses that analytics reveals what is happening but not why, so qualitative research is still needed to explain the numbers. The piece matters because it frames data as a learning tool that complements, rather than replaces, judgment and customer understanding.

01Key takeaways

• Instrument every new feature with basic usage analytics so you can tell whether it works as intended.
• Give teams prioritized outcome metrics instead of prescribed feature roadmaps, and let them choose the solutions.
• Use A/B tests or live-data prototypes for risky or expensive changes to learn which ideas actually work.
• Let data challenge opinions, especially from senior people, while remaining willing to not be ruled by it.
• Explore existing data with good questions to uncover product opportunities you might otherwise miss.
• Follow quantitative findings with qualitative research to understand the reasons behind observed behavior.

02Key sections

Understand user behavior

Analytics shows how people actually use a product, which can differ from what they say. Cagan treats basic usage tracking for every new feature as essentially non-negotiable.

Measure product progress

Teams should be given prioritized KPIs rather than fixed feature roadmaps, so they can choose how to reach outcomes. This reflects a broader shift from outputs to outcomes.

Prove if ideas work

A/B tests and live-data prototypes can isolate the impact of features and designs, especially for high-risk or costly changes. Low-traffic products can still gather useful signals.

Inform and inspire product work

Data can overturn opinions, especially those of senior leaders, and it can also surface new opportunities that teams would not otherwise find. Asking the right questions is key to this exploration.

Pair data with qualitative insight

Quantitative results show what is happening, but qualitative research is needed to understand why. Cagan closes by urging teams to check how fully they use data across all five roles.

03From the post

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

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