Back to blog
·5 min read

What OKRs are and how to use them at your company (with examples by team)

OKR stands for Objectives and Key Results. It is a goal-setting method that gets a team pushing in the same direction over a short period, usually a quarter. Each objective says what you want to achieve; each key result says how you will know you got there.

Everyone from startups to companies with thousands of people uses them. They work when used to focus, and fail when they turn into one more form to fill in. This guide explains how to do the first and avoid the second.

The two parts of an OKR

The objective

A qualitative sentence that says where you want to go. It should be important, concrete and understandable without explanation. No numbers: numbers go in the key results.

  • Good: "New hires feel part of the team from their first month."
  • Good: "Be the easiest option to buy from in our category."
  • Bad: "Improve." (improve what?)
  • Bad: "Sell 20% more." (that is a key result, not an objective)

The key results

2 to 4 per objective. Each has a starting value, a target and a date (the end of the period). Together, if met, they prove the objective was achieved.

  • Cut 6-month turnover from 18% to 10%.
  • Raise onboarding satisfaction from 3.6 to 4.3 out of 5.
  • Get 90% of new hires a 30-day check-in with their manager (40% today).

The simplest test: if you meet every key result but the objective was not achieved, the key results were badly chosen.

Outcomes, not tasks

The most common mistake is writing tasks as key results: "launch the onboarding program", "implement the new CRM", "run four workshops". Tasks matter, but they do not say whether anything changed. You can run four workshops and nobody learns anything.

To turn a task into an outcome, ask: why am I doing this? Which number should move if it works? "Run four feedback workshops" becomes "go from 61% to 75% favorable on my manager gives me useful feedback". The workshops stay in the work plan, as one way to get there.

Ambitious on purpose

With OKRs, targets are set above what would feel comfortable. That is why getting 70% of the way is usually considered a good result. If a team always hits 100%, its targets are too easy; if it always stays at 30%, they are unrealistic or execution is failing.

Some companies separate two kinds: committed OKRs (expected at 100%, like launching something with a fixed date on time) and aspirational OKRs (60% or 70% is expected). If you use both, label each one.

Cascading without bureaucracy

The classic idea is that the company sets 3 to 5 OKRs and each team sets its own to contribute. The mistake is copying OKRs top-down word for word, or asking every person for their own OKRs. That produces hundreds of OKRs nobody reviews.

  1. Leadership sets the company OKRs for the period.
  2. Each team proposes its own: some contribute to company OKRs, others are team-specific. Not everything has to be 100% aligned.
  3. They are reviewed together to spot gaps (a company objective nobody contributes to) and conflicts (two teams pulling in opposite directions).
  4. OKRs go down to team level. For individuals, use individual goals in the performance review.

The rhythm: how they are reviewed

  • Start of the quarter: OKRs are set in one or two sessions, not over a month.
  • Every week or two: a short team meeting to update each key result’s current value and discuss what is blocking progress.
  • Mid-quarter: check whether any key result stopped making sense. Changing it is allowed if the context changed, and you should say why.
  • At the close: score each key result from 0 to 1 (or 0% to 100%), write down what you learned and use it to set the next ones.

Write your OKRs, check they are not tasks and download them with progress calculated:

OKR template in Excel (free)

Examples by team

People (HR)

  • Objective: our managers give useful, frequent feedback.
  • Key result: go from 61% to 75% favorable on "my manager gives me useful feedback" in the pulse survey.
  • Key result: get 30 of 34 managers holding a monthly one-on-one with each person (8 today).

Sales

  • Objective: corporate clients choose us for more than price.
  • Key result: raise the close rate on corporate accounts from 18% to 25%.
  • Key result: cut the average discount given from 12% to 8%.

Customer support

  • Objective: solving a problem with us is easy.
  • Key result: raise first-contact resolution from 64% to 80%.
  • Key result: lower the customer effort score (CES) from 3.4 to 2.5 out of 5.

Operations

  • Objective: deliver on time, every time.
  • Key result: raise on-time deliveries from 87% to 96%.
  • Key result: cut complaints about incomplete orders from 40 to 10 a month.

OKRs and performance reviews

Keep them separate. If the bonus or the performance rating depends directly on hitting the OKR, people set easy targets and the system loses its point. Usually OKRs guide the team’s work, and the performance review looks at each person’s contribution (including what they did for the OKRs), their individual goals and their competencies.

If you are torn between OKRs and SMART goals:

OKRs vs SMART goals: differences and when to use each

For individual goals in the review:

SMART goal generator

Mistakes that get them dropped

  • Too many: 8 objectives with 5 results each. Nobody remembers 40 numbers.
  • Tasks dressed up as key results.
  • Setting them and not looking again until the close.
  • Tying them to bonuses, so everyone sets targets they already know they will hit.
  • Asking every person for individual OKRs.
  • Switching systems every year before the team learns to use one. The first two quarters are usually clumsy; it gets better with practice.

How OKRs fit into the yearly performance cycle:

Performance management: the complete guide