SpunkArt
Numbers and money maths

How to write, track and score OKRs

OKRs, short for objectives and key results, are a goal-setting format. The objective says where you want to go. Two to five key results say how you will know you got there. This page covers writing them, tracking them in a plain spreadsheet, and scoring them honestly.

The parts of an OKR

  • Objective: a short, qualitative statement of what you want to achieve this period. It should be clear enough that anyone on the team can repeat it.
  • Key results: measurable outcomes with a start value and a target value. If you cannot put a number on it, it is probably a task, not a key result.
  • Initiatives: the projects you will do to move the key results. These are tracked separately.

Turning a vague goal into an OKR

Weak: “Improve the website.” Better:

Objective: Make the help pages good enough that customers solve problems on their own.

  • KR1: Raise weekly help-page sessions that end without a support ticket from 120 to 200.
  • KR2: Cut average first-reply time on tickets from 48 hours to 24 hours.
  • KR3: Publish answers for the 30 most frequent ticket topics.

Each key result is an outcome you can check at the end of the quarter, not an activity like “write more articles”.

Scoring a key result

A common convention scores each key result from 0.0 to 1.0, based on how far you moved from the start value toward the target:

score = (current − start) ÷ (target − start)

The same formula works when the goal is to reduce a number, because both the top and the bottom are negative. Cap the score at 1.0 and at 0.0.

Worked example at the end of the quarter.

  • KR1: sessions reached 168. (168 − 120) ÷ (200 − 120) = 48 ÷ 80 = 0.6
  • KR2: reply time reached 36 hours. (36 − 48) ÷ (24 − 48) = −12 ÷ −24 = 0.5
  • KR3: 30 of 30 topics published = 1.0
  • Objective score: (0.6 + 0.5 + 1.0) ÷ 3 = 0.7

Reading the score

Teams that set ambitious targets on purpose often treat about 0.6 to 0.7 as a good result. A team that scores 1.0 on everything is probably setting targets it already knows it can hit. A score near 0 means the target, the plan or the measurement needs a second look. Whatever scale you choose, agree on it before the quarter starts.

Tracking without special software

A spreadsheet is enough. Use one row per key result:

Key resultStartTargetCurrentScoreConfidenceNote
KR1 sessions1202001680.6MediumNew search box helped
KR2 reply hours4824360.5LowOne person on leave
KR3 topics030301.0Done

In the score column, a formula such as =MAX(0,MIN(1,(D2-B2)/(C2-B2))) applies the formula and the caps. Update the current value once a week and write one honest sentence about confidence.

A weekly check-in in four questions

  1. What moved since last week, and why?
  2. How confident are we in each key result now?
  3. What is blocking progress?
  4. What will we do differently this week?

Common mistakes

  • Too many OKRs. One to three objectives per team per quarter keeps focus.
  • Task lists disguised as key results. “Launch feature X” is an initiative. Measure what the feature should change.
  • Tying scores to pay. People then set safe targets, which defeats the purpose.
  • Setting and forgetting. Without weekly updates, the end-of-quarter score is a surprise.

FAQ

How are OKRs different from KPIs?

A KPI is a health metric you watch all the time. An OKR is a time-boxed push to change something. A key result can aim to move a KPI.

Should individuals have OKRs?

Some teams do, but many keep them at team level, so people work together on shared outcomes.