<!-- Team OKR set · from Chapter 02 of The Product 360 Handbook -->

# OKRs · [Team] · [Quarter]

**Input on the metric tree this team owns:** [input]   **Guardrails this team could break:** [list]

## Objective 1: [Qualitative, inspiring, achievable by this team]
**Type:** Committed (expected 1.0) / Aspirational (expected about 0.7)

| # | Key result (who does what by how much) | Baseline and source | Target | Confidence at start (0 to 10) | Type |
|---|---|---|---|---|---|
| KR1 | | | | | |
| KR2 | | | | | |
| KR3 | | | | | |

**Guardrail for this objective:** [metric, threshold]
**Problem the team is solving (not a feature list):** [one paragraph]

## Objective 2 (optional)
...

## Tests before submitting
- [ ] Each KR names an actor and a behavior change, not a deliverable.
- [ ] Each KR has a baseline with a named source.
- [ ] Each OKR is labeled committed or aspirational.
- [ ] No KR can be hit by breaking a guardrail.
- [ ] Deliverables and dates are in the delivery plan, not here.
- [ ] The team can move every KR without waiting on another team.

## Moved to the delivery plan
- [Output] · [date]