Objectives and Key Results (OKR)

Objectives and Key Results, or OKR, is a way of writing goals so that ambition and evidence live in the same place. The Objective is a short, qualitative statement of what you want to achieve — memorable, inspiring, and deliberately a stretch, such as "become the default tool teams reach for." The Key Results are the three to five measurable outcomes that would prove the objective is being met — concrete numbers like "raise weekly active teams from 4,000 to 7,000" or "cut time-to-first-value below ten minutes." The objective says where you are going; the key results say how you will know you arrived. Andy Grove developed the approach at Intel, and John Doerr carried it to Google early in the company's life, after which it spread across the technology industry and beyond. The format is intentionally spare so a whole organization can read, remember, and rally around it.

OKRs do two jobs at once: they align and they focus. Alignment comes from making goals public and connected — a team's OKRs visibly support the company's, so everyone can see how their work ladders up. Focus comes from the cap: a handful of objectives, each with a few key results, forces a team to choose what matters most rather than list everything it could do. Crucially, key results measure outcomes, not effort — "reduce churn to 3%," not "ship the retention feature." Shipping the feature is a task; the churn number is the result the task is supposed to produce. That distinction is what keeps OKRs honest. A team can complete every task on its list and still miss the key result, which is exactly the signal an OKR is built to surface.

OKRs are often confused with KPIs, but they answer different questions. A Key Performance Indicator is an ongoing health metric you monitor continuously — monthly revenue, support response time, uptime — a number you want to keep in a good range indefinitely. An OKR is time-boxed and directional: it names a change you want to drive this quarter and the results that prove it. KPIs tell you whether the engine is running; OKRs tell you where you are trying to steer it. The two coexist: a KPI that has drifted out of range often becomes the seed of a quarterly OKR aimed at fixing it. Treating every KPI as an OKR buries a team in goals; treating an OKR as just another dashboard metric drains it of its stretch and direction.

OKRs also differ from SMART goals in their relationship to ambition. SMART goals prize being Achievable and Realistic — you should expect to hit them. Many OKR practitioners, following the Google tradition, deliberately set "stretch" key results where landing around 70% is considered a strong result, because aiming only for the safely achievable caps how far a team will reach. That stretch convention is a choice, not a rule, and it has a sharp edge: stretch OKRs must never be tied to compensation or used as a performance club, or people will sandbag their targets to protect their bonuses, defeating the purpose. The healthiest practice keeps grading honest and low-stakes, treats a miss as information, and resets each cycle. OKRs are a focusing and learning tool first, an accountability ritual second.

Used well, OKRs are few and outcome-based. Limit a team to a small number of objectives, each with three to five key results, and make those key results measurable outcomes rather than to-do lists — the test is whether you could complete all your planned work and still miss the result. Run them on a rhythm, usually quarterly, with a check-in cadence so they steer the work instead of gathering dust until review day. Connect them up and down so individual and team goals visibly serve the company's, which is where the alignment payoff comes from. Grade them openly, learn from the misses, and reset. The discipline is choosing what matters and measuring whether you achieved it — not cataloging activity and calling it a goal.

The failures are well documented. Teams write too many OKRs, so nothing is truly a priority. They confuse output for outcome, listing features to ship as key results, then declare victory on shipping while the number that mattered never moved. They set OKRs and forget them until the quarter ends. They tie stretch goals to pay, so people lowball targets to stay safe. And they let KPIs and OKRs blur until the framework is just a renamed dashboard. The remedy each time is the same: keep them few, make key results measure results, review them on a cadence, keep grading honest and separate from compensation, and reserve OKRs for the changes you want to drive rather than the metrics you merely watch.

Objectives and Key Results (OKR) — an ambitious objective paired with measurable key results — was developed by Andy Grove at Intel and spread by John Doerr at Google as a focusing and alignment framework.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where objectives and key results (okr) is a core concern: