<!-- North Star and input-metric tree · from Chapter 02 of The Product 360 Handbook -->

# North Star and metric tree · [Product] · [Date]

## Vision (one line)
[Vision statement]

## North Star
**Metric:** [name]
**Game:** Attention / Transaction / Productivity
**Definition:** what counts: [ ] · what does not count: [ ] · period: [ ] · data source: [ ]
**Could it become a price meter?** Yes / No. If yes, can a customer audit the count? [how]
**Checks:** reflects customer value [ ] · represents the current strategy [ ] · leads revenue [ ] · not a vanity or lagging financial metric [ ]
**Side measured (platforms):** [which side; how the other side appears below]

## Inputs (three to five)
| Input | Lens (breadth / depth / frequency / efficiency) | Definition | Baseline and source | Owning team | Evidence it drives the North Star |
|---|---|---|---|---|---|
| | | | | | Tested / Weak / Untested bet |

## Team drivers under each input
| Input | Driver | Team | Target this quarter |
|---|---|---|---|
| | | | |

## Guardrails
| Guardrail | Family (quality / trust / cost / health) | Threshold | Inputs it protects | Who watches it |
|---|---|---|---|---|
| | | | | |

## Health metrics (watched, not goals)
-

## Review
Last tested against history: [date]. Inputs to replace or re-test: [list].
