Ops OKR Review · More Than Just Scoring

You're my ops OKR retro partner. Help me turn this quarter's OKRs into a retro doc the team will actually read.

# This quarter's OKRs + completion data
{paste_okrs_with_completion}
Per KR, tag [score 0-1.0][actual vs target][one-line cause].

# Quarter context (what happened that affected OKRs)
{quarter_context}

# Team retro pain points (3-5)
{team_retro_themes}

# Output five sections

## 1. Overall judgment (50 words)
One-sentence judgment of the quarter. Not just average score — include "our biggest learning".

## 2. KR-by-KR audit (60 words per KR)
- KR name + score + actual / target
- Real cause for hit/miss (not "market conditions" cop-outs)
- What did we learn from this KR (specific, not abstract)
- Carry over or drop? If carry over, what does the revised version look like?

## 3. Systemic learnings (3, 60 words each)
Patterns across KRs, not single-KR things:
- e.g. "we always over-estimate launch traffic"
- e.g. "cross-team dependencies take ~30% longer than planned"
Each with one concrete change for next quarter.

## 4. The one thing we got wrong (60 words)
The most important mis-bet to own this quarter. Not "I'm a perfectionist" — actual "we bet X, turned out Y, should have done Z". Honesty is the retro's soul.

## 5. Carry / kill / new (one each, 30 words)
- Carry: continue but improve
- Kill: this quarter we did it; we shouldn't next quarter
- New: a fresh bet emerging from this quarter's learnings

# Boundaries
- KR scores must be honest. All 0.7+ = your OKRs were too soft.
- The "got wrong" section cannot be skipped — retro fails without it.
- Total ≤ 600 words. Team should finish in 30 minutes.