Execution

OKRs (Objectives and Key Results)

OKRs are a goal-setting framework in which qualitative Objectives (what you want to achieve) are paired with measurable Key Results (how you know you achieved it). The framework creates alignment by making priorities and progress visible across teams and levels.

Also known as: objectives and key results, goal-setting framework

Why It Matters

Most organizations have goals. Few have a system for connecting daily work to those goals. OKRs solve this by creating a structured link between ambitious direction (the Objective) and measurable evidence of progress (the Key Results). When implemented well, OKRs answer two questions for every person on the team: what matters most right now, and how will we know if we are making progress?

How It Works

An Objective is qualitative, inspiring, and time-bound (typically quarterly). It describes the outcome you want, not the activities you will perform. Key Results are quantitative, specific, and verifiable. Each Objective typically has two to five Key Results. The discipline of writing measurable Key Results forces teams to move beyond vague aspirations ("improve customer satisfaction") toward concrete targets ("increase NPS from 32 to 45 by end of Q2").

Origin and Adoption

The framework was created by Andy Grove at Intel in the 1970s and popularized by John Doerr, who introduced it to Google in 1999. Doerr's 2018 book "Measure What Matters" brought the methodology to a broader business audience. Today OKRs are used by organizations ranging from startups to the Gates Foundation, though implementation quality varies widely.

Why They Fail

OKRs fail most often for three reasons. First, teams write Key Results that are actually task lists ("launch the new website") rather than measurable outcomes ("increase conversion rate from 2.1% to 3.5%"). Second, organizations set too many OKRs, which defeats the purpose of focus. Third, OKRs are written at the start of the quarter and never revisited, turning them into shelf documents rather than working alignment tools.

  • Limit to three to five Objectives per team per quarter
  • Key Results must be measurable: if you cannot put a number on it, rewrite it
  • Review OKRs weekly or biweekly, not just at quarter boundaries
  • Separate OKRs (stretch goals) from committed deliverables to avoid sandbagging
  • Use OKRs to drive focus, not to catalog everything the team is doing