~/learn/Product Metrics · Trade-offs & launch decisions
Guardrails & counter-metrics
Pair every goal metric with one that catches you gaming it or hurting users.
why this matters
Naming a sharp counter-metric is a fast way to show product judgment.
Every metric can be pushed up in a bad way. More notifications raise daily opens but annoy users; more ads raise revenue but reduce time spent; faster driver dispatch raises completed rides but may hurt driver earnings. A counter-metric is chosen specifically to catch these side effects.
Guardrails are metrics that must not get worse beyond a set limit for any launch: crash rate, page load time, unsubscribes, refund rate, reports of bad content. They protect long-term health while teams chase short-term goals.
Pairs
goal metric counter-metric notification opens opt-outs, uninstalls ad revenue session time, ad hides support tickets closed reopen rate, satisfaction feed engagement content reports, regret surveys
Interview trap
Saying 'I'd track revenue and also engagement' isn't a counter-metric answer. Name the specific way your goal could be gamed, then name the metric that would expose it.
Pro tip
Set thresholds in advance: 'Ship if revenue +2% and session time drops no more than 0.5%.' It shows you think in decisions, not dashboards.
key takeaways
- Every goal metric can be gamed.
- Pick counter-metrics for specific harms.
- Set guardrail thresholds in advance.
check your understanding
You're optimizing push-notification open rate. Best counter-metric?