OKR stands for Objectives and Key Results. It's a goal-setting framework that pairs an ambitious qualitative goal (the Objective) with 3–5 measurable outcomes (Key Results) that prove you achieved it. Created at Intel in the 1970s and made famous by Google, OKRs are used today by Microsoft, Spotify, LinkedIn, Adobe, and thousands of growing companies to align teams around what matters most each quarter.
TL;DR
Every OKR has two parts that work together. The Objective gives the team a direction worth fighting for. The Key Results make progress unambiguous — you either hit the number or you didn't.
A qualitative, ambitious, time-bound statement of what you want to achieve. It should be memorable, inspiring, and meaningful enough that a new hire could quote it. Good Objectives describe a future state — not a task list.
Example
"Become the default OKR platform for Series A–C SaaS companies."
3–5 quantitative outcomes that prove the Objective was achieved. Each one needs a number, a baseline, and a target. If you can't put a metric on it, it's an initiative, not a Key Result.
Example
The same framework adapts to every function. Here's what good quarterly OKRs look like for the four teams that adopt them first.
Sales
Product
Marketing
People & Ops
The single biggest source of OKR confusion. KPIs are health metrics — they describe the ongoing state of a function. OKRs are change metrics — they describe what you're trying to move this cycle. You need both, and they're not interchangeable.
| Dimension | KPI | OKR |
|---|---|---|
| Purpose | Monitor health | Drive change |
| Time horizon | Continuous | Quarterly / annual |
| Ambition | Stable target | Stretch — aim for 0.7 |
| Example | Monthly churn < 2% | Reduce churn from 3.4% → 1.8% |
'Launch v2' is not a Key Result — it's a project. A Key Result is the measurable outcome that v2 was supposed to drive (activation rate, retention, revenue).
More than 5 Objectives or more than 5 KRs per Objective and focus evaporates. If everything is a priority, nothing is. Fewer, sharper OKRs always win.
The moment OKRs decide compensation, teams sandbag. They set the safest targets they know they can hit. You lose ambition, transparency, and the willingness to admit a miss.
OKRs aren't a Q1 ceremony. They need weekly or biweekly check-ins with honest confidence scores. Without rhythm, they become decorative.
Pure top-down OKRs ignore the people closest to the work. The best systems mix top-down direction with bottom-up KR proposals — usually a 60/40 split.
OKR stands for Objectives and Key Results. The Objective is the qualitative goal — what you want to achieve. Key Results are the 3–5 measurable outcomes that prove you got there.
Andy Grove created OKRs at Intel in the 1970s, evolving Peter Drucker's Management by Objectives (MBO). John Doerr learned the system at Intel and introduced it to Google in 1999, where it became foundational to the company's operating model.
KPIs are health metrics — they measure the ongoing performance of a function (e.g., monthly churn, NPS, uptime). OKRs are change metrics — they describe what you want to move in a specific quarter or year. KPIs tell you if the business is healthy; OKRs tell you what you're trying to improve.
Most high-performing teams set 3–5 Objectives per cycle, each with 3–5 Key Results. More than that and focus collapses. If everything is a priority, nothing is.
No. Andy Grove and John Doerr both explicitly warn against this. The moment OKRs determine bonuses, teams sandbag — they set safe, easy targets they know they'll hit. OKRs work best when they're ambitious, transparent, and decoupled from pay.
Score each Key Result from 0.0 to 1.0 at the end of the cycle. 0.7 is considered a successful outcome for a stretch goal — hitting 1.0 on everything usually means the targets weren't ambitious enough.
Ordo AI drafts your first set of OKRs from your strategy in minutes, runs the weekly check-in rhythm for you, and surfaces the at-risk Key Results before they slip.