
Track overview
About this track
Decision practice for the moment a metric you care about moves the wrong way and everyone already knows why. Before you act, decompose: split the change into mix versus within-segment, let the arithmetic — not the calendar — name the cause, and act coherently on what the split shows. A blended number can fall while every segment rises; the disciplined diagnostician reads that, resists the obvious rollback, and knows when the right move is to wait.
How each module works
Every module in this course runs the same three steps, from the first lesson to the debrief. The loop is what makes Decyde a place to practise, not just to read.
Step 1
Read
The lessons. Read the situation, the evidence and the shape of the trade-off before you commit.
Step 2
Size
The simulation. Put numbers on both sides of the trade-off, then make the call against the engine.
Step 3
Defend
The debrief and report. See what your call bought and why, so you can defend it or change it.
The same loop in every module, and a new decision each time. Judgment compounds.
Modules · In order
4 modules in this track
Each module is one decision: short readings, the decision itself, then a debrief and a replay in a shifted world.
01/04
The Metric Drop
You're Maya, Senior PM at NorthPeak, a B2B SaaS platform. Activation — the share of new signups reaching first real use in week one — just fell from 41% to 37%, and the room wants to roll back the onboarding redesign that shipped two weeks ago. Pull activation by acquisition channel and every channel went up; the average fell anyway. Attribute the −4-point drop across five candidate causes, then commit the team's next move — and discover why the blend fell while the product improved (a mix shift, not the release), why the obvious rollback is the worst option on the board, and why decomposing before you conclude is the whole skill.
13 lessons · 2 mini-sims · ~52 min
Begin module02/04
The Vanity Metric
You're Maya, Senior PM at NorthPeak, a B2B SaaS platform. Total Registered Users is up 120% and opens every board deck; revenue is flat. Five candidate metrics are on the table and you own the North Star — the one number the whole team will be steered by for the next year. First diagnose: place each metric on a predicts-value by gameable plane. Then act: crown one. Discover that a metric earns the crown only when it is predictive, actionable AND hard to game (steer value = predictive × actionable × (1 − gameable)) — that the celebrated +120% number is the worst thing on the board to aim at ($27k), that the metric with the highest correlation to revenue (0.88) is the trap that catches rigorous people because it is cheap to fake ($118.8k), that the two quiet leading indicators are near-tied at the top ($408k and $393.7k) because good metrics come as a class rather than a single magic number — and finally that none of it is about the name: re-instrument the trap so it cannot be gamed and it becomes the best metric on the board ($633.6k), redefine the vanity metric and it earns the crown honestly ($576k).
13 lessons · 2 mini-sims · ~52 min
Begin module03/04
Signal or Noise
You're Maya, Senior PM at NorthPeak, a B2B SaaS platform. It's been a nervous quarter, and six metric alarms are on the table: a crash, a spike, a recovery after a fix, a quiet slide. Weekly free-to-paid conversion sits at μ = 5.0% and breathes ±0.4pp on its own. Triage each alarm against the control band, signal or noise, then commit the team's response to the ones you call signals. A false alarm and a missed signal both cost something, and the decision is which alarms earn a response.
13 lessons · 2 mini-sims · ~50 min
Begin module04/04
The Confounded Read
You're Maya, Senior PM at NorthPeak, a B2B SaaS platform. Five correlations are on the table and every one is real — integration users retain +30pp, onboarding step 3 doubles activation, support-contacting customers churn 3× more, the new AI feature spiked usage, annual-plan teams expand more — each with an obvious action already stapled to it, and a growth team eager to ship all five. Diagnose each claim's causal structure (a genuine cause, a lurking variable driving both, a reversed arrow, a decaying novelty spike, or a real uncertainty), then deliver a verdict: roll it out, drop it, or spend a controlled test. Discover why the biggest number on the board is the emptiest (committed teams both integrate and retain, so the effect won't transfer), why reducing support contact is the most harmful move available (churning customers contact support — the arrow runs the other way), why a launch spike is the least informative moment to judge a feature, and why the disciplined read (net 200) beats both the naive believer who ships every strong number (−60, the worst on the board) and the reflexive skeptic who ships none (0, and the whole 200 left on the table). The mdd capstone: a correlation is a question, not a cause.
13 lessons · 2 mini-sims · ~50 min
Begin moduleAuthored on Decyde Practice loop curated for decision discipline
Vocabulary
What you'll engage
The decision skills you'll practice are paired with the underlying patterns you'll learn to recognize. Both vocabularies compound across the Product Decisions domain.
Decision skills you'll practice
Scope cuttingRoadmap trade-offsBuild-vs-buyCustomer-evidence weighingSequencing judgmentMVP defining
Patterns you'll see
Practice evidence recorded on Decyde
Every decision practiced builds your Decision Profile
Replays supported
Practice the same decision differently · iteration builds judgment
English
Additional languages on v1.3+ roadmap
What's next · One recommendation
The other Product Decisions courses each practise a different kind of decision.
Begin practice →FAQ
Questions about this track
Common questions about Metrics & Diagnostics Decisions and how this track works.
Related · Other tracks





