OKRs for small teams are a way to choose a few things that matter this quarter, say them in plain words, and measure progress with a handful of numbers. OKR means Objectives and Key Results. The idea is simple, the failure is also simple: too many goals, vague numbers, and nobody looking again after week one. This guide shows how to write them, with examples, how to check in, and how to keep the habit going.
The parts
- Objective. A short sentence on what you want, which should inspire and be clear. "Make onboarding painless for new customers."
- Key results. Two to four numbers that show whether you got there, each with a start and a target. "Cut the average time to first value from 9 days to 3."
- Initiatives. The work you do to move the numbers. They are not key results. "Rewrite the welcome emails" is an initiative, because finishing it does not prove anything improved.
Writing a good objective
- Pick the one thing. Ask: if we achieved only one thing this quarter, what would it be?
- Use plain words. No jargon. A new hire should understand it in one read.
- Keep it within reach of the team. If it depends on someone outside the team, it is a wish.
- Keep it to a period. A quarter is the usual length. A year is too long to steer by.
Writing key results that mean something
A key result has a measure, a start value and a target. Good ones count outcomes, such as customers, time, errors, money or satisfaction. Poor ones count activity, such as meetings held or posts published.
| Weak | Better |
|---|---|
| Launch a new help centre | Cut support tickets about setup from 120 a month to 70 |
| Do more sales calls | Raise the share of demos that become trials from 20% to 35% |
| Improve quality | Reduce customer complaints from 14 a month to 6 |
| Hire a designer | Ship the redesigned checkout and lift completed checkouts from 61% to 68% |
The numbers in the table are examples for illustration, not benchmarks. Use your own starting point, from your own data.
Before you commit, ask for each key result: can we measure it today, who updates it, and how often?
Size and cadence
- How many. One to three objectives per team, two to four key results each. A team of ten with five objectives has no focus.
- How ambitious. Many teams aim so that reaching about 70% is a good result. Others set targets they expect to hit. Choose one style and tell everyone, or people will argue about what 60% means.
- Weekly check in. Fifteen minutes. Each key result gets a fresh value and a one line comment, plus a confidence level: on track, at risk, off track. Spend time on the at risk ones.
- End of quarter review. Score each result, write what you learned, and decide what carries over. Then pick the next set. See also how to run a weekly planning meeting.


