OKR Scoring

What is OKR Scoring?

OKR scoring is the practice of grading each key result at the end of a cycle, usually from 0.0 to 1.0, to show how much of the target was achieved and to inform the next round of goal-setting.

Updated November 2026 · 2 min read


How OKR scoring works

At the end of the quarter, each key result gets a score based on how close the team came to the target. The objective's score is usually the average of its key results. The most common scale, popularized by Google, runs from 0.0 to 1.0.

ScoreColourWhat it usually means
0.0 to 0.3RedLittle progress; the target was missed by a wide margin
0.4 to 0.6YellowReal progress, but short of the target
0.7 to 1.0GreenThe target was met or nearly met

For a measurable key result, scoring is often linear: raising NPS from 30 to a target of 50, but reaching 42, scores 0.6. For binary key results, such as "launch in Germany," the score is 0 or 1, unless partial credit has been agreed in advance.

Aspirational vs committed OKRs

How to read a score depends on the type of OKR. Google distinguishes two kinds:

Committed OKRsAspirational (stretch) OKRs
PurposeThings the team must deliverAmbitious goals that push for a step change
Expected score1.0Around 0.6 to 0.7
What a low score meansA real miss that needs explainingNormal; the bar was set high on purpose
What a 1.0 meansExpectedThe target may have been too easy

Mixing the two without labeling them causes confusion. A 0.7 on a stretch goal is a good result; on a committed goal it is a failure.

An example

A product team ends the quarter with three key results under the objective "Make onboarding effortless." Time to first value fell from 9 days to 5, against a target of 3: a score of 0.67. Setup completion rose from 40% to 58%, against a target of 60%: 0.9. The planned in-app guide shipped, so that binary key result scores 1.0. The objective averages 0.86. In the retrospective, the team notes that the time-to-value target was a stretch and sets a more realistic one for next quarter.

Alternatives to numeric scoring

  • Confidence-based scoring: track how likely each key result is to be met through the quarter, as in an OKR check-in
  • Simple status: achieved, partially achieved, missed
  • Percentage of target, used by teams that find decimals less intuitive

Using scores well

OKR scores are for learning, not for appraisal. Google and most OKR practitioners advise keeping them separate from performance ratings and bonuses. When scores drive pay, people set easy targets and the system loses its point. Use the scores in a short retrospective: which goals were too easy, which were unrealistic, and what got in the way. That reflection is what improves the next set of OKRs. See also OKR vs KPI and leading and lagging indicators. Many companies review company-level scores at the quarterly business review, where they feed decisions about the next quarter's priorities and strategic bets.

Frequently asked questions

What is a good OKR score?

For aspirational OKRs, a score around 0.6 to 0.7 is usually considered good, since the targets are meant to be ambitious. Consistently scoring 1.0 suggests goals are too easy. For committed OKRs, the expected score is 1.0, and anything less needs an explanation and usually a plan to recover.

Should OKR scores be tied to performance reviews?

Most practitioners advise against it. Linking OKR scores to pay or ratings encourages people to set safe targets they know they can hit, which defeats the purpose of ambitious goal-setting. Scores work best as a learning tool for the team, while performance reviews consider a wider picture of each person's contribution.

How do you score a binary key result?

A binary key result, such as launching a product or signing a partner, is usually scored 0 or 1: it happened or it did not. Some teams agree partial credit in advance for clear milestones. A better fix is often to rewrite the key result as a measurable outcome, such as the number of customers using the new product.