OKR (Objectives and Key Results)

What OKR Means

OKR stands for Objectives and Key Results. An Objective describes what you want to achieve in qualitative, inspiring terms. Key Results describe how you will measure whether you achieved it, using 3 to 5 specific, quantifiable metrics. Together, an Objective and its Key Results form a single OKR.

Example OKR: Objective: Become the most trusted voice in project management education. Key Results: (1) Increase organic traffic from 30,000 to 75,000 monthly visitors. (2) Achieve a domain rating of 50 or higher. (3) Earn backlinks from 10 industry publications. (4) Reach 500 newsletter subscribers.

The Objective is aspirational and qualitative. You cannot directly measure “most trusted voice.” The Key Results are concrete and quantifiable. You can measure traffic, domain rating, backlinks, and subscribers. If you hit 3 of 4 Key Results, you have strong evidence you are making progress toward the Objective.

How OKRs Work

OKRs operate on a quarterly cycle at most organizations, though some teams use monthly or biannual cadences. The process follows four phases.

Setting: At the start of each quarter, teams define 3 to 5 Objectives with 3 to 5 Key Results each. Setting happens collaboratively: leadership proposes company level OKRs, then teams align their OKRs to support them. The cascade is not top down dictation. It is a negotiation where teams have autonomy over how they contribute to company goals.

Alignment: Once OKRs are set, teams check for dependencies and conflicts. If the engineering team’s OKR depends on the design team delivering mockups by week 4, that dependency needs to be explicit and agreed upon. Alignment prevents the common failure where every team hits their OKRs but the company misses its goals because the pieces did not fit together.

Tracking: Key Results are scored weekly or biweekly on a 0.0 to 1.0 scale. A score of 0.0 means no progress. A score of 1.0 means the Key Result was fully achieved. A score of 0.7 is considered a strong result in the OKR philosophy because Objectives should be ambitious enough that perfect scores indicate the target was too easy.

Retrospective: At the end of the quarter, teams review their OKR scores, discuss what drove the results, and identify lessons for the next cycle. Key Results that scored below 0.3 need root cause analysis. Key Results that scored 1.0 consistently may indicate the team is sandbagging.

The Origin of OKRs

Andy Grove, CEO of Intel, developed OKRs in the 1970s as an evolution of Peter Drucker’s Management by Objectives. Grove wanted a framework that preserved the alignment benefits of MBO while encouraging the ambition and speed that the semiconductor industry demanded.

John Doerr, a venture capitalist at Kleiner Perkins, learned OKRs from Grove at Intel and introduced them to Google in 1999 when the company had just 40 employees. Google adopted OKRs as a core management practice and still uses them today with over 180,000 employees. Doerr’s 2018 book Measure What Matters brought OKRs to mainstream business audiences.

Since then, OKRs have been adopted by LinkedIn, Twitter, Spotify, Samsung, and thousands of startups and enterprises. The framework’s popularity grew because it solved a problem that scales: as organizations grow, individual teams lose sight of how their work connects to company goals. OKRs make that connection explicit.

How to Write Good OKRs

Good Objectives are qualitative, inspiring, and time bound (usually one quarter). They should make your team feel challenged but not defeated. “Launch a world class onboarding experience” is a good Objective. “Increase onboarding completion rate by 5%” is a Key Result pretending to be an Objective.

Good Key Results are quantitative, unambiguous, and verifiable. Each Key Result should include a metric, a starting value, and a target value. “Reduce average onboarding time from 14 days to 7 days” is a good Key Result because anyone can verify whether it was achieved. “Improve the onboarding process” is not a Key Result because it cannot be objectively scored.

Limit yourself to 3 to 5 Objectives per quarter and 3 to 5 Key Results per Objective. More than that dilutes focus. If everything is a priority, nothing is. The discipline of choosing forces you to decide what truly matters this quarter and what can wait.

At least one Key Result per Objective should be a “stretch” that is only achievable with exceptional effort or creative problem solving. This prevents the natural tendency to set targets you already know you can hit. The discomfort of ambitious targets is a feature of OKRs, not a bug.

OKRs for Different Team Sizes

For individuals, OKRs may feel like overhead. A solo contributor with clear deliverables often does better with 3 SMART goals per quarter than with the full OKR apparatus. OKRs shine when multiple people need to coordinate.

For teams of 5 to 15 people, OKRs provide shared direction without micromanaging individual tasks. The team agrees on 3 to 4 Objectives and individuals choose the tasks and projects that will move the Key Results. This preserves autonomy while ensuring alignment.

For organizations of 50 or more people, OKRs become a communication tool as much as a planning tool. When every team’s OKRs are visible to the whole company, anyone can see how their work connects to the organization’s priorities. Transparency reduces duplicate work, reveals dependencies, and makes resource allocation decisions clearer.

For remote and distributed teams, OKRs compensate for the loss of informal alignment that happens naturally in an office. When you cannot walk by someone’s desk and see what they are working on, shared OKRs provide that visibility digitally.

Common OKR Mistakes

The most common mistake is writing Key Results as tasks instead of outcomes. “Launch the redesigned homepage” is a task. “Increase homepage conversion rate from 2.1% to 3.5%” is an outcome. OKRs measure results, not activities. You can launch a homepage and still fail if it does not improve the metric that matters.

Second: setting too many OKRs. Organizations new to OKRs often set 8 to 10 Objectives per team, which fragments focus and makes weekly scoring burdensome. Three to four Objectives per team is the ceiling.

Third: linking OKRs directly to compensation. When OKR scores determine bonuses, teams set conservative targets to guarantee high scores. This defeats the stretch goal philosophy. Google explicitly separates OKR scoring from performance reviews and compensation decisions.

Fourth: skipping the weekly check in. OKRs that are set in January and reviewed in March produce surprises, not results. A 15 minute weekly check in where each Key Result gets a score and a one sentence status update keeps the system alive and catches problems early.

Fifth: treating OKRs as top down mandates. The cascade should be bidirectional. Leadership sets direction. Teams propose how they will contribute. If all OKRs flow downward without team input, you have Management by Objectives with a new label, not OKRs.