What is OKR: meaning, how to write and examples by area [2026]

OKR stands for Objectives and Key Results. It's the methodology Google, LinkedIn, Spotify and Airbnb use to translate strategy into concrete action. And it works equally well in large companies, startups and small teams.

The idea is old: it was born at Intel in the 1970s with Andy Grove and went global in 1999 when John Doerr brought it to Google. What changed was adoption — it became the standard for anyone who wants to know where they're going and how to prove they got there.

The core principle

Every OKR answers two questions at once:

• Where do we want to go? → Objective
• How will we know we got there? → Key Results

Without this, you have wishes. With this, you have direction with evidence.

OKR does not answer "what are we going to do?". It answers "where do we want to get?" and "how will we know we got there?" — tasks are consequences, not objectives.

The structure: Objective and Key Results

Every OKR has two interdependent components.

• Objective (O) — qualitative, inspiring, no numbers. Answers "what do we want to accomplish this period?". Example: "Turn our customer service into a recognized competitive advantage."
• Key Results (KR) — quantitative, measurable, with a deadline. They answer "how will we know we got there?". Usually 2 to 5 KRs per Objective.

Objective: Turn our customer service into a recognized competitive advantage. KR 1: Raise support NPS from 42 to 72 by the end of the quarter. KR 2: Reduce average first-response time from 18h to 4h. KR 3: Resolve 80% of tickets without escalation.

The real difference between Objective and Key Result

This is the biggest source of confusion for anyone starting with OKRs.

For more practical examples, see Good vs bad Key Results: 10 real examples.

How to write an OKR: the right questions

Before writing, the team should answer six questions:

1. 1What is the most important problem we need to solve this period?
2. 2If we get there, what real difference will it make for the business or the customer?
3. 3How will we know, without a doubt, that we got there?
4. 4Is this objective under our control or do we depend too much on external factors?
5. 5If we reach 70% of this OKR, would it still be worth the effort?
6. 6Does this OKR connect with the broader strategy or does it exist in isolation?

An OKR that fails these questions is a badly written OKR.

OKR vs KPI: what's the difference?

A KPI measures ongoing health — metrics you always monitor (revenue, NPS, churn). An OKR is a quarterly ambition — where you want to go this cycle and how to measure it. The same number (e.g., NPS) can be a KPI when continuously monitored and a Key Result when it becomes an aggressive quarterly target.

To go deeper, read OKR vs KPI: they are complementary, not competing.

Why each area should have its own OKRs

One of the strengths of OKRs is that they cascade: from company to areas, from areas to teams. But each area should have its own OKRs — never just execute the corporate one.

The reason is context. The corporate OKR defines the overall direction. The area OKR defines how that specific area contributes — with the language, metrics and challenges unique to its function.

Same corporate Objective, 4 different breakdowns by area

:::

OKRs by area create distributed accountability — each team clearly sees where its lever is. It also makes growth bottlenecks easier to identify.

To align OKRs across company, areas and people, read OKR cascade: how to align company, teams and people.

How many OKRs to have

Practical rule: 1 to 3 Objectives per quarterly cycle. 2 to 5 Key Results per Objective.

Ten simultaneous OKRs destroy the methodology. If the team can't recall by heart what the quarterly OKRs are, there are too many.

OKR for small companies

OKR works in a 3-person company as well as in a 3,000-person one. The difference is scale, not logic. In a small company, one corporate Objective per quarter is enough, with quick weekly reviews and no expensive tool.

Full guide: OKR in practice: a guide for small teams.

How to track OKRs in practice

Setting OKRs without tracking them is like setting a route in GPS and driving without looking at the screen. The weekly check-in is the ritual that turns OKR into a real direction tool.

Learn how: Weekly check-in: the ritual that makes OKR work.

What to avoid when writing OKRs

OKR is simple to understand, hard to sustain. When it fails, it's usually not because of the method — it's because of old habits that resist change. Vague Objectives, Key Results that become tasks and OKRs imposed without discussion are the most common traps.

See the five traps in detail: When OKR goes wrong: 5 common traps.

Conclusion

OKR is not a control tool — it's a clarity tool. Its strength is forcing teams to answer two questions that seem simple but rarely have an easy answer: where are we going and how will we know we got there?

Writing a good OKR requires honesty about priorities, courage to set targets that challenge the status quo and discipline to measure what matters. When each area builds its own OKRs with autonomy and connection to the broader strategy, the result is an organization that moves different parts in the same direction — without micromanagement.