OKRs (Objectives and Key Results)

Overview

OKRs, developed at Intel by Andy Grove and popularized by John Doerr at Google, provide a goal-setting framework that separates inspirational direction (Objectives) from measurable progress (Key Results). The core insight: most goal systems fail either by being too vague (mission statements) or too metric-obsessed (KPIs without context). OKRs solve this by pairing qualitative ambition with quantitative accountability. The framework operates on quarterly cycles with weekly check-ins, creating rhythm and forcing regular recalibration. Scoring at 0.6-0.7 (not 1.0) signals proper ambition - if you're hitting 100%, you're not aiming high enough.

When to Use

Aligning fast-growing organizations where teams can drift out of sync
Shifting from output metrics (features shipped) to outcome metrics (user impact)
Creating transparency and accountability across departments
Breaking annual planning into actionable quarterly commitments
Cascading strategy from company to team to individual level
Focusing effort when everything feels equally important
Providing common language for cross-functional collaboration

The Process

Step 1: Define Company-Level Objectives (3-5 Max)

Start with 3-5 company objectives for the quarter. Objectives should be qualitative, inspirational, and clearly directional. They answer "what do we want to achieve?" not "how much?" Good objectives are memorable, motivating, and create alignment. Test: can everyone in the company explain why this matters? Example: "Become the most trusted platform in fintech" (not "Improve trust score by 20%").

Step 2: Attach Key Results to Each Objective (3-5 per Objective)

Key Results are quantitative measures that indicate whether the objective is being achieved. They must be: specific (exact number), measurable (can track), time-bound (by end of quarter), outcome-based (not activity). Write as "verb + what you're measuring + from X to Y". Each objective gets 3-5 KRs. Example: For "most trusted platform": KR1: Increase NPS from 35 to 55, KR2: Reduce security incidents from 4/quarter to 0, KR3: Achieve SOC2 Type II certification.

Step 3: Set Ambitious but Achievable Targets (60-70% Confidence)

If you're confident you'll hit 100% of a KR, it's not ambitious enough. Target 60-70% confidence level. This creates "stretch" that drives innovation and prevents sandbagging. Distinguish between committed OKRs (must hit, 100% confidence) and aspirational OKRs (stretch, 60-70% confidence). Most OKRs should be aspirational. Example: Moving NPS from 35 to 55 might be aspirational (50% stretch); moving from 35 to 42 would be committed.

Step 4: Cascade to Team and Individual OKRs

Teams set OKRs that contribute to company objectives - not identical copies, but complementary contributions. Use both top-down (what company needs from us) and bottom-up (what we see as opportunities). Individual OKRs are optional but useful for alignment. About 60% of team OKRs should ladder to company OKRs; 40% can be team-specific priorities. Example: Company objective: "Become most trusted." Product team KR: "Zero critical bugs in production." Support team KR: "First response under 2 hours, resolution under 24 hours."

Step 5: Make OKRs Public and Visible

Transparency is essential - all OKRs visible to entire organization. This creates accountability, enables cross-team coordination, and surfaces conflicts early. Use shared tools (Notion, Lattice, simple spreadsheets). Include context: why this matters, what's the hypothesis, what trade-offs were made. Example: Company-wide OKR dashboard showing all team OKRs, current confidence levels, and progress indicators.

Step 6: Conduct Weekly Check-ins and Update Confidence

OKRs without rhythm become "set and forget." Weekly ritual: update confidence level (0-100%) for each KR, note what changed, identify blockers. This isn't status reporting - it's recalibration. Low confidence early = opportunity to course-correct. Check-ins should take 15-30 minutes, not hours. Example: Monday team standup: "KR2 confidence dropped from 70% to 40% - our hypothesis about mobile was wrong. Pivoting strategy this week."

Step 7: Score and Reflect at Quarter End

Score each KR 0.0-1.0 based on achievement. Average scores across KRs for objective score. Target: 0.6-0.7 average indicates proper ambition. Score 0.9-1.0 = sandbagging (set harder goals). Score below 0.4 = poor execution or unrealistic target. Conduct retrospective: what worked, what didn't, what did we learn? Inform next quarter's OKRs. Example: KR achieved 80% of target = 0.8 score. If consistently scoring 0.9+, add 20% stretch to next quarter's targets.

Example Application

Situation: 150-person SaaS company with functional silos. Engineering ships features, Marketing runs campaigns, Sales closes deals - but no one owns customer outcomes. Net revenue retention declining.

Application:

Step 1: CEO set 3 company objectives: "Customers succeed spectacularly with our product" (NRR focus), "Build world-class team" (hiring), "Establish category leadership" (market)
Step 2: First objective KRs: NRR from 95% to 110%, customer health score from 65 to 80, time-to-value from 45 days to 14 days
Step 3: NRR to 110% set at 60% confidence (ambitious but possible based on benchmarks); time-to-value at 70% (hard but achievable with focus)
Step 4: Product team OKR: "Accelerate customer activation" with KRs on onboarding completion rates. CS team OKR: "Proactive customer success" with KRs on health score interventions
Step 5: All OKRs in Notion, reviewed at all-hands, CEO updates confidence weekly in Slack
Step 6: Weekly team check-ins surfaced onboarding blocker in week 3; pivoted resources immediately
Step 7: End of Q2: Objective score 0.68 (good calibration). NRR reached 104% (0.45), health score reached 78 (0.87), time-to-value reached 21 days (0.72)

Outcome: Cross-functional alignment emerged naturally - teams started collaborating because their OKRs interconnected. NRR stabilized and began improving. OKR retrospective identified that time-to-value KR unlocked the most learning.

Anti-Patterns

Sandbagging: Setting easy targets to guarantee 1.0 scores
Using OKRs for performance reviews (kills ambitious goal-setting)
Activity-based KRs: "Launch 5 features" instead of "Increase retention to 90%"
Too many OKRs: More than 3-5 objectives means lack of focus
Set-and-forget: No weekly check-ins or confidence updates
Cascading literally: Every team has identical copy of company OKR
Individual OKR obsession: Spending more time on individual OKRs than team OKRs
Changing OKRs mid-quarter (except in genuine strategic shifts)
Grading KRs subjectively instead of against specific numeric targets

High Output Management - Grove's original framework that introduced OKRs at Intel
Measure What Matters (John Doerr) - comprehensive OKR implementation guide
North Star Metric - complementary framework for identifying single most important metric
DACI Framework - decision-making framework that helps achieve OKR commitments
V2MOM (Salesforce) - alternative goal-setting framework (Vision, Values, Methods, Obstacles, Measures)
Radical Focus (Christina Wodtke) - narrative-based OKR implementation guide
Key Performance Indicators (KPIs) - ongoing metrics that OKRs can target improving

okrs