What are OKRs? The Complete Guide

OKR meaning

OKR stands for Objectives and Key Results.

Instead of asking "what are we doing?", OKRs force a different question: "what are we achieving?"

The OKR framework has two core components:

• Objective: a clear, high-level description of what you want to achieve
• Key Results: measurable outcomes that measure whether you got there

An OKR is one Objective paired with 2-4 Key Results. John Doerr, the venture capitalist who brought OKRs from Intel to a young Google and helped popularize the framework worldwide, captured this relationship in a simple formula in his book Measure What Matters:

This is easiest to understand with a real example. Here, the Objective sets the ambition, and the three Key Results define what success looks like in numbers.

Let's break down each component.

What are Objectives?

An Objective is the qualitative, inspiring part of an OKR. It defines the what: a clear, high-level description of something your team wants to achieve.

Objectives can span different timeframes, a quarter, a half-year, or even longer, though most teams default to quarterly cycles.

Good Objectives are moonshots: they should feel uncomfortable, stretching your team to the edge of what's possible without tipping into fantasy.

The point is to force prioritization. When you only have room for 2-4 Objectives, you can't hide behind a long list of "nice to haves." Every Objective should connect directly to your company's strategy, mission, or vision.

• Qualitative, not quantitative: no numbers in the Objective itself
• Ambitious enough that achieving 70% still represents real progress
• Few in number (2-4 per team) to maintain ruthless focus
• Tied to a clear timeframe and owned by a specific team

What are Key Results?

Key Results are the quantitative metrics that ground your Objective in reality. They break an ambitious aspiration into tangible milestones, so there's never a debate about whether you succeeded or not.

Every Key Result must have a number. Without one, you're back to vague intentions.

Key Results also serve as an accountability mechanism: when an Objective spans several months, it's easy to lose track. Measurable Key Results keep progress visible and make it obvious when things go off course.

• Always include a number: if it can't be measured, it's not a Key Result
• Measure outcomes (what changed), not activities (what you did)
• Include a start value and a target value so progress is unambiguous
• Limit to 2-4 per Objective to maintain focus

An Initiative is a focused effort geared toward achieving one or more Key Results. Initiatives describe the actual work: the projects, experiments, and tasks your team executes. Because they're separate from Key Results, you can swap an initiative that isn't working without changing the goal itself.

When you put all three together, a complete OKR looks like this:

A brief history of the OKR method

OKRs were invented by Andy Grove at Intel in the 1970s, building on Peter Drucker's Management by Objectives from 1954.

In 1954, Peter Drucker introduced Management by Objectives (MBO) in The Practice of Management: instead of managers dictating tasks, they agreed on goals with employees. But MBO had weaknesses: goals were annual, progress was hard to measure, and the process was top-down and bureaucratic.

In the 1970s, Andy Grove at Intel kept Drucker's idea and added Key Results: measurable outcomes that tracked real progress, not just completed tasks. He also shortened the cycle from annual to quarterly, forcing more frequent reassessment.

In 1999, Doerr, by then a venture capitalist, introduced OKRs to a young Google with just 40 employees. Larry Page and Sergey Brin adopted the framework company-wide, and it became a core part of how Google scaled.

Today, OKRs are used by companies like Spotify, LinkedIn, Samsung, and Netflix, from 10-person startups to 100,000-person enterprises.

Why use OKRs?

83% of organizations using OKRs report a positive impact on their business, according to Mooncamp's OKR Impact Report. That number rises when goals are transparent, reviewed regularly, and connected to company strategy.

OKR benefits

OKRs deliver results through five core mechanisms, often referred to as FACTS:

• Focus: Limiting OKRs to 2-4 per team forces hard choices about what actually matters this quarter. Without that constraint, teams spread themselves across a dozen "priorities" and make meaningful progress on none of them. The discipline of saying no is what makes OKRs powerful.
• Alignment: Team OKRs ladder up to company OKRs, so every department pulls in the same direction instead of optimizing in silos. When a marketing team can see how their pipeline goal connects to the company's revenue target, work stops feeling arbitrary. Misalignment — where teams unknowingly work against each other — becomes visible before it causes damage.
• Commitment: When teams help define their own OKRs rather than receiving them top-down, they own the outcome in a way that mandates never achieve. People fight harder for goals they had a hand in shaping. That sense of ownership is what separates OKRs from the annual goal-setting exercises that collect dust in a spreadsheet.
• Tracking: Measurable Key Results make progress undeniable — there's no hiding behind "we're working on it" when the number hasn't moved. Weekly or biweekly check-ins surface problems early enough to course-correct, rather than discovering at the end of the quarter that something went off the rails. A clear score at the end of each cycle closes the loop and feeds into the next one.
• Stretching: OKRs deliberately push teams beyond business-as-usual by setting targets where 70% completion counts as success. This reframes failure: missing an ambitious goal by 30% usually means you still achieved something remarkable. Safe, conservative targets protect egos but rarely produce breakthroughs.

Beyond FACTS, OKRs also improve collaboration (shared OKRs break down silos between departments) and engagement: research from Harvard Business Review shows that aligned employees are more than twice as likely to be top performers.

What are the types of OKRs?

Not all OKRs work the same way. Different types serve different purposes, and knowing the distinction helps teams set goals that fit the situation.

Committed vs aspirational OKRs

The most important distinction in the OKR method is between committed and aspirational OKRs, a framework Google uses internally.

Committed OKRs are must-dos: targets the team commits to hitting 100%, like a product launch, a compliance deadline, or a contractual obligation. Missing a committed OKR is a serious problem.

Aspirational OKRs (also called stretch goals) are ambitious by design: 70% completion counts as success. If you hit 100% of your aspirational OKRs every quarter, your targets aren't ambitious enough.

This quote might be astronomically questionable (the nearest star is much farther than the moon), but the spirit holds. Aiming high and falling short often beats hitting a safe target. That's the whole point of aspirational OKRs: you set a goal that feels slightly out of reach, and the stretch itself drives more progress than a comfortable target ever would.

Most teams use a mix: committed OKRs for business-critical goals, aspirational OKRs for growth bets.

Company, team, and individual OKRs

OKRs can operate at different levels within an organization.

Company OKRs set the strategic direction for the entire organization. They are typically owned by the leadership team and define the 2-4 most important priorities for the quarter.

Team OKRs translate company priorities into department-level goals. Each team's OKRs should support at least one company OKR, creating alignment across the organization.

Individual OKRs connect a person's daily work to team goals. However, most OKR practitioners discourage them, especially when starting out:

• They create micromanagement pressure and blur the line between goal-setting and performance reviews
• They encourage sandbagging — people set easy targets to protect themselves
• They fragment focus: everyone optimizes for their own scorecard instead of pulling toward shared outcomes

If individuals need goals, regular 1-on-1s and task management are usually a better fit.

Annual vs quarterly OKRs

Most teams operate on a quarterly cadence: 90 days is long enough to achieve something meaningful and short enough to stay focused. Some organizations also set annual OKRs at the company level to anchor long-horizon ambitions, using quarterly OKRs as stepping stones toward them.

OKR vs KPI

OKRs drive change. KPIs monitor health. They serve fundamentally different purposes, but most successful organizations use both.

A KPI (Key Performance Indicator) is a metric you watch continuously to make sure the business is running as expected: revenue, churn rate, uptime, customer satisfaction. KPIs are your dashboard. They tell you if something is off, but they don't tell you what to do about it.

An OKR is a temporary, time-bound goal that drives improvement toward a specific outcome. OKRs are your roadmap: they tell you where you're going and how you'll know you arrived. Once you've reached the destination, you move on to the next one.

The two work best together. KPIs flag problems; OKRs fix them. When your churn rate KPI rises from 5% to 8%, that's a signal to create an OKR: Reduce customer churn, as measured by bringing churn rate from 8% to 4%.

The OKR framework vs. other goal-setting frameworks

OKRs aren't the only option. Here are the frameworks you'll run into most often and when they make sense.

• SMART Goals: A template for writing clear goals (Specific, Measurable, Achievable, Relevant, Time-bound). Useful when you need to sharpen a single goal, but it's a formatting guideline, not a system: there's no alignment across teams, no review cadence, no transparency. The "Achievable" criterion also works against the stretch mentality that makes OKRs effective.
• Balanced Scorecard: Tracks performance across four lenses: financial, customer, process, and learning. Great for executive-level strategy oversight, but heavy to maintain. Many companies pair it with OKRs: Scorecard for the big picture, OKRs for quarterly execution.
• MBO (Management by Objectives): The direct predecessor of OKRs, introduced by Peter Drucker in the 1950s. The core idea was right: agree on goals with your people instead of dictating them. But MBOs run annually, lack measurable Key Results, and stay private between manager and employee. OKRs kept the philosophy and fixed all three problems.
• Hoshin Kanri: A Japanese method for cascading long-term strategy through every level of the organization. Strong on alignment, but runs on annual or multi-year cycles with a formal back-and-forth ("catchball") between leadership and teams. Best for large-scale transformation where speed matters less than precision.
• OGSM: Objectives, Goals, Strategies, and Measures on a single page. Popular in CPG and manufacturing. More structured than OKRs, but annual cadence makes it harder to course-correct mid-year.
• EOS (Entrepreneurial Operating System): More than goal-setting: it's a full operating system with quarterly "Rocks," meeting rhythms, and accountability charts. Designed for companies with 10-200 people. Prescriptive by design. Many growing companies start with EOS and layer OKRs on top as they scale.

These frameworks aren't mutually exclusive. Some teams run OKRs for quarterly execution while tracking long-term strategy with a Balanced Scorecard, or use SMART criteria to sharpen individual Key Results within their OKRs.

How to write great OKRs

A great OKR has an inspiring Objective and 2-4 measurable Key Results. The Objective provides direction, the Key Results provide evidence of success. Before diving into the rules, here's the basic sentence structure behind each:

There's also a second variant for Objectives: start with "We have..." and write it in the past tense, as if you've already achieved it. Why this works:

• Forces the team to visualize the end state concretely
• Shifts the conversation from "what should we try?" to "what does the world look like when we've succeeded?"
• Creates a stronger sense of commitment: you're not aspiring toward something vague, you're declaring a future you intend to make real

Writing Objectives

An Objective should make your team say "Yes, that's worth working toward."

Objectives typically fall into one of three types: build something new (a product, capability, or market position), improve something existing (speed, quality, conversion rate), or innovate by rethinking an approach entirely.

Knowing the type helps keep the Objective focused.

A "build" Objective might read: "Launch our first enterprise product." An "improve" Objective might read: "Deliver a faster, more reliable checkout experience."

Here's what to keep in mind when writing Objectives:

• Keep it qualitative: No numbers. The Objective is the inspiration; Key Results handle the metrics.
• Make it inspiring: "Dominate our category" beats "Grow market share."
• Be ambitious: OKRs should push the team beyond business-as-usual. Aim for what feels 70% achievable.
• Time-bound it: Tie it to a cycle. Most teams use quarterly OKRs.
• Give it an owner: Every Objective needs a team (or person) who is responsible for it.

Writing Key Results

Key Results are the evidence that the Objective has been achieved. The most common mistake people make here is writing tasks (outputs) instead of outcomes.

A few principles that separate good Key Results from bad ones:

• Make it measurable: Every Key Result needs a number. "Improve satisfaction" is not a Key Result. "Increase CSAT from 72 to 90" is.
• Focus on outcomes, not output: Measure what changed, not what you did. "Write 10 blog posts" is a task. "Increase organic traffic from 5K to 15K monthly visitors" is an outcome.
• Be specific: Include a starting value and a target value so progress is unambiguous.
• Limit to 2-4 per Objective: More than four Key Results dilutes focus.

Setting Initiatives

While Objectives and Key Results define the "what" and the "how much," Initiatives are the actions that drive Key Results forward.

• Key Result: "Increase organic traffic from 5K to 15K monthly visitors"
• Initiative 1: Publish 2 SEO-optimized articles per week
• Initiative 2: Rebuild the top 10 landing pages for search intent

If an Initiative isn't working, you can swap it for a different one without changing the Key Result.

Good vs bad OKRs

A good OKR has an inspiring Objective and measurable, outcome-focused Key Results.

The bad OKR sounds reasonable, but "Improve our product" could mean anything, "Ship 10 features" rewards output over impact, and "Make users happier" cannot be verified.

The good OKR gives the team an exact definition of success at the end of the quarter: specific numbers to hit, and an Objective worth working toward.

In our experience, most bad OKRs fail for one of these reasons:

1. Too vague: "Improve marketing" gives no direction. Without specificity, teams interpret the Objective differently and pull in different directions.
2. Output-focused: "Write 10 blog posts" tracks activity, not impact. Measure the outcome (traffic, leads, engagement) instead.
3. Not measurable: "Make customers happier" cannot be verified. Replace it with a number: "Increase CSAT from 72 to 90."

OKR examples

The best way to understand OKRs is to see them in action. The following example shows how OKRs cascade from a company-level goal into department-level priorities — each team's OKRs directly support the overarching Objective.

Company-level OKR

The company OKR sets the strategic direction. Every team OKR below should ladder up to it.

Engineering team OKR

The engineering team translates the company mission into a technical challenge: building the software that keeps settlers alive.

Operations team OKR

The operations team focuses on the supply chain, making sure cargo reaches Mars reliably and at a cost that scales.

For more examples across departments and industries: OKR Examples Library

Common OKR mistakes

The most common OKR mistake is setting too many goals, which destroys the focus that makes OKRs valuable.

1. Setting too many OKRs: More than 3-4 OKRs per team means nothing gets real focus. Fewer goals lead to better results.
2. Confusing Key Results with tasks: "Launch redesigned homepage" is a task. "Increase homepage conversion rate from 2% to 5%" is a Key Result. Key Results track what changed, not what you did.
3. No connection to strategy: OKRs that float in isolation don't move the company forward. Every team OKR should trace back to a company-level goal.
4. Setting OKRs top-down only: When leadership dictates every OKR, teams lose ownership. The best approach combines top-down direction (leadership sets company OKRs) with bottom-up input (teams propose their own OKRs to support them).
5. Not reviewing OKRs regularly: Setting OKRs and forgetting them until the end of the quarter defeats the purpose. Weekly or biweekly check-ins keep progress visible and allow course corrections.
6. Tying OKRs to compensation: When bonuses depend on OKR scores, teams set easy targets to protect their pay. Keep OKRs ambitious by separating them from compensation.

How to implement OKRs

Getting OKRs right takes more than writing a good Objective. You need buy-in, a clear process, and the discipline to stick with it for more than one cycle. Here's a realistic path from zero to a running OKR program.

Start with your strategic foundation

Before writing a single OKR, make sure your organization has a clear mission (why you exist), vision (where you're headed), and strategy (how you'll get there). Without that foundation, OKRs have nothing to attach to. If your leadership team can't articulate the company's top 2-3 priorities for the year, adding OKRs on top will just create noise.

Run a pilot first

Don't roll OKRs out to the entire company on day one. Pick 2-3 teams, run one cycle (typically a quarter), and learn from it. The first cycle will feel messy: OKRs will be imperfect, check-ins will be awkward, and people will confuse Key Results with tasks. That's normal. The pilot lets you work through those growing pains without disrupting the whole organization.

An OKR workshop at the start of the pilot helps teams understand the framework and practice writing OKRs together before committing to a real cycle.

Roll out gradually

Once your pilot teams have a cycle under their belt, expand to more teams. Appoint an OKR champion (a single person responsible for training, quality assurance, and keeping the process on track) and make sure every new team gets proper onboarding. Rushing the rollout is one of the most common reasons OKR programs fail.

For a detailed step-by-step plan, see our OKR implementation guide or download the OKR Rollout Guide.

Use OKR software

Spreadsheets work for a pilot, but they break down quickly. Dedicated OKR software gives you a single place to set OKRs, track progress, run check-ins, and see how team goals connect to company priorities. The visibility alone changes how teams work: when everyone can see each other's OKRs, alignment happens naturally.

Run the OKR cycle

Once OKRs are live, they follow a repeating OKR cycle with four key events:

1. OKR Planning: At the start of each quarter, teams draft their OKRs. Leadership sets company-level OKRs first, then teams propose their own to support them. This is where alignment happens.
2. OKR Check-ins: Every week or two, teams update progress on their Key Results. These are short, focused sessions: what moved, what's stuck, and what needs to change. Check-ins are what keep OKRs alive between planning and review.
3. OKR Review: At the end of the quarter, teams score their OKRs and reflect on what they achieved. What worked? What didn't? What did we learn? This is also where you celebrate wins.
4. OKR Retrospective: Separate from the review, the retrospective focuses on the process itself. Were the OKRs well-written? Did check-ins happen? Was the cadence right? The goal is to improve how you do OKRs, not just what you achieved.

Then the cycle starts again. Most organizations need 2-3 cycles before OKRs feel natural. By the third quarter, teams typically find their rhythm and start seeing the compounding benefits of focus and alignment.

Frequently asked questions