Definition
Objectives and Key Results (OKR) is a collaborative goal-setting framework used by individuals, teams, and organizations to define ambitious, measurable goals and track their outcomes over short, recurring cycles — typically quarterly. An OKR consists of two components:
- Objective — a significant, concrete, action-oriented, and inspirational goal describing what an organization or team wants to achieve.
- Key Results — typically three to five measurable success criteria used to track progress toward the objective, each with a numeric target and a defined timeframe.
The framework was developed by Andrew S. (“Andy”) Grove, then COO and later CEO of Intel, in the early 1970s. Grove built on Peter Drucker’s 1954 concept of Management by Objectives (MBO) — introduced in The Practice of Management — and refined it by pairing each qualitative objective with measurable key results. Grove documented the approach in his 1983 book High Output Management. In a 1975 internal Intel training course, he taught the method to a young salesperson named John Doerr.
Doerr later became a partner at the venture capital firm Kleiner Perkins and, in 1999, introduced OKRs to Google co-founders Larry Page and Sergey Brin when the company had roughly 30–40 employees. Google adopted OKRs and uses them to this day. Doerr popularized the framework more broadly in his 2018 book Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs. Organizations using OKRs today include LinkedIn, Adobe, Spotify, Netflix, Deloitte, BMW, Schneider Electric, and many others.
OKRs are typically associated with five core principles, which Doerr summarizes with the acronym F.A.C.T.S.:
- Focus
- Alignment
- Commitment
- Tracking
- Stretching
How It Relates to Marketing
OKRs are widely used in marketing for goal setting, team alignment, campaign planning, and performance measurement. Marketing applications include:
- Marketing strategy execution — translating annual marketing strategy into quarterly objectives and measurable key results.
- Cross-functional alignment — connecting marketing OKRs to product, sales, customer success, and finance OKRs to ensure coordinated effort across functions.
- Campaign performance management — defining the outcomes (not the activities) marketing campaigns are expected to produce, such as qualified pipeline created, brand lift, or organic reach.
- Channel and team accountability — assigning ownership of specific key results to teams such as demand generation, content, brand, lifecycle, and product marketing.
- Budget allocation — using OKRs to justify and prioritize marketing investments based on the outcomes they are expected to drive.
- Brand and growth balance — using a mix of growth-oriented and brand-oriented OKRs to avoid over-indexing on short-term performance metrics.
- Stretching ambition — encouraging marketers to set aspirational goals (such as category leadership or share-of-voice gains) rather than incremental targets.
How to Write an OKR
OKRs are a qualitative goal-setting structure rather than a numerical calculation. The basic structure is:
I will / We will (Objective) as measured by (Key Results).
A simple Doerr-cited example:
“I will fix the website for the vast majority of people as measured by 7 out of 10 people being able to get through, a 1-second response time, and a 1% error rate.”
The Standard OKR Process
- Define a short list of objectives. Typically three to five objectives per cycle for an organization, team, or individual. Objectives should be significant, concrete, action-oriented, and inspirational — not business-as-usual.
- Define three to five key results per objective. Each key result must be measurable and time-bound. Together, achieving all the key results should imply the objective has been met.
- Establish cycle length. Quarterly is the most common cadence, sometimes paired with longer annual or multi-year objectives.
- Make OKRs transparent. OKRs are typically published organization-wide so every employee can see what others are working on. Transparency is considered essential to alignment.
- Track regularly. Most organizations check in on progress weekly or bi-weekly and conduct a formal mid-cycle review at the midpoint of the cycle.
- Grade at cycle end. Score key results on a scale (commonly 0.0 to 1.0). Average key result scores produce the objective’s overall score.
- Decouple from compensation. Doerr and Grove both emphasized that OKRs should be separated from compensation and performance reviews to preserve their use as stretch tools.
Aspirational vs. Committed OKRs
| Type | Purpose | Target Achievement | Typical Use |
|---|---|---|---|
| Committed OKRs | Operational outcomes that must be delivered (deadlines, launches, “done” milestones) | 1.0 (100%) | Reliable execution of must-deliver work |
| Aspirational (“Moonshot”) OKRs | Ambitious stretch goals encouraging breakthrough thinking | ~0.7 (70%) is considered very strong | Growth and innovation work |
Doerr recommends a target achievement rate of about 70% for aspirational key results. A 70% success rate encourages competitive goal-making that is meant to stretch workers at low risk. If 100% of the key results are consistently being met, the key results should be reevaluated. Washington State University Libraries
How to Utilize OKRs
Common use cases include:
- Annual and quarterly planning — translating long-term vision and strategy into focused short-term goals.
- Cross-functional alignment — ensuring product, engineering, sales, marketing, and operations teams pursue compatible objectives.
- Cascading goals — connecting company-level objectives to team objectives, with each team’s key results contributing to higher-level outcomes.
- Prioritization — using OKRs to make explicit decisions about what not to work on.
- Performance dialogue — providing a structured agenda for one-on-ones, team reviews, and operating reviews.
- Investor and board communication — articulating measurable commitments and tracking progress against them.
- Marketing accountability — replacing activity-based reporting (“we ran X campaigns”) with outcome-based reporting (“we generated Y in qualified pipeline”).
- Personal goal setting — many practitioners apply OKRs to individual professional development goals.
OKR Levels
Historically OKRs were set at the company, team, and individual levels. OKRs were once typically set at the individual, team, and organization levels; however, most organizations no longer define OKRs for individual contributors as these OKRs tend to look like a task list and lead to conflating OKRs with performance reviews. Modern practice generally focuses on company and team levels and avoids individual OKRs. Washington State University Libraries
Comparison to Similar Frameworks
| Framework | Focus | Origin | Primary Use |
|---|---|---|---|
| OKR | Objectives + 3–5 measurable Key Results, transparent and time-bound | Andy Grove / Intel (1970s) | Strategy execution; alignment; stretch goals |
| Management by Objectives (MBO) | Cascading individual objectives tied to compensation | Peter Drucker (1954) | Traditional performance management |
| SMART Goals | Specific, Measurable, Achievable, Relevant, Time-bound | Doran (1981) | Individual and team goal-setting |
| Balanced Scorecard (BSC) | Strategy translated into four perspectives with KPIs | Kaplan & Norton (1992) | Strategy execution and performance measurement |
| KPIs | Quantitative measures of ongoing performance | Multiple origins | Operational performance tracking |
| V2MOM | Vision, Values, Methods, Obstacles, Measures | Marc Benioff / Salesforce (1999) | Salesforce-style strategic alignment |
| OGSM | Objectives, Goals, Strategies, Measures | Procter & Gamble origin | Strategy execution at consumer goods companies |
| Hoshin Kanri | Policy deployment cascading | Toyota / Japanese management | Lean strategy deployment |
OKRs differ from MBOs in that they are set on shorter cycles (typically quarterly), are transparent across the organization, are decoupled from compensation, and pair qualitative objectives with measurable key results. They differ from KPIs in that OKRs describe what an organization is trying to change, while KPIs describe what an organization is trying to monitor.
Best Practices
- Limit to a few objectives. Most practitioners recommend three to five objectives per organization or team per cycle. More than five typically signals a lack of focus.
- Keep three to five key results per objective. Each key result should be measurable, time-bound, and aggressive but achievable.
- Make key results outcomes, not activities. “Launch three campaigns” is an activity. “Generate $5M in qualified pipeline from campaigns” is an outcome.
- Avoid vague verbs. Words like “help” and “consult” should also be avoided as they tend to be used to describe vague activities rather than concrete, measurable outcomes. Washington State University Libraries
- Make OKRs transparent. Every employee should be able to see organization- and team-level OKRs. Transparency is what produces alignment.
- Decouple OKRs from compensation. Tying OKRs to pay encourages employees to set easy goals — defeating the framework’s purpose as a stretch tool.
- Grade aspirational OKRs against ~70%. A consistent 100% achievement rate on aspirational OKRs indicates the targets are insufficiently ambitious.
- Don’t cascade individual OKRs. Most practitioners now recommend setting OKRs at the company and team levels rather than the individual level, to avoid turning OKRs into task lists or performance reviews.
- Pair with regular check-ins. OKRs work best when paired with frequent (weekly or biweekly) check-ins and a structured mid-cycle review.
- Distinguish committed from aspirational OKRs. Mixing high-confidence delivery goals with stretch goals without distinguishing them confuses teams about which to deliver.
- Avoid “OKR theater.” OKRs that are written, filed, and forgotten produce no benefit. They must be actively used to inform prioritization.
Future Trends
- AI-assisted OKR drafting and review. AI tools are increasingly used to help teams draft, refine, and review OKRs, suggest measurable key results, and flag common issues (vague verbs, activity-based key results, conflict with other OKRs).
- Continuous performance management. OKRs are increasingly paired with continuous feedback, one-on-one tools, and lightweight check-ins rather than annual performance reviews.
- Decline of individual OKRs. The original three-level (company, team, individual) model has shifted toward company and team OKRs only, with individuals pursuing personal development goals separately.
- Outcome-based OKRs for marketing and customer experience. Marketing teams increasingly write OKRs around customer outcomes (retention, NPS, lifetime value) and brand outcomes (awareness, consideration) rather than activity metrics.
- OKRs in non-profits and government. OKRs are spreading from technology companies into nonprofits, education, and public-sector organizations, often via Doerr’s Measure What Matters case studies (including Bono’s ONE Campaign and the Bill & Melinda Gates Foundation).
- Tool consolidation. Dedicated OKR platforms (such as Workpath, Peoplelogic, and others) are converging with broader work-management, strategy-execution, and HR platforms.
FAQs
1. Who created OKRs? Andy Grove, then COO of Intel, developed the methodology in the early 1970s as an evolution of Peter Drucker’s Management by Objectives. Grove documented it in his 1983 book High Output Management. John Doerr, who learned the method from Grove at Intel in 1975, introduced it to Google in 1999 and popularized it widely.
2. What is the difference between an Objective and a Key Result? The Objective is the qualitative, inspirational goal — what you want to accomplish. Key Results are the measurable success criteria — how you will know you’ve accomplished it. Typically there are three to five Key Results per Objective.
3. How often are OKRs set? Quarterly is the most common cadence, often paired with longer annual objectives. Some organizations operate on different cycles (such as trimesters or six-week sprints) based on industry rhythm.
4. Should OKRs be linked to compensation? Most practitioners — including Grove and Doerr — recommend keeping OKRs separate from compensation. Linking pay to OKR achievement encourages employees to set easy goals rather than ambitious ones.
5. What is the difference between OKRs and KPIs? KPIs are ongoing performance measures that show how well something is running (e.g., monthly active users, NPS). OKRs are time-bound goals that show what you are trying to change (e.g., increase monthly active users by 25% this quarter). Many KPIs become Key Results when an organization decides to actively improve them.
6. What is the difference between OKRs and SMART Goals? SMART (Specific, Measurable, Achievable, Relevant, Time-bound) is a goal-formulation checklist. OKR is a structured framework with objectives, key results, transparency, scoring, and a cadence. The two are compatible — a well-formulated Key Result typically meets SMART criteria.
7. What is the target achievement rate for OKRs? For aspirational (“moonshot”) OKRs, a target of roughly 70% achievement is widely cited. Consistent 100% achievement indicates the OKRs were not ambitious enough. For committed OKRs — operational deliverables — full delivery (100%) is expected.
8. How are OKRs scored? Google’s standard approach scores each key result on a 0.0–1.0 scale, then averages those scores to produce the objective’s score. Some organizations use a simpler red/yellow/green system or Andy Grove’s original yes/no grading.
9. Should individuals have OKRs? Modern practice typically focuses on company- and team-level OKRs and avoids individual OKRs. Individual OKRs tend to become task lists and to get conflated with performance management, which undermines the framework’s intent.
10. What are the most common failure modes for OKRs? Common failures include too many OKRs (lack of focus), activity-based key results (running campaigns rather than outcomes), key results that lack measurable targets, OKRs treated as static documents rather than active tools, linking OKRs to compensation (which discourages stretch), and cascading OKRs so rigidly that lower-level teams lose autonomy.
Related Terms
- Management by Objectives (MBO)
- SMART Goals
- Objectives and Key Results (OKR)
- Key Performance Indicators (KPIs)
- FAST Goals
- Balanced Scorecard (BSC)
- V2MOM Framework
- OGSM Framework
- Hoshin Kanri
- Strategy Execution
- Cascading Goals
- Stretch Goals (Moonshots)
Sources
- Doerr, J. Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs. Portfolio / Penguin, 2018. https://www.whatmatters.com/the-book
- Grove, A. S. High Output Management. Random House, 1983 (reissued by Vintage 1995). https://www.penguinrandomhouse.com/books/74108/high-output-management-by-andrew-s-grove/
- Drucker, P. F. The Practice of Management. Harper & Brothers, 1954. https://www.harpercollins.com/products/the-practice-of-management-peter-f-drucker
- What Matters — “What Is an OKR? Definition and Examples.” https://www.whatmatters.com/faqs/okr-meaning-definition-example
- What Matters — “OKRs History: Andy Grove and Intel.” https://www.whatmatters.com/articles/the-origin-story
- Google re:Work — “Set Goals with OKRs.” https://rework.withgoogle.com/intl/en/guides/set-goals-with-okrs
- Wikipedia — “Objectives and Key Results.” https://en.wikipedia.org/wiki/Objectives_and_key_results
- Coda — “6 Key Moments That Have Shaped OKRs.” https://coda.io/blog/okrs/6-key-moments-that-have-shaped-okrs
- Workpath Magazine — “Google’s OKR Success Story.” https://www.workpath.com/en/magazine/okr-google
- Peoplelogic — “A History of Objectives and Key Results (OKRs).” https://peoplelogic.ai/blog/history-of-objectives-and-key-results
