# OKR Worksheet — [Team] · [Quarter]

> Work top-down: strategy line first, then objectives, then KRs. The right-hand prompts are the quality gate — a KR that can't fill its row honestly isn't ready.

**North Star metric:** [metric + current value] · **Company priority this supports:** [quote it, don't paraphrase]

## Objective 1: [qualitative, inspiring, time-bound]

*Why this, why now:* [1-2 sentences connecting to the strategy line above]

| # | Key Result | Baseline (source) | Target | Above do-nothing drift? | Team controls it? | Guardrail |
|---|---|---|---|---|---|---|
| KR1 | | | | | | |
| KR2 | | | | | | |
| KR3 | | | | | | |

**Owner:** [name] · **Scored by:** [where the numbers will be read at quarter end]

## Objective 2: [ ... ]

*(same structure — 2-4 objectives max, 3-4 KRs each)*

## Health check before committing

- [ ] Every KR passes the 5-question diagnostic in `references/bad-okr-gallery.md`
- [ ] No KR is phrased "launch / ship / complete" — those moved to the roadmap
- [ ] Baselines exist (or are labelled *(assumed — confirm)* with the instrumentation task named)
- [ ] Targets are ambitious enough that 0.7 is a good quarter
- [ ] Any gameable KR has its guardrail in the last column
- [ ] Each objective tells one story — a reader can say what the quarter is about in a sentence

## Quarter-end scoring (fill in advance, score later)

| KR | 1.0 looks like | 0.7 looks like | 0.3 looks like | Final score |
|---|---|---|---|---|

*(Writing the 0.7 row now is the ambition test — if 0.7 equals the do-nothing drift, raise the target.)*
