Guide: how to create OKRs that actually work

We've covered the history behind OKR, how the model works in practice, and the difference from KPI. What's left is the practical part: how do you actually write an OKR, and in what order?

Eight steps

1. Start from strategy, not the to-do list

Before writing a single Objective, ask which strategic goal it's meant to support. An OKR that can't be tied to a clear strategic priority is, in practice, just a task with a fancier name.

2. Set the timeframe before anything else

Decide the period before you write the Objective. A quarter is the default and works best for most OKRs — six months should be the absolute outer limit, never a year. An OKR stretching longer than that loses its point: too distant to steer daily work, too far off to feel real once it's time to evaluate it.

3. Write the Objective as a direction, not a result

The Objective should answer what, not how much. Write it without numbers. Test it by reading it aloud: does it feel like something you want to work toward, or something that already feels done on paper? If nobody on the team feels the slightest bit energized reading it, rewrite it.

4. Set the ambition level correctly

An Objective should be challenging enough that you don't already know you'll hit it. The right level is often described as roughly 70 percent achievement counting as a good effort — if you hit 100 percent every time, you've probably set the bar too low.

5. Write 3–5 Key Results per Objective

Each Key Result should be measurable, concrete, and time-bound to the period. Avoid phrases like "improve" or "increase" without a number attached — it isn't a Key Result until you can say exactly whether it was met or not.

6. Run the reverse test

Ask: if all the Key Results turn green, is the Objective actually achieved? If the answer is no, a Key Result is missing. If the answer is yes but it felt too easy to hit them all, either the Objective is too narrow or the Key Results are too easy.

7. Disconnect bonuses, set a follow-up rhythm

Keep Key Results separate from pay and bonuses — otherwise ambition quietly erodes on its own. Layer tighter check-ins (weekly or biweekly) on top of the timeframe you already set in step 2, to see whether you're green, yellow, or red.

8. Evaluate and capture the lessons

When the period ends, score each Key Result (for example 0–1.0) and ask why the outcome turned out the way it did — not just whether it did. An OKR that was missed but produced a clear lesson is often worth more than one that was hit without anyone learning anything.

Use the checklist for creating OKRs to check your next set against these steps.