L03 / 7 labs Metric Contract Debugger
0 / 20 complete
Rookie Analyst 0 XP
+100 XP Mission complete.
Practice Lab · 04 · Business Metrics

Metric Contract Debugger

Keep the same numerator but swap the denominator and watch the cancellation story change completely.

DenominatorsMetric contractsBusiness meaning
Case brief

Decide which denominator represents the population that could have produced a cancellation.

01
Your task

Break it. Run the checks. Explain the evidence.

01

Run the failure

Use the red CTA to create the analytical problem intentionally.

02

Predict the result

Before validating, decide what you expect row counts or metrics to do.

03

Run validation

Use the green CTA to reveal the checks that catch the failure.

04

Explain it

Say what broke in plain business language, not only SQL language.

02
Interactive case

Run this.

RUN THIS CASE ↓

Metric Contract Debugger

Decide which denominator represents the population that could have produced a cancellation.

8 min Core 04 · Business Metrics
Ready — run the case. 20 cancellations become either 20.0% or 7.7%.
Numerator20cancelled orders
÷
Denominator100260eligible placed ordersstatus-event rows
=
Cancellation rate20.0%7.7%

The numerator never changed. The business story changed because the denominator moved to the wrong grain and population.

Debrief unlocked

What should the analyst learn?

  1. A rate is a population definition disguised as arithmetic.
  2. Denominator grain must match the business question.
  3. Metric contracts should make inclusion and exclusion rules explicit.
03
Transfer

Use the same checks at work.

01

A rate is a population definition disguised as arithmetic.

02

Denominator grain must match the business question.

03

Metric contracts should make inclusion and exclusion rules explicit.