What Is an OKR? Definition, Formula and 10 Real Examples

KEY TAKEAWAY

An OKR has two parts: an inspiring Objective (a qualitative goal) and 3 to 5 Key Results (measurable outcomes that define success). Created by Andy Grove at Intel, popularized by Google. OKRs work because they separate the ambition from the measurement, forcing teams to define exactly what success looks like before the quarter begins.

OKR is one of the most searched terms in business management, and also one of the most misunderstood. Most people know the acronym. Far fewer understand why the framework works, and fewer still implement it correctly.This guide covers the OKR definition, the formula behind it, the difference between OKRs and KPIs, and 10 real examples you can adapt for your team starting this quarter.

OKR Definition

OKR Definition

OKR stands for Objectives and Key Results. An Objective is an inspiring, qualitative statement of what you want to achieve. Key Results are 3 to 5 specific, measurable outcomes that define what success looks like for that Objective. OKRs are typically set quarterly and reviewed weekly.

The framework was created by Andy Grove, former CEO of Intel, who used it to align Intel's engineering teams around shared priorities during the company's growth phase in the 1970s and 80s. John Doerr, who worked at Intel under Grove, later introduced OKRs to Google in 1999. Google has used them ever since, from 40 employees to over 100,000.The reason OKRs spread from Intel to Google to thousands of organizations is not that they are complex. It is that they solve a specific and universal problem: teams work hard without knowing whether they are working on the right things.

The OKR Formula

Every OKR follows the same structure:

The Formula

Objective:[Inspiring qualitative goal] Key Result 1: [Specific measurable outcome] Key Result 2: [Specific measurable outcome] Key Result 3: [Specific measurable outcome]

The Objective answers: where do we want to go? It should be directional, motivating, and memorable. It does not need a number.The Key Results answer: how will we know we got there? They must be measurable. If you cannot score a Key Result on a scale from 0 to 1 based on actual data, it is not a Key Result. It is a task.

The most common OKR mistake

Writing tasks as Key Results. 'Launch the new product page' is a task. 'Increase organic traffic to the product page from 2,000 to 5,000 monthly visits' is a Key Result. Tasks describe activity. Key Results describe outcomes.

OKR vs KPI: What Is the Difference?

The most common point of confusion is the difference between OKRs and KPIs. They are related but serve different purposes.

Think of KPIs as the dials on your car dashboard. They are always visible and tell you the current state of the business. OKRs are the destination on your GPS. They tell you where you are trying to go this quarter and whether you are making progress toward that specific goal.Most organizations need both. KPIs tell you if the business is healthy. OKRs tell you if you are improving in the areas that matter most right now.

10 Real OKR Examples

The following examples are specific enough to use as templates. Adjust the numbers to match your starting point and target.

Company Level

Objective: Become the most trusted HCM platform for mid-market HR teams.

• Key Result 1: Increase G2 rating from 4.1 to 4.6 with a minimum of 50 new reviews
• Key Result 2: Achieve NPS of 45 or above across the customer base
• Key Result 3: Reduce average support ticket resolution time from 48 hours to 12 hours

Sales Team

Objective: Build a predictable and scalable mid-market sales engine.

• Key Result 1: Increase monthly qualified pipeline from $400K to $700K
• Key Result 2: Reduce average sales cycle from 45 days to 30 days
• Key Result 3: Achieve 90 percent quota attainment across the sales team

Product Team

Objective: Deliver a performance module that makes calibration effortless for HR teams.

• Key Result 1: Ship calibration session feature with 9-box visualization by end of Q2
• Key Result 2: Achieve calibration feature adoption rate of 60 percent within 30 days of release
• Key Result 3: Reduce average calibration session setup time from 4 hours to 45 minutes based on user testing

Marketing Team

Objective: Establish TraineryHCM as the go-to resource for mid-market HR leaders.

• Key Result 1: Grow organic search traffic from 500 to 5,000 monthly sessions
• Key Result 2: Publish 15 SEO-optimized blogs with average word count of 2,500 words
• Key Result 3: Generate 50 qualified demo requests from organic content by end of quarter

HR Team

Objective: Build a high-performance review culture that employees trust.

• Key Result 1: Complete performance review cycle with 95 percent submission rate across all teams
• Key Result 2: Achieve employee satisfaction score of 80 percent or above for the review process
• Key Result 3: Reduce time to complete calibration sessions from 3 weeks to 5 days

How Many OKRs Should a Team Have?

John Doerr recommends a maximum of 3 to 5 Objectives per team per quarter, with no more than 5 Key Results per Objective. Most teams that struggle with OKRs have too many, not too few.The purpose of OKRs is focus. If a team has 8 Objectives, they have made no prioritization decision at all. They have simply listed everything they plan to work on, which defeats the alignment benefit the framework is designed to create.A useful test: if your team had to cut its OKR list in half today, what would you keep? The answer is usually your real OKRs. Start there.

OKR Cadence: How Often to Review

OKRs are set quarterly and reviewed at three levels:

1. Weekly check-ins: brief team meeting to update Key Result confidence scores and surface blockers. Takes 15 to 20 minutes. Not a status report, a problem-solving session.
2. Mid-quarter review: at the 6-week mark, assess whether OKRs need to be adjusted. Markets change. Priorities shift. A mid-quarter review prevents teams from executing against the wrong targets for an entire quarter.
3. End-of-quarter scoring: score each Key Result from 0 to 1 based on actual results. Score the Objective based on its Key Result scores. Celebrate wins. Carry unfinished work into the next quarter's planning.

Google and Intel both follow a weekly check-in rhythm. The teams that skip weekly check-ins almost always find their OKRs abandoned by week 6 when other priorities crowd out the work. The check-in is not bureaucracy. It is accountability infrastructure.