OKR (Objectives and Key Results)
Set ambitious objectives, measure them by key results. Andy Grove's OKR method, popularized by Google, to align the entire organization.
Description
The OKR method (Objectives and Key Results) is a collaborative goal-setting framework created by Andy Grove at Intel in the 1970s and popularized by John Doerr at Google in 1999, which aligns teams around ambitious qualitative objectives measured by quantifiable key results. Its purpose: to turn strategy into measurable actions at every level of the organization. Andy Grove laid out the principle in High Output Management (1983): "Where do I want to go? The answer provides the Objective. How will I pace myself to see if I'm getting there? The answer gives us Key Results." An Objective is a qualitative, ambitious, and inspiring direction ("Become the market reference for SaaS onboarding"). Key Results (2 to 5 per objective) are the measurable evidence that you are moving in the right direction ("Reduce time-to-value from 14 days to 3 days," "Reach an onboarding NPS of 60"). The OKR method works like a hiking GPS: the Objective is the summit you are aiming for, the Key Results are the checkpoints confirming you are on the right trail. John Doerr introduced OKRs at Google in 1999, when the company had 40 employees. He distilled them into "four superpowers": Focus (concentrate on what matters), Alignment (connect teams), Tracking (monitor progress), and Stretching (aim high). At Google, an OKR score between 0.6 and 0.7 out of 1.0 is considered a success. Reaching 100% means the objectives were not ambitious enough. This stretch-goal philosophy is what sets OKRs apart from traditional KPIs: KPIs measure current operational performance (where are we), while OKRs set an ambitious direction for change (where do we want to go). His book Measure What Matters (2018) systematized the method and triggered its worldwide adoption beyond Silicon Valley.
Objectives
- Define the vision
- Measure success
- Improve team collaboration
- Ensure strategic alignment
Used by
- -Google (adopted OKRs in 1999 with 40 employees, still uses them today with over 140,000 team members)
- -LinkedIn (uses OKRs to align its product teams on growth and engagement objectives)
- -Intel (company of origin where Andy Grove created the OKR method in the 1970s)
Advantages
- Strategic alignment at all levels. From CEO to developer, everyone can trace the link between their daily work and company strategy.
- Focus on results, not deliverables. OKRs force measuring impact (outcome) rather than production (output), which fundamentally changes product culture.
- Calibrated ambition. The stretch goal philosophy (aiming for 0.7 out of 1.0) pushes teams beyond their comfort zone without paralyzing them.
- Organizational transparency. When all OKRs are public, silos disappear and cross-team dependencies become visible.
Limitations
- 2-3 quarter learning curve. The first OKRs are almost always poorly formulated (vague KRs, too many Objectives). Accept initial imperfection.
- Risk of bureaucracy. If OKRs become a quarterly administrative exercise disconnected from real work, they lose all value. Regular check-ins are essential.
- Frequent OKR/KPI confusion. Teams often confuse Key Results (direction of change) and KPIs (current health indicators). A stable KPI does not need to be an OKR.
- Does not work without leadership sponsorship. If the CEO does not create their own OKRs and share them, nobody will take the system seriously.
How to apply OKR (Objectives and Key Results)
- 1
Define Objectives at the company level
The leadership team formulates 3-5 Objectives for the quarter. Each Objective must be qualitative, inspiring, and outcome-oriented. "Increase revenue" is not a good Objective (that is a KPI). "Become essential for product teams in Europe" is one. A good test: if the Objective does not generate enthusiasm when you read it aloud, it is too weak. Output: 3-5 quarterly Objectives validated by the executive committee.
- 2
Define 2-5 Key Results per Objective
For each Objective, identify the measurable results that will prove progress. Format: "[Metric] from [baseline] to [target]". Example: "NPS from 32 to 50", "M3 retention rate from 40% to 55%". Key Results must be outcomes (results), not outputs (deliverables). "Launch feature X" is not a Key Result, it is an initiative. "Increase adoption of feature X to 30% of active users" is one. Output: 2-5 measurable Key Results per Objective.
- 3
Cascade OKRs to teams
Each team defines its own OKRs aligned with company OKRs. Alignment happens through Key Results: a company KR can become a team's Objective. Example: if the company KR is "Increase M3 retention from 40% to 55%", the onboarding team can have the Objective "Transform the first 7 days experience". Let teams define their own KRs to foster ownership. Output: team OKRs aligned with company OKRs.
- 4
Publish all OKRs transparently
OKRs for each team and each individual must be visible to everyone. This transparency is non-negotiable. It allows each person to understand how their work contributes to the overall strategy and to identify cross-team dependencies. Use a dedicated tool (Notion, Lattice, Weekdone) or a simple shared Google Sheet. Output: an OKR dashboard accessible to the entire organization.
- 5
Plan the Initiatives that support Key Results
For each Key Result, identify 2-3 concrete initiatives (projects, experiments, tasks) that will contribute to achieving it. This is the link between strategy and daily work. Without initiatives, OKRs remain wishful thinking. With too many initiatives, you spread too thin. Output: 2-3 initiatives per Key Result with assigned owner.
- 6
Run weekly or bi-weekly check-ins
Every week or every two weeks, spend 15 minutes as a team evaluating the progress of each Key Result. Use a simple color code: green (on track), yellow (at risk), red (behind). If a KR is red for 3 consecutive weeks, that is a warning signal: change your approach, add resources, or accept that this OKR will not be achieved. Output: documented check-in with status per KR.
- 7
Score the OKRs at the end of the quarter
Evaluate each Key Result on a scale from 0 to 1.0. At Google, 0.6-0.7 is a good score (you aimed high and made significant progress). A score of 1.0 every time means your objectives are not ambitious enough. A score of 0.3 means something did not work. Analyze the causes, not to blame but to learn. Output: quarterly OKR scorecard with gap analysis.
- 8
Iterate for the next quarter
OKRs are a muscle that develops over time. The first quarter will be imperfect: too many OKRs, poorly worded Key Results, inconsistent scoring. That is normal. Keep unmet Objectives if they remain relevant. Adjust Key Results. Add new Objectives if context changes. After 3-4 quarters, your team will master the rhythm. Output: next quarter's OKRs incorporating lessons learned.