OKR — Objectives and Key Results — is a collaborative goal-setting framework used by organisations, teams, and individuals to define ambitious goals and track measurable outcomes. Developed at Intel by Andy Grove in the 1970s and later popularised by venture capitalist John Doerr, who introduced the framework to Google in 1999, OKRs have since become one of the dominant performance management methodologies in the technology industry and beyond. The framework is built on a deceptively simple premise: pair a qualitative, inspirational objective with a set of quantitative, measurable key results that define what success looks like when the objective is achieved.
An Objective answers the question: Where do we want to go? It is directional, motivating, and time-bound — typically set for a quarter or a full year. A Key Result answers the question: How will we know we have arrived? It is specific, measurable, and verifiable — either achieved or not at the end of the period. Together, the Objective and its Key Results form a complete goal unit that links aspiration to accountability. OKRs are not task lists, project plans, or performance reviews — they are a mechanism for aligning effort across an organisation toward a shared set of priorities.
OKRs operate at multiple levels simultaneously: company-wide OKRs set the strategic direction, department or team OKRs translate that direction into functional priorities, and individual OKRs connect personal work to team and company goals. This cascading and aligning structure — sometimes called “nesting” or “alignment” — ensures that everyone in an organisation understands how their daily work contributes to the larger mission. Unlike traditional top-down goal-setting, OKRs are designed to be bidirectional: senior leadership sets company-level objectives, while teams and individuals have latitude to define their own key results in response.
OKR Structure and Formula
OKR Unit Structure:
OBJECTIVE: [Qualitative, inspirational, time-bound goal]
Key Result 1: [Measurable outcome — metric, target, deadline]
Key Result 2: [Measurable outcome — metric, target, deadline]
Key Result 3: [Measurable outcome — metric, target, deadline]
Standard Format:
"We will [OBJECTIVE] as measured by [KEY RESULTS]."
Example:
Objective: Become the market leader in customer satisfaction in Q3
Key Result 1: Increase Net Promoter Score (NPS) from 42 to 65
Key Result 2: Reduce average customer support response time from 8 hours to 2 hours
Key Result 3: Achieve a customer satisfaction rating of ≥4.7/5.0 across all product lines
OKR Scoring (typical 0.0–1.0 scale):
0.0 = No progress
0.3 = Made some progress but fell significantly short
0.7 = Strong progress; target mostly achieved (often considered "good")
1.0 = Fully achieved
Note: Consistently scoring 1.0 may indicate targets were set too conservatively
Objectives: Definition and Characteristics
The Objective is the qualitative, aspirational component of an OKR. It describes a meaningful destination — a state the organisation wants to reach — in language that is clear, motivating, and memorable. A well-written objective does not contain numbers, percentages, or specific metrics; those belong in the Key Results. Instead, it communicates a direction and an ambition that resonates with everyone who reads it, from the CEO to a frontline employee. Objectives should be challenging enough to require real effort but credible enough that the team believes they are achievable within the timeframe.
| Characteristic | Description | Example of Violation |
|---|---|---|
|
Qualitative
|
Describes a direction or state, not a number
|
“Increase revenue by 20%” (this is a Key Result, not an Objective)
|
|
Inspirational
|
Motivates action; energises the team
|
“Maintain current performance levels” (too passive)
|
|
Time-bound
|
Tied to a specific quarter or annual period
|
Open-ended objectives with no clear horizon
|
|
Actionable
|
Within the team’s sphere of influence
|
“Achieve industry-wide regulatory reform” (outside team control)
|
|
Concise
|
One sentence, easily remembered
|
Multi-paragraph objective statements
|
Key Results: Definition and Characteristics
Key Results are the measurable, verifiable outcomes that define what achieving the objective looks like in concrete terms. Each Key Result must be quantifiable — there should be no ambiguity at the end of the period about whether it was achieved. Key Results are outcomes, not activities or tasks. Writing “launch the new product feature” is a task; writing “achieve 10,000 active users of the new product feature within 30 days of launch” is a Key Result. This distinction is critical: tasks describe inputs and actions, while Key Results describe the change in the world that those actions are intended to produce.
The standard recommendation is three to five Key Results per Objective. Fewer than three may not fully define success; more than five risks diluting focus and creating measurement overhead. Each Key Result should be independently meaningful — the achievement of any single Key Result should represent a genuine, standalone contribution to the Objective, not simply a sub-step in a linear process.
| Characteristic | Description | Poor Example | Strong Example |
|---|---|---|---|
|
Measurable
|
Contains a specific metric and target value
|
“Improve customer satisfaction”
|
“Increase CSAT score from 72% to 88%”
|
|
Outcome-oriented
|
Describes a result, not an activity
|
“Conduct 20 customer interviews”
|
“Identify and validate 3 new customer pain points through user research”
|
|
Time-bound
|
Achievable within the OKR period
|
“Eventually reach 100K users”
|
“Reach 100K monthly active users by end of Q4”
|
|
Verifiable
|
Pass/fail determinable at period end
|
“Significantly reduce churn”
|
“Reduce monthly churn rate from 3.2% to 1.8%”
|
|
Challenging
|
Requires meaningful stretch to achieve
|
“Maintain revenue at current levels”
|
“Grow net new ARR by 40% versus prior quarter”
|
OKR Levels and Alignment
OKRs function as a nested alignment system. Company-level OKRs establish the highest-priority strategic goals for the organisation as a whole. Department and team OKRs translate those priorities into functional actions and commitments. Individual OKRs connect personal performance to team and company direction. This multi-level structure ensures vertical alignment — everyone is working toward the same strategic north star — while preserving horizontal coordination between teams whose work intersects or depends on each other.
| OKR Level | Set By | Time Horizon | Number of OKRs | Primary Purpose |
|---|---|---|---|---|
|
Company / Corporate
|
CEO and executive team
|
Annual + Quarterly
|
3–5 objectives
|
Strategic direction and organisational priorities
|
|
Department / Function
|
Department heads
|
Quarterly
|
3–5 objectives
|
Functional contribution to company OKRs
|
|
Team / Squad
|
Team leads
|
Quarterly
|
2–4 objectives
|
Operational execution and cross-team coordination
|
|
Individual
|
Employee (with manager input)
|
Quarterly
|
2–3 objectives
|
Personal contribution and professional development
|
OKR vs. KPI: Key Differences
OKRs and KPIs are complementary but fundamentally different tools. KPIs (Key Performance Indicators) measure the ongoing health and performance of existing processes — they are the vital signs of a business. OKRs are goal-setting frameworks for driving change — they define where the organisation wants to move and how it will measure progress toward a new state. A company might have a KPI of “Monthly Churn Rate” that it monitors continuously as a health metric. The corresponding OKR might be: Objective — “Dramatically improve customer retention,” with a Key Result of “Reduce monthly churn from 3.5% to 1.5% by end of Q3.” The KPI tells you where you are; the OKR tells you where you are trying to go and by when.
| Dimension | OKR | KPI |
|---|---|---|
|
Purpose
|
Drive change toward a new desired state
|
Monitor ongoing process health and performance
|
|
Time horizon
|
Quarterly or annual; reset each cycle
|
Continuous; tracked indefinitely
|
|
Nature
|
Aspirational and directional
|
Descriptive and diagnostic
|
|
Scope
|
Specific priority areas for a period
|
Broad coverage of all key business functions
|
|
Ownership
|
Team or individual with accountable owner
|
Functional area; often shared ownership
|
|
Success definition
|
Scored 0.0–1.0 at period end
|
Compared to target or historical benchmark
|
|
Relationship
|
OKR Key Results often use KPI metrics as targets
|
KPIs provide the data that populates Key Results
|
OKR Cycle and Cadence
OKRs operate on a defined rhythm that combines quarterly execution cycles with annual strategic planning. The quarterly cadence creates urgency — a 90-day window is long enough to make meaningful progress on ambitious goals but short enough to maintain momentum and course-correct quickly. Annual OKRs set the longer-horizon vision within which quarterly OKRs operate. Many organisations layer weekly check-ins (sometimes called “confidence ratings” or “weekly updates”) on top of the quarterly cycle to maintain visibility and catch at-risk Key Results early.
| Cycle Phase | Timing | Activity | Output |
|---|---|---|---|
|
Planning
|
Weeks 1–2 of quarter
|
Draft objectives, align Key Results, cascade across levels
|
Finalised OKR set for the quarter
|
|
Execution
|
Weeks 3–10
|
Weekly check-ins, confidence scoring, initiative tracking
|
Progress updates, early warning flags
|
|
Mid-cycle Review
|
Week 6–7
|
Formal mid-quarter review; adjust Key Results if needed
|
Updated confidence scores, revised targets if warranted
|
|
Grading
|
Final week of quarter
|
Score each Key Result 0.0–1.0; assess overall objective progress
|
Final OKR scores and retrospective notes
|
|
Retrospective
|
Week 1 of next quarter
|
Review what worked, what didn’t, lessons for next cycle
|
Inputs to next quarter’s OKR planning session
|
Committed vs. Aspirational OKRs
Google, one of the most influential practitioners of OKRs, introduced an important distinction between two types of OKRs: committed OKRs and aspirational (or “stretch”) OKRs. Committed OKRs are goals the organisation has determined it will achieve — resources will be allocated, plans will be adjusted, and the expectation is a score of 1.0. Aspirational OKRs are “moonshot” goals that represent the upper bound of ambition — they are set knowing that full achievement is unlikely, with a score of 0.7 considered excellent. This distinction allows organisations to maintain accountability for operational commitments while preserving space for ambitious, transformational goals that push the organisation beyond its current capabilities.
| OKR Type | Also Known As | Expected Score | Resource Commitment | Purpose |
|---|---|---|---|---|
|
Committed OKR
|
Operational OKR, “Roofshot”
|
1.0 (full achievement expected)
|
Fully resourced and planned
|
Core operational delivery and business-critical outcomes
|
|
Aspirational OKR
|
Stretch OKR, “Moonshot”
|
0.6–0.7 (excellent outcome)
|
Resources allocated but outcome uncertain
|
Innovation, transformation, breakthrough growth
|
OKR Scoring
OKR scoring converts qualitative progress into a numerical assessment at the end of each cycle. The most widely used scale runs from 0.0 to 1.0, where each Key Result is scored individually and the scores are averaged to produce an overall Objective score. A critical cultural principle of OKR scoring — particularly for aspirational OKRs — is that a score of 0.7 is considered strong performance, not failure. If a team consistently scores 1.0 on all Key Results, it is generally a sign that targets were set too conservatively. The scoring system is designed to encourage ambitious goal-setting by normalising the expectation that full achievement of stretch goals is rare.
OKR Scoring Scale:
0.0 = No meaningful progress made
0.1–0.3 = Early progress; fell significantly short of target
0.4–0.6 = Meaningful progress; roughly half of target achieved
0.7 = Strong result; widely considered the "good outcome" for stretch OKRs
0.8–0.9 = Near-full achievement; minor shortfall only
1.0 = Fully achieved (expected for committed OKRs; exceptional for aspirational)
Objective Score = Average of all Key Result scores
Example:
Key Result 1 score: 0.8
Key Result 2 score: 0.6
Key Result 3 score: 0.9
Objective Score = (0.8 + 0.6 + 0.9) / 3 = 0.77 → Strong quarter
OKR Examples Across Functions
| Function | Objective | Key Result Examples |
|---|---|---|
|
Sales
|
Dominate the mid-market segment in Q3
|
Close $2.5M in net new ARR from mid-market accounts; achieve pipeline coverage ratio of 4× for the segment; reduce average sales cycle from 45 to 30 days
|
|
Product
|
Ship a product experience customers love
|
Achieve feature adoption rate of 60% for new module within 60 days of launch; reduce time-to-value from 14 days to 5 days; score 4.5/5.0 or higher in post-release user surveys
|
|
Marketing
|
Build brand authority in the enterprise space
|
Generate 500 qualified enterprise leads; achieve 25,000 unique monthly visitors to the enterprise solution page; place 3 executives in Tier 1 industry publication features
|
|
Engineering
|
Deliver a platform customers can rely on
|
Achieve 99.95% system uptime; reduce median bug resolution time from 72 hours to 24 hours; complete security certification audit with zero critical findings
|
|
HR / People
|
Build a world-class team
|
Reduce time-to-hire from 45 to 28 days; achieve employee engagement score of ≥80%; reduce voluntary turnover from 18% to 12%
|
|
Customer Success
|
Make every customer a champion
|
Achieve NRR of 120%; increase NPS from 38 to 55; complete business reviews for 100% of enterprise accounts each quarter
|
Common OKR Mistakes
Despite the simplicity of the OKR structure, organisations frequently make a consistent set of errors that undermine the framework’s effectiveness. The most common mistake is writing Key Results that are actually tasks or activities rather than measurable outcomes — confusing outputs with results. A second frequent error is setting too many OKRs, which dilutes focus and defeats the framework’s purpose as a prioritisation tool. A third systemic failure is linking OKR scores directly to compensation or performance ratings — this incentivises sandbagging (setting easy targets) and destroys the cultural safety required for ambitious goal-setting. OKRs are a management tool for alignment and focus, not a performance review mechanism.
| Mistake | Description | Consequence |
|---|---|---|
|
Task-based Key Results
|
Writing activities (“launch X”) instead of outcomes (“achieve Y result from X”)
|
Completion of tasks doesn’t guarantee meaningful progress toward the objective
|
|
Too many OKRs
|
Setting 10+ objectives or 20+ Key Results per quarter
|
Prioritisation fails; everything becomes equally important and nothing gets focus
|
|
Linking to compensation
|
Tying OKR scores directly to bonuses or performance ratings
|
Teams set sandbagged targets; aspirational goal-setting dies; scores inflate
|
|
No alignment check
|
Team OKRs set without reference to company-level OKRs
|
Teams optimise locally while the organisation pulls in different directions
|
|
Set and forget
|
OKRs written at quarter start and not reviewed until quarter end
|
No early warning on at-risk Key Results; no ability to course-correct
|
|
Copying last quarter’s OKRs
|
Rolling over identical objectives and key results without refreshing
|
Loss of dynamism; OKRs become routine reporting rather than ambitious goal-setting
|
OKR vs. MBO (Management by Objectives)
OKRs evolved from Management by Objectives (MBO), a framework introduced by Peter Drucker in his 1954 book The Practice of Management. Andy Grove refined Drucker’s MBO approach at Intel by adding two critical elements: the insistence on measurable Key Results (not just objectives) and the public, transparent sharing of OKRs across the organisation. While MBO is typically an annual, top-down process linked directly to compensation, OKRs are quarterly, bidirectional, transparent, and deliberately separated from pay and performance ratings. These structural differences produce fundamentally different cultural outcomes: MBO tends toward conservatism and compliance, while OKRs encourage ambition and learning.
| Dimension | OKR | MBO |
|---|---|---|
|
Origin
|
Andy Grove / Intel (1970s); Google (1999)
|
Peter Drucker (1954)
|
|
Cadence
|
Quarterly + Annual
|
Typically Annual
|
|
Direction
|
Bidirectional (top-down + bottom-up)
|
Top-down
|
|
Transparency
|
Public across the organisation
|
Usually private or manager-only
|
|
Link to compensation
|
Deliberately separated
|
Typically linked to bonuses and ratings
|
|
Target-setting culture
|
Encourages stretch and ambition
|
Encourages achievable, safe targets
|
OKR and the SMART Framework
OKR Key Results share significant overlap with the SMART goal framework — Specific, Measurable, Achievable, Relevant, and Time-bound. A well-written Key Result will satisfy all five SMART criteria: it names a specific metric, contains a measurable target value, is achievable within the quarter with meaningful effort, is relevant to the stated Objective, and has a defined time horizon. The primary difference is in the Achievable dimension: SMART goals are traditionally set to be comfortably achievable, while OKR Key Results — particularly aspirational ones — are intentionally set at the boundary of or slightly beyond comfortable achievability to drive breakthrough performance.
OKR Software and Tools
A growing ecosystem of dedicated OKR software platforms has emerged to support OKR planning, tracking, alignment visualisation, and reporting. These tools range from purpose-built OKR platforms to broader performance management suites that include OKR functionality. Many organisations begin their OKR journey using spreadsheets or project management tools before migrating to dedicated platforms as complexity grows.
| Tool | Type | Best For |
|---|---|---|
|
Lattice
|
Performance management + OKR
|
Mid-size to large organisations with combined HR and OKR needs
|
|
Workboard
|
Enterprise OKR platform
|
Large enterprises with complex alignment requirements
|
|
Betterworks
|
Continuous performance + OKR
|
Enterprise organisations running quarterly OKR cycles
|
|
Perdoo
|
Dedicated OKR tool
|
Growth-stage companies seeking a focused OKR platform
|
|
Weekdone
|
OKR + weekly check-ins
|
Small to mid-size teams prioritising weekly progress visibility
|
|
Google Sheets / Notion
|
General productivity tools
|
Early-stage companies or teams new to OKRs
|
Investor and ESG Context
Investors in growth-stage and public technology companies increasingly view OKR adoption as a proxy indicator of organisational maturity, strategic clarity, and execution discipline. A management team that can articulate company-level OKRs clearly — and demonstrate quarter-over-quarter progress against them — signals to investors that leadership has both a coherent strategic vision and the operational systems to pursue it. In due diligence processes, private equity and venture capital investors routinely ask founders and management teams to share their OKR frameworks as part of assessing execution capability.
From an ESG perspective, OKRs are increasingly being used to operationalise environmental and social commitments. Rather than publishing aspirational sustainability reports with no accountability mechanism, leading organisations are embedding ESG objectives directly into their OKR frameworks — with measurable Key Results tied to carbon reduction targets, diversity and inclusion hiring metrics, community investment commitments, and supply chain sustainability standards. This integration transforms ESG pledges from marketing communications into operational priorities with the same visibility and accountability as revenue and product goals.
Limitations of OKRs
OKRs are a powerful framework, but they are not without limitations. The framework works best in environments with relatively fast feedback loops and clear outcome metrics — conditions that are common in technology product and commercial functions but less present in research, creative, regulatory, or long-cycle operational contexts. In roles where outcomes are inherently long-term, ambiguous, or dependent on factors largely outside the team’s control, the quarterly OKR cadence can feel artificial and create pressure to define proxy metrics that do not genuinely represent the desired outcome.
OKRs also carry the risk of creating perverse incentives if Key Results are poorly designed. A sales team with a Key Result tied to “number of contracts signed” may optimise for quantity at the expense of quality, signing small or poor-fit customers to hit their number. An engineering team with a Key Result tied to “bugs closed” may close tickets prematurely or deprioritise prevention in favour of reactive fixes. These “metric gaming” behaviours are a direct result of Key Results measuring the wrong things, and they highlight the critical importance of outcome-oriented Key Result design.
Related Terms
- KPI (Key Performance Indicator) — Ongoing performance metric used to monitor business health; OKR Key Results frequently use KPIs as their measurement vehicle
- SMART Framework — Goal-setting criteria (Specific, Measurable, Achievable, Relevant, Time-bound) that OKR Key Results should satisfy
- MBO (Management by Objectives) — The predecessor framework to OKRs, introduced by Peter Drucker; OKRs are a refined, more transparent version of MBO
- Strategic Objective — A high-level organisational goal that OKRs at the company level are designed to operationalise and measure
- Leading Indicator — A forward-looking metric that predicts future outcomes; strong OKR Key Results are often leading indicators of business performance
- Lagging Indicator — A retrospective metric that confirms past outcomes; many company-level KPIs function as lagging indicators that OKRs are designed to improve
- North Star Metric — A single primary metric representing the core value delivered to customers; often the inspiration for a company’s top-level annual Objective
- Initiative / Project — The specific activities and projects that teams execute to drive progress toward OKR Key Results; initiatives are inputs, Key Results are outcomes
- Cascade / Alignment — The process of connecting company OKRs to department, team, and individual OKRs to ensure organisational coherence
- Rule of 40 — A SaaS health benchmark that OKRs may target; NRR, ARR growth, and EBITDA margin improvements are common OKR Key Results in SaaS companies
External Resources
- WhatMatters.
com — John Doerr’s official OKR resource; definitions, examples, and case studies - Google re:
Work — Set Goals with OKRs:  Google’s internal OKR guide made public - Perdoo OKR Guide — Comprehensive practitioner guide covering structure, cadence, and scoring
- Harvard Business Review — The Secret OKR Sauce at Google
- Betterworks — OKRs vs.
 KPIs:  Understanding the Relationship Between the Two Frameworks
Disclaimer
The information provided in this article is intended for educational and informational purposes only. OKR framework descriptions, best practices, scoring conventions, and benchmark guidance reflect general industry conventions and widely cited practitioner literature as of the time of writing. Implementation approaches, cadences, and scoring methodologies vary significantly across organisations, industries, and cultural contexts. References to specific companies, software products, and published works are provided for illustrative and educational purposes only and do not constitute endorsement. Nothing in this article constitutes management consulting, legal, financial, or professional advice. Readers should conduct independent research and consult qualified professionals before implementing goal-setting frameworks within their organisations. Uninformed Investors makes no representation as to the accuracy, completeness, or timeliness of the information contained herein.
OKR definition is ready. The article covers the full framework: structure and formula, Objectives characteristics, Key Results characteristics, OKR levels and alignment cascade, OKR vs. KPI distinction, cycle and cadence, committed vs. aspirational OKRs, scoring (0.0–1.0 scale), cross-functional examples, common mistakes, OKR vs. MBO comparison, relationship to SMART framework, software tools, investor and ESG context, limitations including metric gaming, and all related terms.