Skip to main content
Category: Methods
Type: Goal-Setting Framework
Origin: Andy Grove, Intel, 1970s / John Doerr, Google, 1990s
Also known as: Objectives and Key Results
Quick Answer — OKR (Objectives and Key Results) is a collaborative goal-setting framework that helps organizations align around ambitious objectives and track progress through measurable key results. Originally developed by Andy Grove at Intel and popularized at Google by John Doerr, the framework works by setting 3-5 bold objectives per period, each accompanied by 3-5 quantifiable key results. The power of OKR lies in its ability to create transparency, foster alignment, and encourage ambitious thinking while maintaining accountability through measurable outcomes.

​
What is OKR?

OKR is a goal-setting methodology that connects ambitious objectives to specific, measurable outcomes. Unlike traditional goal-setting that focuses on完成任务 (completing tasks), OKR distinguishes between the direction you want to go (the Objective) and how you’ll know you’ve gotten there (the Key Results). This separation is critical because it allows teams to be ambitious about their direction while staying grounded in measurable progress. The framework operates on a simple but powerful principle: what gets measured gets managed, but what gets measured must actually matter. An objective describes what you want to achieve—a qualitative, inspirational statement of direction. Key results are quantitative metrics that define how you’ll measure success. Together, they create a compass that guides effort while allowing flexibility in how teams reach their goals.
“The key is not to prioritize what’s on your schedule, but to schedule your priorities.” — Stephen Covey
OKRs are typically set at multiple levels within an organization—company-wide, team, and individual—with each level cascading down while maintaining alignment. This cascading structure ensures that every person’s work connects to larger organizational goals, creating a sense of purpose and context that motivates sustained effort.

​
OKR in 3 Depths

  • Beginner: Start with one objective and three key results. Make key results measurable (e.g., “increase revenue from 1Mto1M to 1.5M” rather than “increase revenue”). Review OKRs weekly and adjust as needed. Keep objectives inspirational and key results specific.
  • Practitioner: Set OKRs quarterly with 60-70% completion as the target—too easy undermines ambition, too hard destroys motivation. Use outcome-oriented key results rather than output-oriented tasks. Align team OKRs with company OKRs while allowing teams to create their own objectives. Track progress transparently across the organization.
  • Advanced: Implement nested OKRs across all organizational levels with clear alignment maps. Use OKRs to drive innovation by including stretch goals (70%+ difficulty). Combine OKRs with other frameworks like CFRs (Conversations, Feedback, Recognition). Run OK retrospectives to continuously improve the OKR process itself.

​
Origin

The OKR framework traces back to Andy Grove, the legendary CEO of Intel, who developed the concept in the 1970s. Grove recognized that traditional management approaches failed to capture the dynamic nature of technology companies where goals needed to be continuously adjusted as conditions changed. He introduced the concept of “objectives and key results” as a way to translate strategic direction into measurable outcomes that could be tracked and evaluated. John Doerr, who learned OKR from Grove while at Intel, introduced the framework to Google in 1999 when the company was still a small startup. Doerr, who later wrote the bestselling book “Measure What Matters,” convinced Google’s founders Larry Page and Sergey Brin to adopt OKRs as their primary goal-setting system. Google’s rapid growth and success helped popularize OKRs globally, and the framework has since been adopted by companies including Amazon, Microsoft, LinkedIn, and many others. The framework gained further traction in the 2010s as agile methodologies transformed how organizations approach goal-setting. Unlike annual planning cycles that had dominated corporate management, OKRs embrace shorter cycles (typically quarterly) that allow organizations to adapt more quickly to changing conditions while maintaining strategic focus.

​
Key Points

1

Set Inspirational Objectives

Objectives should be qualitative, ambitious, and actionable. They describe the direction you want to go and should inspire teams to stretch beyond their comfort zone. A good objective answers the question: “Where do we want to go?” Avoid generic objectives like “improve sales” in favor of more specific directional statements like “become the preferred choice for enterprise customers in our market.”
2

Define Measurable Key Results

Key results should be quantifiable metrics that indicate whether the objective has been achieved. Each objective typically has 3-5 key results. The key is to focus on outcomes (the result of work) rather than outputs (the work itself). For example, “launch 5 new features” is an output; “increase daily active users by 25%” is an outcome.
3

Align Across Levels

Company OKRs cascade to team OKRs, which cascade to individual OKRs. Each level should understand how their work contributes to the larger organizational goals. Alignment doesn’t mean copying—it means connecting your objectives to broader organizational direction while maintaining autonomy in how you achieve them.
4

Track Progress Regularly

OKRs require ongoing attention throughout the cycle. Weekly check-ins help teams identify blockers, celebrate progress, and adjust course when needed. Transparency is essential—sharing OKRs across the organization enables collaboration and helps identify dependencies.

​
Applications

Strategic Planning

OKRs help organizations translate vision into actionable goals. By breaking down strategic priorities into measurable key results, leadership can track whether strategy is actually executing as planned and make adjustments quickly.

Product Development

Product teams use OKRs to balance feature delivery with outcome achievement. Rather than simply shipping features, teams focus on metrics like user engagement, retention, and revenue that demonstrate genuine value creation.

Organizational Alignment

OKRs create transparency about priorities across the entire organization. When everyone can see how their work connects to company goals, silos break down and cross-functional collaboration improves.

Performance Management

While OKRs are not meant to be directly tied to compensation, they provide context for performance conversations. Understanding what someone tried to achieve and what they accomplished helps managers provide more meaningful feedback.

​
Case Study

Context: In 2013, the Wikimedia Foundation, the non-profit that operates Wikipedia, was struggling with declining editor engagement and a sense that the organization had lost its strategic direction. Leadership wanted to reignite the community’s passion while also achieving measurable growth in editor participation. Question: How could Wikimedia create a goal-setting system that would motivate a global volunteer community while also driving measurable improvements in editor engagement and content quality? Evidence: The foundation implemented OKRs with input from the volunteer community. Their first set of OKRs included objectives like “Increase editor engagement and retention” with key results such as “Increase the number of active editors making 5+ edits per month from 80,000 to 100,000” and “Reduce the activation time for new editors from 14 days to 7 days.” They made their OKRs transparent on a public wiki page, allowing the entire community to track progress and contribute ideas. Result: Over the next two years, Wikimedia achieved significant improvements in their key metrics. Active editor numbers increased by approximately 25%, and new editor retention improved substantially. The transparent OKR process also helped the community feel more connected to the organization’s strategic priorities. Lesson: OKRs work even in decentralized, volunteer-driven organizations when transparency and community involvement are built into the process. The key was making OKRs visible and participatory rather than a top-down mandate.

​
Boundaries and Failure Modes

OKRs are powerful but not universally applicable. Understanding when not to use them prevents common pitfalls:
  • Purely operational work: If your work consists primarily of maintaining existing systems or following compliance requirements, OKRs may add overhead without value. The framework works best when there’s meaningful latitude in how goals are achieved.
  • When measurement is counterproductive: Some important outcomes are difficult or dangerous to measure. Measuring proxy metrics can lead to gaming the system. If you can’t define meaningful outcomes without creating perverse incentives, OKRs may cause harm.
  • Without organizational commitment: OKRs require significant organizational discipline—regular check-ins, transparent tracking, and honest evaluation. Without leadership buy-in and willingness to adapt the process, OKRs become bureaucratic theater rather than genuine goal-setting.
  • Overloading with too many objectives: The power of OKRs comes from focus. Organizations that create 15-20 objectives per quarter diffuse energy and attention. Three to five well-chosen objectives create genuine prioritization.

​
Common Misconceptions

KPIs (Key Performance Indicators) are ongoing metrics that measure business health, while OKRs are time-bound goals for a specific period. KPIs answer “how are we performing?” while OKRs answer “where are we going and how will we know we arrived?” A healthy organization has both—KPIs for ongoing monitoring and OKRs for directional focus.
Tying OKRs directly to bonuses or performance reviews creates risk-averse behavior where employees set easy goals to guarantee reward. The original intent of OKRs was to encourage ambitious goal-setting, which requires psychological safety to fail. Keep OKRs and compensation separate for maximum benefit.
The optimal completion rate for OKRs is typically 60-70%. Achieving 100% suggests goals were too easy; consistently falling short suggests goals are unrealistic. This “Goldilocks zone” encourages stretch thinking while maintaining motivation.
OKRs connect deeply to other management and goal-setting methodologies. KPI (Key Performance Indicator) provides the ongoing metrics that inform OKR progress. Eisenhower Matrix helps prioritize which objectives matter most. For understanding organizational alignment, OKR relates to PDCA Cycle in their iterative approach to goal achievement. The concept of Regret Minimization provides a philosophical framework for setting ambitious objectives.

KPI

Ongoing metrics for measuring business performance

Eisenhower Matrix

Priority-setting framework for urgent vs important

PDCA Cycle

Iterative improvement framework

​
One-Line Takeaway

Use OKRs to create focus and alignment—set ambitious, inspirational objectives and define measurable key results that tell you whether you’re actually making progress toward your goals.