To write an OKR, pick one ambitious Objective — a qualitative direction worth a quarter — and pair it with two to four measurable Key Results that prove you reached it. For example: Objective — “Make new teams love their first week”; Key Results — lift week-one activation from 40% to 60%, cut time-to-first-goal under 5 minutes, and get 30% of new teams to invite a teammate.
OKRs look simple and trip up almost everyone the first time — usually by turning Key Results into a to-do list. This is the hands-on version for small teams of 5 to 50: a formula, real rewrites, and a test you can run on any OKR. New to the framework itself? Start with the OKR guide; for the bigger picture, see goal setting for small teams →
The OKR formula
Two sentence templates keep the two halves in their lanes — a qualitative Objective, and measurable Key Results:
Objective: [ambitious, qualitative direction] — so [why it matters this cycle]. Key Result: [metric] from [baseline] to [target] by [date].
Filled in: Objective — “Make the first week effortless, so new teams stick around.” Key Results — “activation from 40% to 60%,” “time-to-first-goal from 12 minutes to under 5,” and “invited-a-teammate rate from 15% to 30%” — all by the end of Q3. One direction, three numbers that prove it.
How to write OKRs, step by step
Six moves take you from a fuzzy ambition to an OKR your team can rally around.
Start from one priority worth a quarter
Pick the single most important thing to move this cycle — not ten. A small team’s focus is its advantage, so spend it on one or two objectives, not a wish list.
Write the Objective — qualitative and memorable
State the direction in plain words: “Make new teams love their first week.” It should inspire and be worth rallying behind. No numbers here — that’s the job of the key results.
Ask “how would we know?”
For each objective, name the two to four numbers that would prove it’s met. If every key result hit its target, the objective should be genuinely, undeniably achieved.
Make every Key Result an outcome, not a task
“Ship the redesign” is a to-do; “lift activation from 40% to 60%” is a result. If you can simply tick it off, rewrite it as the change it’s supposed to create.
Set the stretch so ~0.7 is a win
Good OKRs are ambitious. Calibrate targets so hitting about 70% counts as strong. If you’d always score 1.0, aim higher — and keep scores away from bonuses so nobody sandbags.
Give it an owner and a check-in rhythm
One accountable name per objective, plus a weekly or biweekly look at each key result. OKRs reviewed only at quarter-end are decoration, not direction.
Turn tasks into real Key Results
The most common mistake is listing tasks as key results. The fix is to ask what each task is for — then measure that. Three rewrites:
“Launch the new onboarding flow.”
“Lift week-one activation from 40% to 60% by the end of Q3.”
“Publish 12 blog posts.”
“Grow content-sourced signups from 20 to 60 per month by Q4.”
“Run a customer survey.”
“Raise NPS from 30 to 45 by the end of Q3.”
Want complete OKRs by team to adapt? See OKR examples by team →
Run it through the OKR test
Before you commit an OKR, run it through five quick checks. Fail any, and rewrite before the cycle starts.
Is it qualitative?
The Objective sets direction in words, not numbers. If it reads like a metric, it’s a key result wearing the wrong hat.
Do the Key Results prove it?
If all key results hit, is the objective undeniably met? If not, you’re measuring the wrong things.
Are Key Results results, not tasks?
Each one names a number that moves — not an activity you can tick off. Outcomes, never to-dos.
Is it genuinely ambitious?
Targets set so that ~0.7 is a strong result. A plan you’re certain to fully hit isn’t an OKR, it’s a forecast.
Is it few enough?
One to three objectives per team, two to four key results each. More than that and nobody tracks them.
Common mistakes when writing OKRs
Most OKR trouble starts at the writing stage. Watch for these four — and see the full list across writing, running, and scoring in common OKR mistakes →
An Objective that’s really a metric
“Grow MRR to $20k” is a key result, not an objective. The objective is the direction behind the number — say why it matters.
Key Results that are tasks
“Launch X,” “hire Y,” “run Z” are activities. Rewrite each as the outcome it should produce, or it’s just a to-do list.
Too many Key Results
Five or more per objective and none get real attention. Keep the two to four that genuinely prove the objective.
A Key Result with no baseline
“Reach 60% activation” hides whether that’s a nudge or a moonshot. Always write “from X to Y” so the stretch is honest.
In OKR mode, Celorly guides you to write a qualitative Objective, then add its Key Results as measurable sub-goals — and at the end of the cycle it scores each one from 0.0 to 1.0 and rolls them up. The framework shapes the fields, so OKRs come out well-formed by default. Weighing up tools more broadly? See OKR software for small teams →
How to write OKRs — quick answers
How do I write an OKR?+
Pick one ambitious Objective (a qualitative direction), then add two to four measurable Key Results that would prove it’s met. A quick template — Objective: “[direction] — so [why]”; Key Result: “[metric] from [baseline] to [target] by [date].”
How many Key Results should each Objective have?+
Two to four. Fewer than two and the objective isn’t well-defined; more than four and nobody tracks them all. Pick the handful that genuinely prove it.
What makes a good Objective?+
It’s qualitative, ambitious, and memorable — a direction worth rallying behind, like “make onboarding effortless.” If it has a number in it, that’s a key result, not the objective.
Should Key Results be tasks or outcomes?+
Outcomes. “Ship the new flow” is a task; “lift week-one activation from 40% to 60%” is the outcome that task is meant to create. Measure the result, not the activity.
How ambitious should OKRs be?+
Ambitious enough that hitting around 70% is a good result. If your team consistently scores 100%, the targets are too easy. Keep scores out of performance reviews so nobody lowballs them.
Should I write OKRs or SMART goals?+
Use OKRs to align a team around one ambitious direction; use SMART to sharpen a single goal. A strong key result is usually a SMART goal, so they fit together rather than compete.