Run the failure
Use the red CTA to create the analytical problem intentionally.
Keep the same numerator but swap the denominator and watch the cancellation story change completely.
Decide which denominator represents the population that could have produced a cancellation.
Use the red CTA to create the analytical problem intentionally.
Before validating, decide what you expect row counts or metrics to do.
Use the green CTA to reveal the checks that catch the failure.
Say what broke in plain business language, not only SQL language.
Decide which denominator represents the population that could have produced a cancellation.
The numerator never changed. The business story changed because the denominator moved to the wrong grain and population.
A rate is a population definition disguised as arithmetic.
Denominator grain must match the business question.
Metric contracts should make inclusion and exclusion rules explicit.