Product Analytics for Decision Makers
Instrument once, measure honestly, and stop arguing about which dashboard is right.
Tobias Lund
Data scientist · ex-forecasting lead
- Testing
- Analytics
- SQL
What you will be able to do
- Design a tracking plan that survives three product rewrites
- Choose metrics that reflect value rather than activity
- Read cohort and funnel analyses without fooling yourself
- Diagnose why two dashboards disagree
- Run a weekly metrics review people find useful
About this course
Most product teams have plenty of data and very little clarity. This course covers tracking plan design, the metrics that actually reflect value delivered, cohort and funnel analysis done correctly, and how to tell when a dashboard is quietly lying to you.
Curriculum
3 sections · 9 lessons
- 1Designing a tracking planNaming, properties and a schema that survives the rewrite.Preview22 min
- 2Identity, sessions and the joins that breakAnonymous to identified, and the stitching in between.20 min
- 3Validating that the data is realTests, monitors and catching the day tracking broke.18 min
Before you start
- Basic SQL helps but is not required.
Student reviews
4.8 from 4
Ryan Whitfield
19 Aug 2026The quiz actually taught me something
I got two questions wrong and the explanations made the reason obvious immediately. That is a rarer thing than it should be.
21 found this helpful
Léo Fontaine
19 Aug 2026Changed how my team works
I ran the middle section as a lunch-and-learn series with my team. We have since adopted three of the practices as defaults. Rare for a course to have that effect.
11 found this helpful
Amara Diallo
19 Aug 2026Great foundation, wanted more on the advanced end
The fundamentals are covered better than anywhere else I have found. I would happily pay again for a follow-up that goes deeper into the last module.
8 found this helpful
Hana Kimura
19 Aug 2026The quiz actually taught me something
I got two questions wrong and the explanations made the reason obvious immediately. That is a rarer thing than it should be.
10 found this helpful