Objectives and Key Results give a small team a shared sense of what matters this quarter and how everyone will know whether they got there. They work especially well when you are short on people and cannot afford to pull in a dozen directions at once. The trap is treating them as a glorified task list. This guide covers what OKRs are, how many to set, how to write key results you can actually measure, and the rhythm that keeps them alive.
What are OKRs?
OKRs are a lightweight goal-setting method built from two parts. The objective is a short, qualitative statement of what you want to achieve — it should be memorable and a little inspiring. The key results are the two to four measurable outcomes that prove you reached it. If every key result hits its target, the objective is, by definition, done. The method forces a team to agree in advance on what success looks like, instead of arguing about it at the end of the quarter.
Objective versus key result
People mix these up constantly, so it is worth being strict. An objective answers “where do we want to go?” and carries no number. A key result answers “how will we know we arrived?” and always carries a number. “Become the first choice for local customers” is an objective. “Lift the repeat-order rate from 40% to 55%” is a key result. If a line has no metric, it is not a key result — it is either part of the objective or a task.
How many OKRs should a small team set?
Fewer than you think. For a team of five to fifteen people, aim for one to three objectives, each with two to four key results. That is the whole quarter. A small team that sets five objectives has really set none, because attention is the scarce resource, not ambition. If you struggle to cut, ask which objective you would protect if the quarter fell apart. Start there, and let the rest wait.
How do you write measurable key results?
A good key result names a metric, a starting point and a target, so there is no debate later about whether you hit it. Prefer outcomes over activities: “publish 10 articles” measures effort, while “grow organic sign-ups from 120 to 200 a month” measures the result you actually want. For stretch goals, set the bar high enough that landing around 70% still counts as a strong quarter. If you hit 100% of every key result every time, your targets are too soft and are teaching the team to sandbag.
A worked example
Here is a single-quarter set for a small operations team at a services company. Treat it as a pattern, not a prescription.
- Objective: Make onboarding something new clients rave about.
- Key result 1: Cut average time-to-first-value from 21 days to 10 days.
- Key result 2: Raise the onboarding satisfaction score from 3.8 to 4.5 out of 5.
- Key result 3: Reduce setup-related support tickets per new client from 6 to 2.
Notice that none of these name a task. “Write a welcome guide” might help, but it belongs on the backlog, not in the key results.
What cadence keeps OKRs alive?
Set OKRs once a quarter, ideally in the week before it starts. Then check in weekly or every two weeks in a short standing meeting: each owner says where their key results stand and what is blocking them. At the end of the quarter, grade every key result on a 0.0 to 1.0 scale, where 1.0 means the target was fully met and 0.7 means solid progress. The grade is a prompt for an honest conversation, not a performance-review score. Spend more time on what you learned than on the number itself.
Common pitfalls
- Too many OKRs. Four objectives with five key results each is a wish list, not a plan.
- Tasks masquerading as key results. If you can check it off in an afternoon, it is a task, not an outcome.
- Sandbagging. Targets you are certain to hit protect no one and teach nothing.
- Set and forget. OKRs written at the start of the quarter and reopened at the end were just decoration.
- Grading as judgement. If a low score means punishment, people will aim low next time.
Keep the first quarter deliberately small. Set one objective, run the weekly check-ins, grade honestly, and adjust. The habit matters more than the paperwork.
Frequently asked questions
What is the difference between an objective and a key result?
An objective is a short, qualitative statement of what you want to achieve. A key result is a measurable outcome that proves you got there, and it always carries a number.
How many OKRs should a small team set?
Aim for one to three objectives, each with two to four key results, for the whole quarter. A small team that sets more has usually set none, because attention is the limit, not ambition.
What does a 70% score mean?
For stretch goals, landing around 70% of your targets is a strong quarter. If you consistently hit 100%, your targets are probably too easy.
How often should we review OKRs?
Set them once a quarter, check in weekly or every two weeks, and grade each key result on a 0.0 to 1.0 scale at the end of the quarter.
FulcrumGrid Command Center
Keep your OKRs in one place
FulcrumGrid Command Center lets you track objectives, owners and KPIs together, so your OKRs stay visible instead of fading into a forgotten doc.