OKR Scoring: How to Grade Your OKRs at End of Quarter
Learn the OKR scoring system (0.0–1.0 scale), how to calculate scores, what good scores look like, and how to use end-of-quarter results to improve next quarter's planning.
Loach Team
Product Team
At the end of every OKR quarter, teams need to answer one question: how did we do?
OKR scoring is the system for answering that question consistently. It uses a 0.0–1.0 scale to grade each key result and then aggregate those grades into an overall picture of the quarter.
Done well, OKR scoring drives better planning for the next quarter. Done poorly — or skipped entirely — it becomes a ritual where everyone glosses over failures and moves on.
The OKR Scoring Scale
OKRs are graded on a 0.0 to 1.0 scale:
| Score | Meaning |
|---|---|
| 1.0 | Key result fully achieved |
| 0.7 | Strong progress — this is the target |
| 0.5 | Meaningful progress but fell short |
| 0.3 | Some work done, limited impact |
| 0.0 | Not started or negligible progress |
The 0.7 target is the most important thing to understand about OKR scoring. In most OKR frameworks — including Google's original approach — a 0.7 is considered a success. A consistent 1.0 means the targets were not ambitious enough.
Why 0.7 is the target, not 1.0
If your team consistently scores 1.0 on all key results, your OKRs are too easy. The purpose of OKRs is to stretch. A target set at the edge of what you think is achievable will sometimes be fully met and sometimes not — producing an average around 0.6–0.7. That is the sign of well-calibrated OKRs.
How to Calculate OKR Scores
Scoring a Key Result
For numerical key results, the score is typically calculated as:
Score = (Actual − Baseline) / (Target − Baseline)
Example:
- Baseline (start of quarter): NPS = 30
- Target: NPS = 50
- Actual (end of quarter): NPS = 44
Score = (44 − 30) / (50 − 30) = 14 / 20 = 0.7
For binary key results ("did we ship feature X?"), the score is typically 0.0 or 1.0.
Scoring an Objective
The Objective score is the average of its Key Result scores.
Example:
- KR1: 0.7
- KR2: 0.5
- KR3: 1.0
Objective score = (0.7 + 0.5 + 1.0) / 3 = 0.73
Some teams weight key results differently (e.g., a more important KR counts double), but simple averaging works well for most teams.
Overall quarter score
Average the Objective scores.
What Different Scores Mean
Consistently scoring 0.8–1.0
Your targets are probably not ambitious enough. Either you are setting goals you already know how to achieve, or you are sandbagging to protect scores. Try raising the bar by 20–30% next quarter.
Scoring around 0.6–0.7
This is the healthy range. You are pushing for ambitious outcomes and making strong progress. Some key results you fully achieved, some you fell short on. Your OKRs are well-calibrated.
Consistently scoring 0.3–0.5
Something is wrong. Either the targets are unrealistic, the team does not have enough resources, the planning broke down, or the OKRs were the wrong goals to begin with. The retrospective needs to be honest about which of these is true.
Scoring below 0.3
This is a signal to pause and diagnose. Common causes: OKRs were set without a path to achievement; major unexpected disruptions derailed the quarter; the team was not resourced for the goals; or the check-in habit broke down and nobody noticed the drift until too late.
The End-of-Quarter Scoring Session
Block 60–90 minutes for the end-of-quarter review. Run it in this order:
1. Score key results independently (15 minutes)
Before the meeting, have each owner score their key results privately. This prevents anchoring on other people's scores and produces more honest assessments.
2. Share and align (20 minutes)
Compare scores as a team. Where there is disagreement, discuss why. The conversation about scoring differences is often more valuable than the score itself.
3. Celebrate what worked (10 minutes)
Name the specific wins explicitly. What did the team do well? What should you replicate next quarter?
4. Diagnose what did not work (20 minutes)
For every key result that scored below 0.5, ask: why? The goal is honest diagnosis, not blame. Common answers:
- "We set this target without a clear path to achieve it"
- "We lost focus when X happened in month 2"
- "We underestimated the dependency on Y"
- "We hit our weekly priorities but they were the wrong priorities"
5. Carry forward to next quarter's planning (10 minutes)
What do the scores tell you about next quarter's OKRs? What should be continued, abandoned, or approached differently?
OKR Scoring vs Performance Reviews
This distinction is important enough to state clearly: OKR scores are not performance ratings.
If an employee scores 0.4 on their key results and that feeds into their performance review, two things happen:
- Employees start setting conservative targets to protect their scores
- The stretch goal — the entire point of OKRs — disappears
OKRs measure team and company progress toward strategic goals. Performance reviews measure individual growth, contribution, and competencies. Keep them separate.
Common Scoring Mistakes
Retroactively adjusting targets to get a better score
If the quarter's results were disappointing, it is tempting to quietly lower the target so the score looks better. Do not do this. The score only has value if it is honest.
Scoring all key results 0.7 regardless of reality
Some teams have an unspoken norm of reporting 0.7 on everything because it is "the target." This makes the scoring process meaningless. Be specific and honest.
Skipping the scoring session entirely
If you do not score your OKRs, you do not learn from them. The scoring session is where institutional knowledge about what works is built. Skipping it breaks the improvement loop.
FAQs
Q: What is a good OKR score?
0.7 is the benchmark for "strong progress." The right question is not "did we hit 1.0?" but "did we make meaningful progress toward an ambitious goal?" A 0.6–0.8 range across a quarter is typically healthy.
Q: Should all key results be weighted equally?
For most teams, yes. Simple averaging is easier to understand and communicate. If some key results are genuinely more important, you can weight them, but keep the weighting consistent and transparent.
Q: What if circumstances changed significantly mid-quarter?
If you updated your OKRs mid-quarter (which is fine and sometimes right), score against the updated targets. If you did not update them but should have, note this in the retrospective — it is a planning lesson for next quarter.
Q: How long should the scoring session take?
60–90 minutes for a team of 5–15 people. If it takes significantly longer, either your OKRs are too complex or the retrospective is turning into a blame session rather than a learning exercise.
Conclusion
OKR scoring is not about rating your team. It is about creating an honest feedback loop that makes each quarter's planning better than the last.
Score honestly. Diagnose failures without blame. Celebrate real progress. And set the next quarter's targets based on what you learned.
Related resources:
- How to Write OKRs — Setting targets that are ambitious but achievable
- Why OKRs Fail — What low scores often reveal about the planning gap
- OKR Check-in Guide — The weekly rhythm that prevents score surprises
- OKR Guide: Setting Effective OKRs — Detailed OKR framework
Running your end-of-quarter review? Start next quarter right with Loach →