OKR Scoring Guide: How to Grade a Cycle
OKR scoring grades Key Results at cycle end, often on a 0.0–1.0 scale from progress data. Stretch OKRs may succeed around 0.6–0.7; committed goals should land near 1.0. Score from metrics first, then discuss narrative — do not weaponize scores in performance reviews.
Overview
Scoring closes the OKR planning loop: learn, then set better goals next quarter. Pair with progress tracking history in your OKR platform.
Why it matters
Without scoring, teams repeat weak goals. With fair scoring, ambition and honesty improve.
Step-by-step
- Export or review final KR values from check-in history.
- Compute progress vs start/target.
- Label stretch vs committed before interpreting scores.
- Hold a short retrospective: keep / change / kill.
- Publish scores for transparency.
Examples
0.7 on a moonshot KR can be excellent performance.
Best practices
- Data before narrative.
- Separate scoring from compensation formulas.
- Compare like-for-like Objectives across cycles.
Common mistakes
Trains sandbagging next quarter.
Celebrate strong stretch outcomes.
Frequently asked questions
What is a good average OKR score?
For ambitious stretch sets, ~0.6–0.7 is healthy. Constant 1.0 usually means weak goals.