# Example 09 — Metrics Scorecard

## Scenario

A PM needs a practical measurement design for a feature or initiative, not just a random KPI list.

## Input

> "We’re about to launch conversation history search. Help me define the success metrics and guardrails we should use for launch review."

## What good output looks like

A strong `pm-workbench` response should:

- tie metrics to the real product goal
- separate the core success metric from leading indicators
- include meaningful guardrails
- define when judgment should happen
- note where interpretation could be noisy or misleading

## Expected output shape

**Metrics Scorecard**

## Example response shape

- measurement objective
- core success metric
- leading indicators
- guardrail metrics
- baseline and target
- observation window
- interpretation notes
- recommendation for use

## Why this is useful

Teams often confuse dashboard activity with product success. A scorecard helps define what actually counts and when to make a call.
