Objectives and Key Results (OKR)

A goal-setting framework that pairs qualitative, aspirational Objectives with quantitative, measurable Key Results, scored on a 0.0 to 1.0 scale, and typically set on quarterly cycles to align individual, team, and organizational priorities.

What Are Objectives and Key Results (OKR)?

Key Takeaways

  • ✓An OKR consists of two parts: the Objective (a qualitative statement of what you want to achieve) and 2 to 5 Key Results (quantitative metrics that prove you achieved it). The Objective inspires. The Key Results measure.
  • ✓OKRs were invented by Andy Grove at Intel in 1975, then brought to Google in 1999 by venture capitalist John Doerr. Google's early adoption made OKRs the default goal framework for Silicon Valley and eventually the broader business world.
  • ✓The framework operates on quarterly cycles. Teams set OKRs at the start of each quarter, track progress weekly, and score them at the end of the quarter on a 0.0 to 1.0 scale.
  • ✓Scoring 0.7 on an OKR is considered success. Consistently scoring 1.0 means the objectives aren't ambitious enough. This "stretch" philosophy is what distinguishes OKRs from traditional goal-setting methods.
  • ✓OKRs are designed to be transparent. Everyone in the organization, from the CEO to individual contributors, publishes their OKRs so that alignment, dependencies, and priorities are visible across teams.

The OKR framework answers two questions. First: Where do we want to go? That's the Objective. Second: How will we know we're getting there? Those are the Key Results. An Objective is qualitative, inspiring, and time-bound. "Become the most trusted brand in our category" is an Objective. "Increase revenue by 20%" isn't. That's a Key Result. Key Results are binary or numeric. They're measurable, specific, and verifiable. At the end of the quarter, you can look at each Key Result and say definitively whether it was achieved, partially achieved, or missed. There's no ambiguity. This two-part structure forces clarity. Teams can't hide behind vague goals like "improve customer satisfaction." They have to define what satisfaction means, how it's measured, and what number constitutes success. That specificity is what makes OKRs work when implemented correctly, and it's also what makes them hard to write well.

0.7Target average score for stretch OKRs. Consistently scoring 1.0 means objectives aren't ambitious enough (Google re:Work)
3-5Recommended number of Objectives per team per quarter, each with 2-5 Key Results (Measure What Matters, John Doerr)
1975Year Andy Grove introduced OKRs at Intel, later popularized by John Doerr at Google in 1999
83%Of companies using OKRs report a positive impact on organizational alignment and performance (Perdoo, 2024)

How to Write OKRs: The Methodology

Writing effective OKRs is a skill that takes practice. Most teams struggle in the first 2 to 3 quarters before finding their rhythm.

Writing Objectives

Good Objectives are qualitative, aspirational, action-oriented, and achievable within the time frame (usually one quarter). They should feel slightly uncomfortable. If the team is certain they can achieve it, the Objective isn't ambitious enough. Format: Start with an action verb. "Launch," "Build," "Establish," "Transform," "Deliver." Example: "Establish our onboarding program as the industry benchmark for time-to-productivity." Bad example: "Improve onboarding." That's too vague. Worse example: "Increase onboarding completion rate to 95%." That's a Key Result disguised as an Objective. Keep Objectives to one sentence. If you need a paragraph to describe it, it's either too complex or too vague.

Writing Key Results

Each Objective gets 2 to 5 Key Results. Each Key Result must be measurable, specific, and have a clear numeric target. Format: Verb + metric + from X to Y (or "to Z" if the baseline is known). Example: "Reduce average time-to-productivity from 90 days to 45 days." Example: "Achieve a new hire satisfaction score of 4.5/5.0 or higher on the 30-day survey." Example: "Complete onboarding certification for 100% of new managers before they receive their first direct report." Bad example: "Improve onboarding satisfaction." No number. Bad example: "Send weekly onboarding emails." That's a task, not a result. The key test: Can someone else verify this Key Result was achieved by looking at the data? If yes, it's a good Key Result.

Common OKR writing mistakes

Confusing Key Results with tasks. "Launch new career page" is a task. "Increase career page application conversion rate from 3% to 8%" is a Key Result. The task describes what you'll do. The Key Result describes what changes because of what you did. Setting too many OKRs. Three Objectives per team per quarter is the sweet spot. Five is the maximum. Beyond that, nothing gets prioritized. Writing OKRs in isolation. OKRs should cascade from company-level priorities. A team's OKRs should clearly connect to at least one organizational Objective. If they don't, the team might be working on the wrong things.

The OKR Grading System (0.0 to 1.0)

OKR scoring uses a simple 0.0 to 1.0 scale. The grading happens at the end of each quarter during the OKR retrospective.

Committed vs stretch OKRs

Google distinguishes between two types: Committed OKRs are objectives the team agrees to achieve completely. Scoring below 1.0 on a committed OKR requires a post-mortem to understand what went wrong. Stretch (aspirational) OKRs are intentionally set beyond what the team believes is achievable. The expected score is 0.7. Scoring 1.0 means the target was too easy. Teams should know which type each OKR is before the quarter starts. Treating all OKRs as stretch goals when some are actually commitments (and vice versa) creates confusion and misaligned expectations.

Score RangeInterpretationWhat It Signals
0.0 - 0.3Failed to make meaningful progressThe Key Result was too ambitious, the team was under-resourced, or priorities shifted mid-quarter
0.4 - 0.6Made progress but didn't reach the targetAcceptable for stretch goals. The team learned something and can carry momentum into next quarter
0.7 - 0.8Target zone for stretch OKRsThe team pushed hard and nearly achieved an ambitious goal. This is the ideal landing zone
0.9 - 1.0Fully achieved or exceededGreat for committed OKRs. For stretch OKRs, consistently scoring here means objectives aren't ambitious enough

The Quarterly OKR Cycle

OKRs follow a repeating quarterly cadence. Each phase has a specific purpose and timeline.

Planning (2 weeks before quarter start)

Company leadership sets 3 to 5 organizational OKRs based on annual strategy. These are shared with all teams. Department and team leaders draft their own OKRs that align with and contribute to organizational OKRs. Cross-functional dependencies are identified and negotiated ("Our Key Result depends on your team's API launch"). Individual contributors may set personal OKRs that align with team priorities. Final OKRs are published publicly (company wiki, OKR tool, or shared document).

Tracking (throughout the quarter)

Weekly check-ins: Each team reviews Key Result progress in a 15-minute standup. Green (on track), yellow (at risk), red (off track). Mid-quarter review: Halfway through the quarter, teams assess whether OKRs are still relevant and achievable. If a major priority shift occurs (acquisition, market change, leadership transition), OKRs can be revised. This is rare but allowed. Transparency is maintained throughout. Anyone in the organization can view any team's OKR progress at any time.

Scoring and retrospective (last week of quarter)

Each Key Result gets a score from 0.0 to 1.0. The Objective's overall score is the average of its Key Results. Teams hold a retrospective to discuss what worked, what didn't, and what they'll change in the next cycle. Scores are recorded and made visible but are NOT used for performance reviews or compensation. This is crucial. The moment OKR scores affect pay, teams sandbar their targets to guarantee high scores, and the stretch philosophy collapses.

OKR vs KPI: Understanding the Difference

OKRs and KPIs are both measurement frameworks, but they serve different purposes and should be used together, not as substitutes for each other.

DimensionOKRKPI
PurposeDrive change and improvement toward specific goalsMonitor ongoing business health and performance
TimeframeQuarterly (reset each cycle)Ongoing (tracked continuously, thresholds may change annually)
Ambition levelStretch targets (0.7 = success)Realistic targets (100% = expectation)
ScopeSelective: 3-5 priorities per quarterBroad: can track dozens simultaneously
Tied to compensation?No (explicitly decoupled)Often (bonus targets, commission thresholds)
ExampleObjective: Build a world-class engineering culture. KR: Reduce voluntary attrition from 18% to 10%KPI: Monthly voluntary attrition rate (threshold: < 15%)

Cascading and Aligning OKRs Across the Organization

OKR alignment ensures every team is pulling in the same direction. But alignment doesn't mean top-down dictation. It means transparent negotiation.

Top-down alignment

Company OKRs set the direction. The CEO and leadership team publish 3 to 5 organizational Objectives for the quarter. Teams then create their own OKRs that contribute to at least one organizational Objective. Example: Company Objective: "Win in the mid-market segment." Sales team Key Result: "Close 50 mid-market deals above $50K ACV." Marketing team Key Result: "Generate 200 mid-market qualified leads." Product team Key Result: "Launch 3 mid-market feature requests by end of quarter." Each team contributes differently, but all connect to the same strategic priority.

Bottom-up input

Good OKR implementations aren't purely top-down. Teams and individual contributors propose OKRs based on what they see in the work: technical debt that needs addressing, customer feedback patterns, process bottlenecks, or innovation opportunities. Google estimates that roughly 60% of OKRs are set bottom-up or laterally, not cascaded from above. This balance keeps the framework responsive to ground-level reality while maintaining strategic alignment.

Why OKR Implementations Fail

Research from Perdoo (2024) shows that 65% of companies abandon OKRs within the first year. These are the most common reasons.

  • Tying OKRs to compensation. The moment OKR scores affect bonuses, teams set conservative targets they're guaranteed to hit. The stretch philosophy dies, and OKRs become just another KPI dashboard. Google, Intel, and every major OKR advocate explicitly separates OKR scoring from performance reviews.
  • Setting too many OKRs. If a team has 8 Objectives with 4 Key Results each, they're tracking 32 metrics. Nothing gets prioritized. Nothing gets focus. Three Objectives is the ideal. Five is the absolute maximum.
  • Writing tasks instead of outcomes. "Ship feature X by March 15" is a task. "Increase user activation rate from 25% to 45%" is an outcome. OKRs should describe what changes in the world because of the team's work, not what the team will do.
  • No weekly tracking rhythm. OKRs set in January and reviewed in March are goals, not OKRs. The framework requires weekly check-ins (even 10-minute standups) where teams assess Key Result progress using green/yellow/red status.
  • Leadership doesn't model the practice. If the CEO and executive team don't publish their own OKRs and score them publicly, nobody else will take the process seriously. OKRs require top-down participation, not just top-down mandates.
  • Treating OKRs as a project management tool. OKRs define what success looks like. Project plans define how you'll get there. Conflating the two turns OKRs into a glorified task list.

OKR Software and Tools

Dedicated OKR platforms simplify tracking, alignment visualization, and scoring. Spreadsheets work for small teams, but they don't scale.

PlatformBest ForKey FeaturesPrice Range
LatticeMid-market companies with existing performance managementOKR + performance review integration, goal trees, 1-on-1 tracking$6-$11/person/month
15FiveTeams focused on manager effectivenessOKR tracking, weekly check-ins, engagement surveys$4-$16/person/month
PerdooOKR-first organizationsStrategy maps, OKR coaching, alignment trees, reporting$Free-$10/person/month
WeekdoneSmall teams new to OKRsOKR templates, weekly planning, team dashboards$Free-$108/team/month
Gtmhub (Quantive)Enterprise OKR programsAI-assisted KR tracking, integrations with 150+ data sourcesCustom pricing
Google Sheets/NotionStartups and small teamsFull flexibility, no cost, but no automation or alignment featuresFree

Frequently Asked Questions

Should OKRs be set annually or quarterly?

Company-level OKRs are often set annually to provide strategic direction, then broken into quarterly OKRs for execution. Team and individual OKRs are always quarterly. The quarterly cycle is non-negotiable because it creates urgency, forces prioritization, and allows course correction. Annual OKRs tend to lose relevance by Q2 as market conditions, priorities, and team capacity change.

Can individual contributors have their own OKRs?

Yes, but it's optional and depends on the organization's maturity. Google and other OKR pioneers encourage individual OKRs because they create ownership and clarity. However, many companies find that team-level OKRs are sufficient, especially if the team is small (under 8 people) or if individual OKRs would just mirror team priorities. Start with company and team OKRs. Add individual OKRs once the organization is comfortable with the framework.

What's the difference between this and the existing 'OKRs' glossary term?

The OKRs term provides a practical overview of how OKRs work in HR contexts. This term, Objectives and Key Results (OKR), focuses on the formal framework definition: the methodology invented by Andy Grove, the grading system (0.0 to 1.0 scale), committed vs stretch OKRs, the quarterly cycle mechanics, and the implementation playbook. Think of the OKRs entry as "OKRs for HR teams" and this entry as "the OKR framework itself."

How do OKRs work in HR departments specifically?

HR teams use OKRs to set quarterly priorities around talent acquisition, retention, engagement, L&D, and compliance. Example HR OKR: Objective: "Build a hiring engine that attracts top engineering talent." KR1: Reduce time-to-hire from 45 to 25 days. KR2: Increase offer acceptance rate from 72% to 88%. KR3: Achieve a candidate NPS of 60+ across all engineering roles. The Key Results are specific, measurable, and connect to the strategic Objective. They don't describe HR tasks ("post 50 job listings"). They describe outcomes.

Why shouldn't OKR scores be used in performance reviews?

Because it kills the stretch philosophy. If a manager knows their bonus depends on OKR scores, they'll set easy targets they can guarantee hitting at 1.0. The result: sandbagged goals, no innovation, no ambition. OKRs should inform performance conversations ("Here's what I prioritized and what I achieved") but the score itself shouldn't map to a rating or a payout. Companies like Google, LinkedIn, and Twitter use OKRs for alignment and focus, then evaluate performance through separate processes that consider OKR effort alongside business impact, leadership behaviors, and peer feedback.

What should we do if priorities change mid-quarter?

If a major strategic shift occurs (acquisition, market disruption, leadership change), it's acceptable to revise or replace OKRs mid-quarter. But this should be rare, maybe once or twice a year. If you're revising OKRs every quarter, the problem isn't the framework. It's the planning process. When mid-quarter changes happen, document why the change was made, score the original OKRs as-is (with context notes), and set revised OKRs for the remainder of the quarter. Transparency about why priorities shifted is more important than maintaining the original targets.
Adithyan RKWritten by Adithyan RK
Surya N
Fact-checked by Surya N
Published on: 25 Mar 2026Last updated:
Share:
Previous
Next