OKR (Objectives and Key Results): Definition and Meaning

What does OKR stand for?

OKR stands for Objectives and Key Results. It’s a goal-setting framework built on a simple formula: define what you want to achieve (the Objective) and specify how you’ll measure progress (the Key Results).

Andy Grove developed the concept at Intel in the 1970s, drawing on Peter Drucker’s Management by Objectives but adding measurable results to keep things honest.¹ John Doerr, who learned the system as a young salesperson at Intel, later introduced it to Google’s founders in 1999. That adoption story is what put OKRs on the map for the wider business world.

The framework’s core logic fits in one sentence: “I will [Objective] as measured by [Key Results].” A marketing team’s OKR might look like this:

• Objective: Become the top-ranked resource for revenue operations content.
• Key Result 1: Increase organic traffic to the blog by 40%.
• Key Result 2: Publish 12 new RevOps glossary pages.
• Key Result 3: Grow email subscribers from content by 25%.

The Objective is qualitative and directional. The Key Results are quantitative and time-bound, typically scoped to a quarter.

How OKRs work in practice

OKRs operate on a quarterly cycle in most organizations. At the start of each quarter, leadership sets company-level OKRs. Teams then create their own OKRs that align upward to those company priorities.

Why quarterly? Annual goals are too distant to drive urgency. Weekly goals are too narrow to create meaningful change. Quarters hit a middle ground where teams can take on ambitious projects while still being accountable to a near-term deadline.

A few principles that separate OKRs from generic goal-setting:

Transparency. OKRs are visible across the company. Anyone can see what any other team is working toward. This kills the “I didn’t know they were working on that” problem that plagues organizations past about 30 people.

Separation from compensation. Doerr is explicit about this: OKRs should not be tied to bonuses or performance reviews.² If hitting 100% means a bigger bonus, people sandbag their targets. If falling short means a penalty, nobody sets ambitious goals.

Scoring and reflection. At quarter’s end — often during a quarterly business review — teams score each Key Result on a 0.0 to 1.0 scale. A target of 0.7 is considered success for aspirational OKRs. The scoring conversation matters more than the number itself because it forces an honest look at what happened and why.

OKRs vs. KPIs

This is the most common point of confusion for people encountering OKRs for the first time. A KPI is an ongoing health metric. An OKR is a targeted change initiative.

Your KPI dashboard might track MRR, NRR, lead-to-close conversion rate, and customer satisfaction score. These run continuously. You don’t “finish” a KPI.

An OKR has a start date and an end date. “Improve onboarding completion rate from 60% to 85% by end of Q3” is an OKR. Once Q3 ends, you score it and move on.

In practice, KPIs often generate OKRs. You notice a KPI trending in the wrong direction, and you write an OKR to fix it. Does your RPU keep declining? That’s a KPI problem that deserves an OKR-level response.

Common mistakes with OKRs

The framework is simple. The execution is where teams trip up.

Too many OKRs. If every team has 8 Objectives with 5 Key Results each, you’ve got 40 things to track per team. That’s not focus; that’s a to-do list. Three to five Objectives per team, with three Key Results each, is the upper bound.

Writing tasks instead of outcomes. “Launch the new landing page” is a task. “Increase demo requests from organic traffic by 30%” is a Key Result. The task can get done without moving the number. Outcome-based Key Results keep teams focused on impact, not activity.

Setting OKRs from the top down only. If leadership dictates every OKR and teams just execute, you lose the alignment benefit. The best implementations have company OKRs that set direction, with teams proposing their own OKRs that connect upward.³

Abandoning OKRs mid-quarter. Teams set OKRs at the start of Q1, forget about them by week three, and scramble to score them in the last week. OKRs need a weekly check-in rhythm to stay relevant.

Frequently Asked Questions

What does OKR stand for?

OKR stands for Objectives and Key Results. The Objective is a qualitative, ambitious goal that defines what you want to accomplish. Key Results are 3-5 specific, measurable outcomes that tell you whether you're getting there. John Doerr's formula captures it simply: 'I will [Objective] as measured by [Key Results].' The framework was originally developed by Andy Grove at Intel in the 1970s and later brought to Google by Doerr in 1999.

What is the difference between OKRs and KPIs?

A KPI is a standalone metric that tracks ongoing performance (monthly recurring revenue, customer satisfaction score, employee turnover rate). An OKR is a time-bound goal with a clear finish line. KPIs tell you how the business is running right now. OKRs tell you what you're trying to change. In practice, a KPI might signal a problem ('churn rate hit 8%'), and an OKR would define the fix ('reduce churn to 5% by end of Q2, as measured by...'). Many teams use both: KPIs for monitoring, OKRs for driving specific improvements.

How do you score OKRs?

Most teams score Key Results on a 0.0 to 1.0 scale at the end of each quarter. A score of 0.7 is considered a success for aspirational OKRs. If you're consistently hitting 1.0 on every Key Result, your goals aren't ambitious enough. If you're consistently below 0.4, something is off with either the goal or the execution. The scoring isn't meant to judge individuals; it's a calibration tool that helps teams set better goals over time and have honest conversations about what worked and what didn't.