OKR (Objectives and Key Results)
Also known as: OKRs, Objectives & Key Results
A goal-setting framework that defines ambitious Objectives (what you want to achieve) paired with measurable Key Results (how you'll know you've achieved it), creating alignment and focus across the organization.
Quick Reference
Memory Aid
Objective = Where do we want to go? Key Results = How will we know we're there?
TL;DR
Set 3-5 ambitious Objectives per quarter, each with 3-5 measurable Key Results. Cascade from company to teams. Review weekly, score quarterly. 70% achievement = success.
What Is OKR (Objectives and Key Results)?
OKRs are simple: set a bold Objective (what you want to achieve), then define 3-5 Key Results (measurable outcomes that prove you achieved it). Set them quarterly, review them regularly, and score them at the end.
Ideas are easy. Execution is everything.
— John Doerr
OKRs create alignment by cascading goals from the company level to teams and individuals, ensuring everyone is rowing in the same direction. Objectives are qualitative, inspiring, and time-bound. Key Results are quantitative, measurable, and verifiable. OKRs should be ambitious — achieving 70% is considered good. This 'stretch' mentality encourages innovation and prevents sandbagging. OKRs are public within the organization, creating transparency and accountability. They are typically set quarterly and reviewed weekly or biweekly.
OKR Alignment Hierarchy
A hierarchical cascade showing Company OKRs at the top flowing down to Team OKRs and then Individual OKRs. Each Objective branches into 3-5 measurable Key Results.
Level 1
3-5 company-wide Objectives set by leadership, each with 3-5 Key Results
Level 2
Team OKRs that contribute to company OKRs (mix of top-down and bottom-up)
Level 3
Personal OKRs aligned to team goals (optional in some implementations)
Origin & Context
Andy Grove developed OKRs at Intel, building on Peter Drucker's Management by Objectives. John Doerr later brought OKRs to Google in 1999, where they became foundational to the company's culture and growth.
Core Components
Objectives
Qualitative, inspiring statements of what you want to achieve. They should be ambitious and motivating.
Example
Objective: 'Become the #1 customer-rated platform in our category.'
Key Results
Quantitative, measurable outcomes that indicate whether the objective has been achieved.
Example
KR1: Achieve NPS of 60+. KR2: Reduce support ticket resolution time to < 4 hours. KR3: Increase monthly active users by 40%.
Scoring
At the end of each cycle, score each Key Result from 0 to 1.0. A score of 0.7 is considered a strong result.
Example
KR1: NPS reached 55 → score 0.8. KR2: Resolution time at 5 hours → score 0.6. KR3: MAU grew 35% → score 0.85.
Google has used OKRs since it had fewer than 40 employees. Larry Page credits OKRs with helping Google achieve 10x growth multiple times.
When to Use OKR (Objectives and Key Results)
Quarterly goal setting for fast-moving companies
Problem it solves: Creates focus and alignment in environments where priorities shift rapidly.
Real-World Application
A Series B startup uses OKRs to ensure all 8 teams are aligned on the quarter's top priorities, reviewing progress in weekly all-hands meetings.
Scaling organizational alignment
Problem it solves: As organizations grow, maintaining alignment becomes harder. OKRs make goals visible and connected.
Real-World Application
Google uses OKRs at every level — company, team, and individual — all visible to every employee, creating transparency at massive scale.
OKRs should NOT be tied to compensation or performance reviews. If they are, people will sandbag and set easy goals. Keep them aspirational.
How to Apply OKR (Objectives and Key Results): Step by Step
Before You Start
- →Clear company strategy and priorities
- →Leadership buy-in to the OKR process
- →Willingness to set ambitious goals and accept partial achievement
Set Company-Level OKRs
Leadership defines 3-5 company Objectives with 3-5 Key Results each for the quarter.
Tips
- ✓Fewer is better — 3 Objectives with 3 KRs each is ideal
Common Mistakes
- ✗Setting too many OKRs, diluting focus
Cascade to Teams
Teams create their own OKRs that contribute to company OKRs.
Tips
- ✓Allow bottom-up input — about 40% of OKRs should come from teams
Common Mistakes
- ✗Pure top-down cascading without team input
Review Weekly
Check progress on Key Results in weekly team meetings.
Tips
- ✓Use a simple red/yellow/green status for each KR
Common Mistakes
- ✗Setting OKRs and forgetting about them until the end of the quarter
Score and Reflect
At quarter end, score each KR from 0-1.0 and reflect on learnings.
Tips
- ✓A score of 0.7 is success — if you're hitting 1.0, your goals aren't ambitious enough
Common Mistakes
- ✗Treating 0.7 as failure — it means the stretch target worked
Value & Outcomes
Primary Benefit
Creates focus, alignment, and accountability around the most important goals each quarter.
Additional Benefits
- ✓Makes goals transparent across the organization
- ✓Encourages ambitious goal-setting through the stretch mentality
- ✓Provides a simple, repeatable cadence for goal management
What You'll Learn
- →How to set ambitious yet achievable goals
- →How to measure progress with quantitative key results
- →How to create alignment across a growing organization
Typical Outcomes
Best Practices
📋 Preparation
- •Clarify company strategy before setting OKRs
- •Train teams on the OKR methodology before the first cycle
🚀 Execution
- •Keep it simple — 3-5 Objectives, 3-5 KRs each
- •Make OKRs visible to everyone in the organization
🔄 Follow-Up
- •Score quarterly and share learnings
- •Iterate the process — the first 2-3 cycles are learning cycles
💎 Pro Tips
- •Separate committed OKRs (must achieve) from aspirational OKRs (stretch goals) so teams know which are non-negotiable
Intel's Operation Crush
One of the earliest and most celebrated uses of OKRs was Intel's 'Operation Crush' in 1980, where Andy Grove set a company-wide objective to make the 8086 processor the dominant chip in the market against Motorola's 68000. The cascaded OKRs aligned sales, engineering, and marketing teams so effectively that Intel won over 2,000 design wins in a single year, establishing x86 architecture dominance that persists to this day.
— John Doerr, Measure What Matters
Limitations & Pitfalls
Can create tunnel vision if OKRs are too narrow
Mitigation: Include both output KRs and health metrics to prevent unintended consequences
First few cycles are often messy as the organization learns the process
Mitigation: Treat the first 2-3 quarters as learning experiments and don't judge too harshly
Apply OKR (Objectives and Key Results) with Stratrix
Turn this framework into a professional strategy deck in under a minute. Stratrix applies OKR (Objectives and Key Results) automatically to your business context.
Try Stratrix Free