An OKR (Objectives and Key Results) is a goal-setting method that pairs one ambitious Objective — what you want to achieve — with two to four measurable Key Results that prove you got there. 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 to under 5 minutes,” and “get 30% of new teams to invite a teammate.”
OKRs were made famous by Intel and Google, but you don’t need to be Google to use them. Stripped of the corporate mythology, an OKR is simple: pick a direction that matters, then name the handful of results that would prove you’re winning. This guide is for small teams of 5 to 50 who want that focus without the overhead. For the bigger picture, see goal setting for small teams →
Objectives vs key results
Every OKR has two halves — and mixing them up is the most common beginner mistake.
The Objective — where you’re headed
Qualitative, ambitious, and memorable. It sets direction and should feel worth rallying behind. One per OKR — think “become the easiest goal tool to adopt,” not a number.
The Key Results — how you’ll know
Two to four measurable outcomes that prove the objective is met. Numbers, not tasks. If you can’t put a number on it, it isn’t a key result.
How to write good OKRs
Five steps to go from a fuzzy ambition to an OKR your team can rally around. Want the deeper walkthrough — with a formula and an OKR test? See how to write OKRs →
Pick an objective that matters
Choose one ambitious, qualitative direction for the cycle. It should be memorable and worth the effort — not a metric, and not a laundry list.
Choose 2–4 key results that prove it
Ask: if these numbers move, is the objective genuinely met? Fewer, sharper key results beat a long list nobody tracks.
Make key results outcomes, not tasks
“Launch the new onboarding” is a task; “lift week-one activation from 40% to 60%” is an outcome. Measure the result, not the activity.
Set the bar as a stretch
Good OKRs are ambitious — aim so that hitting around 70% is a strong result. If you always score 100%, you’re sandbagging.
Cascade and align
Connect team OKRs up to the company’s and down to individuals, so everyone sees how their work ladders up. Alignment is half the value.
Objective: Make new teams love their first week. Key results: (1) lift week-one activation from 40% to 60%, (2) cut time-to-first-goal from 12 minutes to under 5, and (3) get 30% of new teams to invite a teammate — all by the end of Q3. One direction, three numbers that prove it.
OKR examples by team
Real, small-team OKRs — one objective, a few measurable key results each.
Objective: Become a go-to resource on goal-setting
KR1: grow organic traffic 2k → 8k/mo · KR2: 500 newsletter signups · KR3: 20 referring domains — by Q4.
Objective: Build a repeatable outbound motion
KR1: 25 qualified demos/mo · KR2: 20% demo → trial rate · KR3: $10k new MRR — by Q3.
Objective: Make the first week effortless
KR1: activation 40% → 60% · KR2: time-to-first-goal under 5 min · KR3: NPS 30 → 45 — by Q3.
Objective: Turn new teams into sticky ones
KR1: churn 4% → 2.5% · KR2: 60% of teams set a quarter plan · KR3: 40 reference customers — by Q3.
Want more? See OKR examples for every team →
OKRs vs KPIs
They work together, but they’re not the same thing.
OKRs drive change
An OKR is a bet on moving something forward this cycle — ambitious, temporary, and retired when the cycle ends.
KPIs track health
A KPI is a metric you watch continuously to keep the business healthy — churn, uptime, margin. Steady, not a stretch.
A useful rule: if you want a number to change, it’s an OKR; if you want it to stay in a safe range, it’s a KPI. For the full comparison, see OKR vs KPI →
OKRs vs SMART goals — which should you use?
SMART goals shape one well-formed goal; OKRs align a whole team around an ambitious objective. They’re complementary — a strong key result is often just a SMART goal. Not sure which fits? Read the SMART goals guide or compare them in OKR vs SMART goals →. Celorly supports both.
How to score OKRs
At the end of the cycle, score each key result from 0.0 to 1.0 — the share of the target you hit — and average them for the objective’s score.
Here’s the counterintuitive part: a score around 0.7 is the target, not a failure. If you consistently hit 1.0, your OKRs aren’t ambitious enough. And keep scores away from performance reviews — the moment OKRs affect someone’s bonus, people start sandbagging. For the scale, the formula, and how to run a grading session, see OKR grading & scoring →
Common OKR mistakes
Most OKR failures aren’t about the writing — they’re about how the OKRs get used. For the full field guide across the whole cycle, see common OKR mistakes →
Too many OKRs
One to three objectives with a few key results each is plenty. A dozen means none get real attention.
Key results that are tasks
“Ship the redesign” is a to-do. Measure the outcome the redesign is supposed to create.
Sandbagging
Setting targets you know you’ll hit defeats the point. Aim for a stretch where about 0.7 is a win.
Set and forgotten
OKRs reviewed only at quarter-end are decoration. Check in on a weekly or biweekly rhythm.
Celorly runs the whole OKR loop for small teams: it prompts sound objectives and measurable key results, cascades them from company to person, flags what’s slipping mid-cycle, and scores each one at the close — guided when you’re learning, out of your way when you’re not. Comparing options? See what matters in OKR software for small teams →
OKRs — quick answers
What does OKR stand for?+
Objectives and Key Results. The objective is the ambitious direction; the key results are the two to four measurable outcomes that prove you reached it.
What’s an example of an OKR?+
Objective: “Make new teams love their first week.” Key results: lift activation from 40% to 60%, cut time-to-first-goal to under 5 minutes, and get 30% of new teams to invite a teammate — by the end of Q3.
How many OKRs should a team have?+
Fewer than you’d think — usually one to three objectives per team per cycle, with two to four key results each. Focus is the whole point.
OKRs vs KPIs — what’s the difference?+
OKRs drive change you want to make this cycle; KPIs are health metrics you watch continuously. If you want a number to move, it’s an OKR; if you want it to stay in range, it’s a KPI.
What’s a good OKR score?+
Around 0.7 out of 1.0. OKRs are meant to be a stretch, so consistently scoring 1.0 usually means the targets were too easy. Keep scores out of performance reviews so nobody sandbags.
OKRs or SMART goals — which should my team use?+
SMART shapes a single well-formed goal; OKRs align a team around an ambitious objective. They’re complementary — many teams write key results as SMART goals. Celorly supports both.