OKR guide

    What is an OKR?

    OKR stands for Objectives and Key Results. An objective is the outcome you want to reach; key results are the measurable signs that you are getting closer. Most teams set them quarterly and review them monthly.

    By Reuben Chircop, OKR coach and creator of OKRgen

    The definition

    An OKR has two parts. The objective is qualitative. It describes an outcome and answers the question: where do we want to go? It should be clear enough that people remember it and important enough that they care.

    The key results are measurable. Each one has a baseline and a target, and together they answer a different question: how will we know we got there? If the objective is the destination, the key results are the signs along the road.

    John Doerr put it as a single sentence you can test any OKR against: "I will [objective] as measured by [key results]." If your draft does not read naturally in that sentence, something is missing.

    The method started with Andy Grove at Intel and was later popularised by John Doerr and Google.

    For a term you want to look up, use the OKR glossary.

    One worked example

    Here is a single objective with three key results, written the way we write them on our OKR examples page. The figures are illustrative.

    Objective

    Make new customers successful in their first month

    Key results

    • Increase the share of new accounts that complete setup in their first week from 45% to 70%Why it is a measure: It describes a change in customer behaviour, not a piece of work someone can finish.
    • Reduce support tickets from customers in their first 30 days from 120 to 70 per monthWhy it is a measure: It is a number that only moves if the experience actually gets easier.
    • Raise first month retention from 80% to 88%Why it is a measure: It is the outcome the whole objective exists for, so it cannot be ticked off by effort alone.

    None of these says what to build or who should do it. That is deliberate. The work belongs somewhere else, which is the part most guides leave out.

    The third layer most guides skip: initiatives

    Most explanations of OKRs stop at two layers. In practice there are three, and the third is where the work actually lives.

    • Objective: the outcome we are trying to reach.
    • Key result: how we will know we are getting closer.
    • Initiative: the actual work, often needing several skill sets and more than one team.
    Objective, key result and initiativeThree layers with their purpose and common error below each title. Initiative moves the key result, which moves the objective.ObjectiveBecomes a taskwearing the wordThe outcome you aretrying to reachKey resultBecomes the task list,so it stops measuringHow you know you aregetting closerInitiativeMissing entirely, so theother two get corruptedThe work, often across severalteams and skill setsmovesmoves
    If an objective could be marked complete, it is not an objective. If a key result is something a person can finish on a Thursday, it is not measuring anything.

    When there is nowhere to put the work, it leaks upwards. Tasks end up written as objectives, or squeezed into key results, and both stop doing their job. I have seen this with team after team. Once initiatives existed, the other two could finally be what they were supposed to be.

    The tick off test

    There is one quick test I use on every draft.

    If an objective could be marked complete, it is not an objective. It is a task wearing the word.

    The same applies one layer down. If your key result is something a person can complete on a Thursday, it is not measuring anything. It is a task, and it belongs with the initiatives.

    A story: sixteen objectives

    The clearest lesson I have had in all of this came from one team over one year.

    In the first quarter, their OKRs were handed down from above. Nobody had been part of writing them, so nobody owned them, and they failed for lack of buy in.

    In the second quarter we built them together. That fixed the ownership and created a new problem: we came out with sixteen objectives. Most of them were a task list with percentages attached.

    So we overcorrected. We moved the tasks down into the key results. It looked tidier, and it was equally wrong. The key results became the task list and stopped measuring anything. What fixed it was adding initiatives as a separate layer, so the tasks had a home of their own.

    The third quarter was better written but still missed, because nobody looked at the OKRs again once they were agreed.

    Good objectives with no rhythm behind them are just a better document.

    The fourth quarter is where it came together. We started with the mission, then the leadership team built about six objectives together, each with six to eight key results. We refined them fortnightly at first, and later quarterly, once the habit had stuck.

    How many objectives and key results

    Aim for two to four key results per objective, and a small number of objectives per team each quarter. If people cannot remember their objectives without looking them up, there are too many.

    Leadership level sets can carry more key results, as in the story above, because they cover more of the organisation. Team level sets should stay lean. If you want a format to start from, copy this OKR template.

    For a change outside team planning, use a lighter set of personal OKRs rather than trying to measure your whole life.

    OKRs vs KPIs, briefly

    KPIsOKRs
    Monitor the health of the businessDrive a deliberate change
    Running the engineSteering it somewhere new

    The two work together: when a KPI drifts, an OKR can be how you fix it. See the full comparison of OKRs and KPIs.

    OKRs are a rhythm, not an event

    OKRs only work if you come back to them. A simple rhythm is enough: a short monthly sync per team to check the key results are still the right ones, a proper quarterly review of what you achieved and learned, and Q4 to draft and agree next year's objectives.

    OKRs are not a document, they are a cadence.

    When you are ready to plan next year's OKRs, start earlier than feels necessary.

    What OKRs are not

    OKRs are not a task list, and they are not a way to rate individual performance. When OKRs are tied to pay or appraisals, people set safe targets they know they can hit, and the ambition that makes the method useful disappears. Use them to steer the organisation, not to grade the people in it. If yours are stalling, see why OKRs fail.

    When the blank page is the problem

    Even when people understand the three layers, producing a decent first draft is where they stall. Turning a strategy into objectives, key results and initiatives from nothing is hard work, and it is often the moment teams give up.

    The free generator drafts an objective with measurable key results. The full OKRgen builder then helps you add initiatives, check the set's health and track it. Treat the draft as a starting point worth arguing about, not the answer.

    FAQ

    OKR stands for Objectives and Key Results. The objective is the outcome you want to reach, and the key results are the measurable signs that tell you whether you are getting closer to it.

    A goal on its own often stops at the intention. An OKR pairs the intention with a small number of measures, each with a starting point and a target, so everyone can see what progress looks like and argue about the same numbers.

    Most teams set OKRs quarterly and look at them monthly. The monthly check is short and asks whether the key results are still the right ones. The quarterly review is where you look at what you achieved, what you learned and what changes next.

    No. When OKRs decide pay or appraisals, people set targets they know they can hit, and the ambition that makes OKRs useful disappears. Use them to steer the work of the organisation, and assess individual performance separately.

    Write your first OKR set