OKR Scoring and Grading: How to Measure Success

OKR Scoring and Grading: How to Measure Success
Meta Description: Master OKR scoring with clear frameworks and methods. Learn how to grade Key Results, calculate objective scores, and interpret results for continuous improvement.
Keywords: OKR scoring, OKR grading, key result scoring, OKR metrics, measuring OKR success, OKR achievement
Introduction
OKRs without scoring are just wishes. The scoring process transforms aspirational objectives into measurable outcomes, provides data for learning, and creates accountability without punishment.
But scoring isn't as simple as pass/fail. The OKR philosophy expects stretch goals where 70% achievement is success. Understanding how to score—and what scores mean—is essential for getting value from the framework.
This guide covers everything you need to know about OKR scoring.
The OKR Scoring Philosophy
Why 70% Is Success
OKRs are meant to be ambitious. If you consistently achieve 100%, you're not stretching enough.
The expectation:
- 70% achievement = Success
- 100% achievement = Goals were too easy
- 30% achievement = Goals were too hard (or something went wrong)
This philosophy enables ambitious goal-setting. Teams can aim high knowing that falling short isn't failure—it's expected.
Scoring Creates Learning
Scores aren't for judgment—they're for learning:
- What worked well?
- What didn't work?
- What would we do differently?
- What should we aim for next quarter?
Separating Scoring from Performance
OKR scores should NOT directly determine:
- Compensation
- Performance ratings
- Promotion decisions
- Job security
This separation preserves the stretch goal mindset. When scores affect careers, people sandbag.
Scoring Methods
Method 1: The 0-1.0 Scale (Google Method)
Each Key Result is scored from 0.0 to 1.0:
| Score | Meaning |
|---|---|
| 0.0 | No progress |
| 0.1-0.3 | Far from target |
| 0.4-0.6 | Made progress but fell short |
| 0.7-0.9 | Strong performance |
| 1.0 | Fully achieved |
Objective score = Average of Key Result scores
Example:
- KR1: 0.8
- KR2: 0.5
- KR3: 0.9
- Objective Score: 0.73
Method 2: Percentage Completion
Calculate actual progress as percentage of target:
Formula: Score = (Actual - Starting) / (Target - Starting)
Example:
- KR: Increase revenue from $1M to $2M
- Actual: $1.7M
- Score: ($1.7M - $1M) / ($2M - $1M) = 0.7 (70%)
Method 3: Traffic Light (Simplified)
For organizations wanting simplicity:
| Status | Meaning |
|---|---|
| Green | On track / Achieved |
| Yellow | At risk / Partially achieved |
| Red | Off track / Not achieved |
Useful for quick reviews but less precise for learning.
Method 4: Committed vs. Aspirational
Some organizations distinguish:
Committed OKRs: Must achieve 100% (operational necessities)
Aspirational OKRs: Target 70% achievement (stretch goals)
Committed OKRs are scored pass/fail. Aspirational use the 0-1.0 scale.
Scoring Different Types of Key Results
Metric-Based Key Results
Example: Increase NPS from 32 to 50
Calculation:
- Achieved NPS: 45
- Score: (45 - 32) / (50 - 32) = 13/18 = 0.72
Milestone-Based Key Results
Example: Launch new product with 4.5+ star rating
If achieved fully: Score = 1.0
If partially achieved:
- Launched with 4.2 stars → 0.7-0.8
- Launched late with 4.5 stars → 0.7-0.8
- Not launched → 0.0-0.3 depending on progress
Binary Key Results
Example: Complete SOC 2 certification
If achieved: Score = 1.0
If not achieved: Score based on progress
- Application submitted → 0.5
- Audit complete, awaiting results → 0.8
- Not started → 0.0
Quality Key Results
Example: Achieve 90% customer satisfaction
Calculation: Straightforward percentage
- Achieved 85% → Score: 85/90 = 0.94
Or relative to starting point:
- Started at 75%, target 90%, achieved 85%
- Score: (85 - 75) / (90 - 75) = 10/15 = 0.67
When and How to Score
Ongoing Tracking (Weekly/Bi-weekly)
Track progress throughout the quarter:
Update format:
- Current value
- Target value
- Confidence level (will we hit the target?)
This isn't formal scoring—it's progress tracking that informs final scores.
Mid-Quarter Check-in
Around week 6, assess trajectory:
- Are we on pace?
- What needs adjustment?
- What risks exist?
This isn't formal scoring but informs course correction.
End-of-Quarter Scoring
Final scoring happens at quarter end:
Timeline:
- Week 12-13: Final data collection
- Week 13: Self-scoring
- Week 13-14: Team/manager review
- Week 14: Scores finalized and discussed
Scoring Meeting Format
Individual Scoring (30 minutes per objective):
- Present final data for each KR
- Calculate scores using agreed method
- Discuss what drove results
- Capture learnings
Team Scoring (60-90 minutes):
- Review each objective together
- Discuss scores and context
- Identify patterns and learnings
- Document insights for next quarter
Interpreting Scores
What Different Scores Mean
0.7-1.0: Strong performance
- Celebrate the achievement
- Consider if goal was ambitious enough
- Capture what worked well
0.4-0.6: Mixed results
- Not failure—important learning
- Understand what worked and didn't
- Consider what would have helped
0.0-0.3: Significant miss
- Investigate root causes
- Don't punish—learn
- Was the goal realistic? Were resources adequate?
Score Patterns to Watch
Consistently 1.0: Goals aren't ambitious enough
Consistently < 0.3: Goals unrealistic or systemic issues
High variance: Estimation problems
Declining over time: Possible engagement issues
Context Matters
The same score can mean different things:
0.7 with full effort: Good outcome, appropriate goal
0.7 with minimal effort: Goal was too easy
0.7 with major obstacles: Excellent outcome given context
Always discuss context alongside scores.
The Scoring Conversation
Questions to Ask
For each Key Result:
- What was our target? What did we achieve?
- What drove the result (positive and negative)?
- What would we do differently?
- What does this tell us about next quarter?
For the Objective overall:
- Did we move toward our objective?
- What did we learn?
- What capability did we build?
- What should we tackle next?
Avoiding Common Pitfalls
Don't: Justify why scores should be higher
Do: Accept scores honestly and learn from them
Don't: Blame external factors
Do: Acknowledge factors while taking ownership
Don't: Rush through scoring
Do: Have genuine learning conversations
Don't: Punish low scores
Do: Celebrate honest assessment and learning
Scoring Calibration
Consistency Matters
Scores are meaningful when consistent:
- Same scoring method across teams
- Same interpretation of the 0-1.0 scale
- Same approach to partial achievement
Calibration Sessions
Periodically review scoring consistency:
- Compare how different teams score similar situations
- Discuss ambiguous cases
- Align on interpretation
Avoiding Gaming
Watch for gaming behaviors:
- Setting easy targets
- Redefining success at quarter end
- Inflating progress updates
- Hiding problems until scoring
Counter with:
- Review of targets at quarter start
- Locked targets (no mid-quarter changes to goals)
- Honest culture that celebrates learning
- Separation from performance reviews
Aggregating Scores
Team Scores
Method 1: Average of Objectives
Team Score = Average of all Objective scores
Method 2: Weighted Average
Weight objectives by importance
Example:
- Obj 1 (Weight 50%): Score 0.8
- Obj 2 (Weight 30%): Score 0.6
- Obj 3 (Weight 20%): Score 0.9
- Team Score: (0.5 × 0.8) + (0.3 × 0.6) + (0.2 × 0.9) = 0.76
Company Scores
Aggregate team or department scores:
- Simple average of all objectives
- Weighted by strategic importance
- Focus on company-level OKRs only
Dashboard Presentation
| Objective | KR1 | KR2 | KR3 | Avg |
|---|---|---|---|---|
| Objective 1 | 0.8 | 0.7 | 0.9 | 0.80 |
| Objective 2 | 0.5 | 0.6 | 0.4 | 0.50 |
| Objective 3 | 1.0 | 0.8 | 0.7 | 0.83 |
| Team Average | 0.71 |
Post-Scoring: What Next?
Learning Documentation
After scoring, document:
What worked:
- Strategies that succeeded
- Practices worth repeating
- Capabilities built
What didn't work:
- Approaches that failed
- Obstacles encountered
- Things to avoid
Key learnings:
- Insights for future planning
- Capability gaps identified
- Process improvements needed
Informing Next Quarter
Scores inform next quarter planning:
Unfinished work: Do we continue this objective?
Exceeded targets: Do we raise the bar?
Learned limitations: Do we adjust expectations?
New insights: Do we shift focus?
Sharing Results
Make scores visible:
- Team reviews share with organization
- Trends tracked over time
- Learnings shared broadly
Transparency builds trust and enables learning.
Scoring Template
Key Result Scoring Template
KEY RESULT: [Description]
Target: [Number or outcome]
Actual: [What was achieved]
Calculation:
- Starting point: X
- Target: Y
- Achieved: Z
- Score: (Z - X) / (Y - X) = [Score]
Context:
- Key factors affecting result
- What worked / didn't work
- What we learned
Final Score: [0.0-1.0]
Objective Scoring Template
OBJECTIVE: [Name]
Key Results:
- KR1: [Score]
- KR2: [Score]
- KR3: [Score]
Objective Score: [Average]
Retrospective:
- Did we achieve the objective? (Beyond just numbers)
- What would we do differently?
- What will we do next?
Conclusion
Scoring turns OKRs from aspirational statements into learning tools. Done right, it creates accountability without punishment, enables continuous improvement, and provides data for better planning.
Remember: the goal isn't a high score. The goal is accurate assessment that enables learning. A honest 0.4 teaches more than an inflated 0.8.
Embrace the scoring process as a learning opportunity. Celebrate what worked. Understand what didn't. Apply those insights to do better next quarter.
That's how OKRs drive continuous improvement.
Related Articles:
- The Anatomy of a Great Key Result
- Common OKR Mistakes and How to Avoid Them
- How to Run Effective OKR Check-ins
Ready to align your team with OKRs?
Start tracking your objectives and key results with Leemu. Free to get started, no credit card required.
Get Started Free

