Most teams are busy, but busy is not the same as effective. The gap between the two is usually a goal-setting problem: people work hard on things that do not move the needle, or pull in different directions without realising. OKRs are a simple, widely used framework designed to fix exactly that — by making goals ambitious, measurable and shared. This guide explains what OKRs are, how to write good ones, and the traps to avoid. This is general business information, not professional advice.

What OKRs are

OKR stands for Objectives and Key Results — a goal-setting framework that pairs an ambitious goal with the measurable outcomes that prove you reached it. Popularised by technology companies but used across all kinds of organisations, it gives teams a shared, repeatable way to decide what matters and track whether they are getting there.

The framework has just two ingredients:

  • An Objective: a clear, qualitative statement of what you want to achieve.
  • A set of Key Results: a small number of measurable outcomes that show whether you achieved it.

The power lies in the pairing. The objective provides direction and motivation; the key results provide proof and accountability. Together they turn a vague ambition into something you can actually steer towards.

Objectives: the what

An objective is a concise, inspiring description of a goal you want to reach. It should be qualitative and memorable — the kind of thing a team can rally around — and it deliberately avoids numbers.

Good objectives tend to be:

  • Significant — they matter enough to focus real effort on.
  • Clear — anyone reading them understands the intent.
  • Time-bound — usually framed for a quarter or a year.

For example, "Become the easiest tool to get started with in our market" is an objective. It sets a direction without yet saying how success will be measured. That measurement is the job of the key results. An objective should align with the bigger picture too; it is the bridge between day-to-day work and a company's mission statement or longer-term strategy.

Key Results: the how you will know

Key results are the specific, measurable outcomes that demonstrate the objective has been met. If the objective is the destination, key results are the signposts that prove you have arrived.

The golden rule is that they must be measurable — expressed as a number, percentage or clear yes/no — so there is no arguing about whether you hit them. A typical objective has two to four key results; more than that and focus starts to dissolve.

Crucially, good key results measure outcomes, not activity.

"Publish 20 blog posts" is activity — it measures effort. "Increase trial sign-ups by 30%" is an outcome — it measures impact. OKRs care about results, not busywork.

This distinction is what separates OKRs from a simple to-do list. Anyone can be busy; the question is whether that effort changed anything that matters. Tying key results to real impact — sign-ups, retention, revenue, satisfaction — keeps the framework honest.

A worked example

To see it all fit together, here is one objective with its key results.

ElementExample
ObjectiveMake our customers measurably more successful
Key result 1Increase the share of customers who complete onboarding from 50% to 75%
Key result 2Improve our customer satisfaction score from 7.5 to 8.5
Key result 3Reduce average support response time from 24 hours to 6 hours

Notice how the objective is motivating but vague, while each key result is precise and trackable. At the end of the period, you can score each one and know exactly how you did — no debate required.

How OKRs are used in practice

OKRs are not a one-off exercise; they run on a rhythm.

  1. Set them periodically. Most organisations set OKRs quarterly, sometimes with a small number of broader annual ones above them.
  2. Cascade and align. Company OKRs guide team OKRs, which guide individual focus, so everyone is pulling the same way. This alignment is often the biggest benefit, especially as a business grows and you start to scale a small business.
  3. Check in regularly. Teams review progress frequently — often weekly or fortnightly — so problems surface early rather than at the deadline.
  4. Score and reflect. At the end of the cycle, score each key result, discuss what worked, and feed the lessons into the next set.

This regular cadence is what keeps OKRs alive rather than forgotten in a document. The conversations they prompt are as valuable as the scores themselves.

Committed versus stretch OKRs

One point often trips people up: are you supposed to hit 100%?

The answer depends on the type of OKR. Committed OKRs are goals you fully expect to deliver — missing them is a real failure that needs explaining. Stretch OKRs are deliberately ambitious, set beyond what feels comfortable. With stretch goals, many teams treat scoring around 70% as a strong result, because the point is to reach further than safe targets would allow.

The mistake is mixing the two up — celebrating a missed committed goal, or punishing a stretch goal for not hitting full marks. Decide up front which type each OKR is, so everyone judges the outcome fairly.

Common mistakes to avoid

OKRs are simple in theory but easy to get wrong. Watch for these:

  • Too many OKRs. A handful of objectives, each with a few key results, beats a long list nobody can remember.
  • Measuring activity. If a key result counts tasks rather than impact, rewrite it.
  • Set and forget. OKRs ignored until the deadline lose all their value; the regular check-ins are essential.
  • Using them as a performance stick. Tying OKRs too tightly to individual pay or appraisals tempts people to set timid goals. They work best as a focus and alignment tool.

The bottom line

OKRs pair an ambitious Objective — a clear statement of what you want to achieve — with a few measurable Key Results that prove you got there. Set them on a regular cycle, focus on outcomes rather than activity, keep the list short, and review progress often. Used well, OKRs turn scattered effort into shared, visible progress on the things that genuinely matter.