OKRs attract a consistent set of questions — some about basic mechanics, some about the edge cases, and some about the gap between how the framework is described and how it works in practice. This FAQ answers the 25 most common ones, with source references where the evidence is clear and honest hedging where it isn’t.
Origins and Basics
What does OKR stand for?
Objectives and Key Results. An Objective is a qualitative statement of direction — where the team is trying to go. A Key Result is a quantitative measure that answers how you’ll know you got there.
Who invented OKRs?
Andy Grove developed the framework at Intel in the 1970s, building on Peter Drucker’s Management by Objectives (MBO). Grove called it iMBO internally. John Doerr, who interned at Intel and learned the system firsthand, brought it to Google in 1999 and popularized it significantly through his 2018 book Measure What Matters.
Why did John Doerr bring OKRs to Google?
When Doerr invested in Google as a Kleiner Perkins partner, the company had approximately 40 employees and no formal goal management system. Doerr presented the OKR framework in a PowerPoint deck in 1999. Larry Page and Sergey Brin adopted it provisionally. It has been in continuous use at Google since.
How are OKRs different from KPIs?
KPIs (Key Performance Indicators) track ongoing operational health — whether a business is running normally. OKRs track directional change — whether a team is making progress toward a new, better state. A mature organization needs both: KPIs to confirm the business is healthy, OKRs to confirm it is improving. Treating OKRs as KPIs is one of the most common failure modes.
How are OKRs different from SMART goals?
SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) are designed to be fully achievable. Aspirational OKRs are deliberately designed to be partially achievable — the expected completion rate is 60–70%, not 100%. This reflects a different philosophy: SMART goals value reliability, aspirational OKRs value ambition.
Structure and Writing
What makes an Objective well-written?
A well-written Objective is qualitative, inspiring, time-bound, and short enough to memorize. It should function as a decision filter — a team member facing a choice between two projects should be able to use the Objective to identify which one to prioritize. It should not contain numbers (those belong in Key Results).
What is the test for a good Key Result?
The most reliable test, from Doerr: does the Key Result require a number to verify? If you can answer “did we achieve it?” with a yes/no rather than a measurement, it’s an activity in disguise. Key Results should have a baseline (“from X”), a target (“to Y”), and a clear owner.
How many OKRs should a team have?
Grove’s recommendation: 3–5 Objectives, with 2–4 Key Results each. More than that and focus collapses into a task list. The discipline of choosing what goes on the list is where most of the strategic value is generated.
Can an Objective have only one Key Result?
Yes, though it is unusual. A single Key Result can adequately capture what success looks like for a focused Objective. The risk with a single KR is that it may represent only one dimension of success — you optimize the measured metric without achieving the Objective’s intent. Two or three KRs typically provide better coverage.
Should Key Results use the same unit of measurement?
No. Key Results within the same Objective can and often should measure different dimensions: a retention rate, a revenue figure, and an NPS score can all serve as Key Results for the same Objective. The diversity of measurement is what prevents narrowly gaming a single metric.
Scoring and Grading
What is a good OKR score?
For Aspirational OKRs: 0.6–0.75 is the success zone, per both Grove and Doerr. A score of 1.0 suggests the goal wasn’t ambitious enough. For Committed OKRs: 1.0 is the expected score. A 0.8 on a Committed OKR indicates something went wrong.
Why is 70% considered success?
The 70% norm for aspirational goals is designed to make ambitious goal-setting safe. If teams know that partial achievement is treated as success, they can set genuinely hard goals. If they know anything below 100% is treated as failure, they’ll set goals they know they can hit.
Should OKR scores affect performance reviews?
Both Grove and Doerr are explicit: no. Coupling OKR scores to compensation or performance ratings is the single most commonly cited cause of OKR programs becoming counterproductive. Once career consequences are attached to scores, people optimize for the score rather than the underlying outcome.
What do you do if you’ll clearly miss an OKR mid-cycle?
First, investigate whether the miss is due to execution gaps or factors outside the team’s control. Second, determine whether the goal should be revised (because circumstances have genuinely changed) or kept (because the miss is informative and the goal remains right). Change goals when the world changes, not when you’re behind.
Can you score above 1.0?
Some teams allow scores above 1.0 to acknowledge exceptional overperformance. Grove’s original framework didn’t include this, and Doerr’s implementation is ambivalent. The risk is that 1.1 scores on committed KRs become a target in themselves, which can encourage over-promising in subsequent cycles.
Team, Individual, and Company OKRs
Should every employee have individual OKRs?
Not necessarily. Individual OKRs work best for roles with clear output metrics. For many knowledge-work roles, forcing numeric Key Results produces metrics that measure the measurable rather than the meaningful. Many organizations use OKRs only at the company and team level and handle individual performance evaluation through other mechanisms.
How should team OKRs relate to company OKRs?
Team OKRs should represent the team’s specific contribution to company-level Objectives — not copies of the company OKRs. A product team and a sales team will have entirely different OKRs that both contribute to the same company Objective. Doerr recommends roughly 40% top-down alignment (team OKRs explicitly supporting company OKRs) and 60% bottom-up (team-initiated goals that the team believes are most important for advancing the strategy).
What is the right frequency for OKR cycles?
Quarterly is standard and works well for most organizations. Annual OKRs get stale; monthly can produce excessive administrative overhead. Some fast-moving teams use rolling monthly OKRs, adding and retiring goals as circumstances change. The key is that the cycle is short enough that feedback loops are meaningful.
Should leadership publish their own OKRs?
Yes. One of the most powerful features of Google’s implementation is that leadership OKRs are visible to everyone. When senior leadership exempts itself from the transparency that others are held to, teams interpret OKRs as an accountability mechanism pointing downward rather than a coordination mechanism pointing in all directions.
Common Questions and Edge Cases
What is the difference between a Committed and an Aspirational OKR?
Committed OKRs are operational commitments — the team is saying “we will deliver this.” Aspirational OKRs are strategic bets — the team is saying “this is our best shot at meaningful progress.” The 70% success norm applies only to Aspirational OKRs. Committed OKRs are expected to score 1.0.
Can you change OKRs mid-cycle?
Yes, when circumstances genuinely change — a competitor moves, a major customer churns, a product bet doesn’t pan out. The critical distinction is between changing a goal because the situation calls for it versus changing it to protect a score that’s trending low. Teams need a clear policy and the intellectual honesty to tell the difference.
What if a Key Result becomes irrelevant mid-cycle?
Close it with a note explaining what changed, then add a replacement Key Result that reflects the updated priority. Don’t just quietly stop tracking it — the lack of closure creates ambiguity about whether the goal was achieved, dropped, or simply forgotten.
What happens in the quarterly retrospective?
At the end of each cycle: score every Key Result, average to Objective scores, and run a retrospective focused on what drove the scores (execution gaps, favorable conditions, structural blockers, unclear ownership). The retrospective output is an input to next cycle’s planning. Teams that run rigorous retrospectives consistently improve their OKR quality and execution over time.
Is there an OKR framework for individuals, not just companies?
Yes, though it requires adaptation. The company and team levels of OKRs have clear precedents. The individual level is more challenging — many types of personal and professional work don’t decompose cleanly into quarterly numeric targets. For a full treatment of individual OKR adaptation, see The Complete Guide to OKRs for Individuals.
Can AI help with OKR planning?
Yes, at two stages specifically. First, drafting quality Key Results — AI can reliably catch activity-based Key Results and suggest outcome-based rewrites, which is one of the most common and impactful writing failures. Second, weekly check-in synthesis — AI can aggregate confidence scores and blocker reports across a team’s Key Results, surfacing patterns that would require manual compilation otherwise. For specific prompts, see 5 AI Prompts to Write Better OKRs.
Where to Go Next
If you are new to OKRs, the best starting point is Grove’s High Output Management, Part 2 — shorter and more honest than most current summaries. Doerr’s Measure What Matters provides richer case studies and is a better read if you want organizational examples.
If you are resetting a broken OKR implementation, start with Why OKRs Are Misused in Most Companies — it maps the specific failure modes and their fixes.
If you are ready to draft your next OKR set, start with How to Write OKRs That Actually Work and run the five AI prompts in 5 AI Prompts to Write Better OKRs before you publish.
Tags: OKR FAQ, OKR questions answered, objectives and key results, OKR basics, goal setting, Andy Grove, John Doerr, OKR framework
Frequently Asked Questions
-
What is the most important thing to understand about OKRs?
That Objectives are qualitative directions and Key Results are quantitative measures — and keeping them structurally separate is not formatting convention but the core behavioral mechanism of the framework. -
How long does it take to get OKRs working well in an organization?
Most practitioners report that OKRs begin producing meaningful alignment by the second or third cycle. The first cycle is typically diagnostic — it surfaces the writing problems and cadence failures that the second cycle can fix.