Analytics for Product Teams
Reading a metric properly: variation, base rates, and knowing when a change is not a change.
- Courses
- 13
- Hours
- 18
- Modules
- 4
Written for the people who read dashboards rather than build them. There is no SQL on this path and no apology for that.
Assessed on a one-page readout of a real dataset, marked on whether the conclusion follows from the evidence.
The sequence
Modules unlock in order. You finish one before the next opens, which is the point of a path rather than a playlist.
-
01
What a metric is for
Choosing the one number a team should argue about.
-
02
Noise and signal
Reading a dashboard without reacting to weather.
-
03
Experiments you can trust
Sample size, duration, and stopping rules set in advance.
-
04
Telling the story
Presenting a result so a room makes a decision.
What you can do afterwards
The assessment checks these directly, against a rubric published before you start.
Before you start None. Written for designers, engineers and product managers rather than for analysts.
- Tell a real movement from ordinary variation.
- Set a stopping rule before you look at the result.
- Present a finding without overclaiming it.