How to Write OKRs: Complete Guide with Real Examples

OKR stands for Objectives and Key Results. It's the methodology Google, LinkedIn, Spotify, and Airbnb use to translate strategy into concrete action. Works the same way in big companies, startups, and small teams.

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

The core principle

Every OKR answers two questions:

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

Without it, you have just a wish. With that, you have direction backed by evidence.

OKR doesn't answer "what are we going to do?". It answers "where do we want to go?" and "how will we know we got there?". Tasks are a consequence, not the goal.

The structure: Objective and Key Results

Every OKR has two interdependent components.

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

Objective: Make our customer service a recognized competitive advantage. KR 1: Raise support NPS from 42 to 72 by end of quarter. KR 2: Cut 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 OKR beginners. And the easiest to fix once you see it.

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 asks six questions:

1. 1What's the most important problem we need to solve this period?
2. 2If we pull this off, what real difference does it make for the business or the customer?
3. 3How will we know, without doubt, that we got there?
4. 4Is this goal under our control, or do we depend too much on external factors?
5. 5If we hit 70% of this OKR, would the effort still be worth it?
6. 6Does this OKR connect to the bigger strategy, or does it stand alone?

An OKR that doesn't pass these questions is a poorly written OKR.

OKR vs KPI: what's the difference?

KPI measures continuous health. Metrics you watch always: revenue, NPS, churn. OKR is quarterly ambition. Where you want to go this cycle and how to measure it.

The same number (NPS, for instance) can be a KPI when watched continuously and a Key Result when you set an aggressive quarterly target for it.

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

Why each team needs its own OKR

One of OKR's strengths is working in cascade. From company to teams, from teams to people. But each team has to have its own OKRs. Never just execute the corporate one.

The reason is context. The corporate OKR defines general direction. The team OKR defines how that specific team contributes. With its own language, metrics, and challenges.

Same corporate Objective, 4 versions across teams

:::

OKR by team creates distributed accountability. Each team sees where its lever is. It also surfaces growth bottlenecks faster.

To align company, team, and personal OKRs, 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 recite the quarter's OKRs from memory, there are too many.

OKR for small companies

OKR works in a 3-person company as well as in a 3,000-person company. The difference is scale, not logic. Small company, one corporate Objective per quarter is enough. Quick weekly reviews. No expensive tool.

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

How to track OKRs in practice

Setting OKRs without tracking them is like setting a route on GPS and driving without looking at the screen. The weekly check-in is the ritual that turns OKRs 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 maintain. When it fails, it's usually not the method. It's old habits resisting change. Vague Objectives, Key Results that turn into tasks, and OKRs imposed without discussion are the most common traps.

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

OKR beyond the company

The methodology was built for companies, but it works in any life area. Health, money, career, hobbies, relationships. What changes is scale, not structure. If you want to learn OKR by applying it to your own life before bringing it to the team, read Personal OKR: Stop Having Intentions, Start Having Results with 3 complete examples in health, money and career.

Wrap up

OKR isn't a control tool. It's a clarity tool.

Its strength is forcing teams to answer two questions that look simple but rarely have easy answers. Where are we going? How will we know we got there?

Writing a good OKR demands honesty about priorities. Courage to set goals that challenge the status quo. Discipline to measure what matters.

When each team builds its own OKRs with autonomy and connection to the bigger strategy, you get an organization moving different parts in the same direction. Without micromanagement.