OKRs

OKRs (Objectives and Key Results) is a goal-setting framework that pairs qualitative ambitious objectives with measurable key results to align teams around outcomes. Originally developed at Intel by Andy Grove in the 1970s and brought to Google by John Doerr in 1999, OKRs are typically cascaded from company down to team and sometimes individual, on quarterly or annual cycles, and used to align teams around outcomes rather than activities. Most OKR implementations fail because organizations adopt the format without the discipline that makes OKRs actually work. It is one of the most-adopted goal-setting frameworks of the 2010s and one of the most-poorly-implemented.

The structure:

Objective: qualitative, ambitious, time-bound statement of what the company/team/individual wants to achieve in the period. Should be inspirational and clear.

• Good: "Make our SaaS product the obvious choice for SMB sales teams."
• Bad: "Improve product."

Key Results: 2-5 measurable outcomes that indicate whether the objective was achieved. Each KR is specific and quantifiable.

• Good: "Sign 50 new SMB sales team customers in Q2."
• Bad: "Get more customers."

The principles that make OKRs work:

Objectives are aspirational, not certain:

• OKRs are meant to be ambitious; 70-80% achievement is considered success.
• 100% achievement on every OKR signals the objectives weren't ambitious enough.
• Stretch goals drive bigger thinking and bigger results.

Key Results are outcomes, not activities:

• Wrong: "Launch new pricing page" (activity).
• Right: "Increase conversion rate from pricing page by 30%" (outcome).
• The distinction matters because activities can be completed without producing the desired outcome.

Cascading from company to team to individual:

• Company OKRs set top-level direction.
• Team OKRs reflect how each team contributes to company objectives.
• Individual OKRs (where used) reflect personal contributions.
• Cascade creates alignment without rigid top-down control.

Quarterly cadence (typically):

• Quarterly OKRs balance ambition with feedback loops.
• Annual OKRs at company level; quarterly at team level common.
• More frequent than annual; less frequent than monthly.

Transparency:

• OKRs are typically visible to the entire organization.
• Creates alignment and reduces redundant work.
• Some companies use OKR-management tools (Lattice, Ally, WorkBoard) for visibility.

Decoupled from compensation:

• OKRs are about ambitious goals; compensation tied to OKRs distorts goal-setting (people set easy goals).
• Best practice: separate OKRs from performance reviews and compensation decisions.

Why OKRs commonly fail:

Treated as bureaucracy:

• OKRs become a quarterly ritual disconnected from actual work.
• Set in January, forgotten by March.
• Reviewed only at quarter-end.

Activities masquerading as outcomes:

• "Launch X, build Y, hire Z" filling KR slots.
• Doesn't measure outcomes; just activities.

Cascading rigidly top-down:

• Team OKRs forced to match company OKRs exactly.
• Loses the autonomy that makes OKRs work.

Linked to compensation:

• People set conservative OKRs to ensure achievement.
• Defeats the ambitious-goal-setting purpose.

Too many OKRs:

• 10 objectives with 5 KRs each = 50 things to track.
• Loses focus; nothing actually gets prioritized.

Operating disciplines that make OKRs work:

• Monthly check-ins (not just quarter-end).
• Mid-quarter adjustments if circumstances change.
• Explicit prioritization: 2-5 objectives per team max.
• Clear distinction between activities and outcomes in KRs.
• Decoupling from compensation.
• Leadership engagement throughout the quarter.

What founders get wrong: Adopting OKRs as ritual without the discipline that makes them useful (too many objectives, activities disguised as outcomes, no mid-quarter check-ins, linked to compensation, set-and-forget). The right discipline: 2-5 ambitious objectives per team, outcome-focused KRs, monthly check-ins, decoupling from compensation, consistent leadership engagement. OKRs work when they're a real management system, not when they're a quarterly ritual.

Related: KPIs · North Star Framework · Strategic Planning · Quarterly Planning · Performance Review

FAQ

What are OKRs?
Objectives and Key Results: a goal-setting framework popularized at Google (originally Intel) pairing qualitative ambitious objectives (what we want to achieve) with measurable key results (how we'll know we achieved it). Typically cascaded from company to team to individual on quarterly or annual cycles.

What makes OKRs different from regular goals?
OKRs are designed to be ambitious (70-80% achievement is success; 100% means goals were too easy), outcome-focused (KRs measure outcomes not activities), cascaded with alignment (not rigid control), transparent across the organization, and decoupled from compensation (preserves ambition).

Why do most OKR implementations fail?
Treated as bureaucratic ritual rather than active management system. Common failures: activities masquerading as outcomes, too many OKRs per team, linked to compensation (defeats ambition), set-and-forget approach (no mid-quarter check-ins), and rigid top-down cascading. The discipline matters more than the format.