Lesson 11

How to Score and Review OKRs

Great OKRs are not set-and-forget goals. The review system is what makes them operational and what turns misses into learning instead of confusion.

Key takeaways
  • Weekly review is often more important than perfect initial wording.
  • Confidence signals help teams surface risk before quarter-end.
  • Scoring should support learning, not punish ambition.

Run weekly reviews for decision-making, not status theater

The best check-ins are not long status meetings. Metrics should already be updated asynchronously. The meeting should focus on red flags, changing confidence, blockers, and decisions needed to move the KR.

Use confidence alongside progress

A KR can show early numeric progress while the team already knows it is at risk. Confidence makes that visible. It is a forecast signal that helps management intervene before the quarter is lost.

Score without turning the system punitive

OKR scoring should reveal whether the team set meaningful stretch and whether the assumptions were right. If teams are punished for missing hard goals, they will start gaming the system with safer targets.

Put this into practice
  • Use a weekly agenda that starts with low-confidence KRs and blocked items first.
  • Keep the scoring scale simple and explain how stretch targets should be interpreted before the cycle begins.
  • Hold a short retrospective after scoring to decide what should change next cycle.

Review quality determines whether OKRs become a living management system. The next lesson focuses on the most common mistakes that derail good intentions.

Related examples
Ready to run this as a real system?

Use okr.mx to turn the lesson into a live cadence with shared ownership, measurable progress, and weekly reviews instead of spreadsheet drift.

Start for free