# Metrics Scorecard

## When to use

Use this template when a PM needs a practical measurement frame for a feature, initiative, roadmap stage, or experiment.

## Input needed

Prefer to gather the minimum useful context:

- initiative or feature
- target outcome
- expected causal path
- relevant segment or audience
- known baseline if available
- observation window
- known risks or side effects

If 1-2 critical premises would materially change the metric design, clarify those first.

## Output goal

Produce a compact metrics artifact that shows what success means, what early signals to watch, what guardrails matter, and how judgment should be made.

---

# Metrics Scorecard

## 1. Measurement objective

- What are we trying to learn or judge?
- What decision will this scorecard support?

## 2. Core success metric

- What is the single most important result metric?
- Why is it the best outcome measure here?

## 3. Leading indicators

- Which signals should move earlier than the core outcome metric?
- How do they connect to the expected mechanism of impact?

## 4. Guardrail metrics

- What negative side effects must be watched?
- What metrics help prevent local optimization or misleading wins?

## 5. Baseline and target

- What is the current baseline, if known?
- What directional or quantitative target would count as success?

## 6. Observation window

- When should this be reviewed?
- What is too early to judge, and what is late enough to make a call?

## 7. Interpretation notes

- Which metrics are noisy, easy to game, or easy to misread?
- What context should be considered before overreacting?

## 8. Recommendation for use

- How should this scorecard be used in launch review, roadmap review, or iteration decisions?

---

## Notes for use

A strong metrics scorecard should:

- distinguish outcome from process metrics
- include meaningful guardrails when side effects are plausible
- define when judgment happens
- help a future decision get better
