OKRs (Objectives and Key Results)
Updated July 21, 2026
Goal-setting framework for translating competitive strategy into execution: qualitative Objectives with quantitative Key Results.
Also known as: Objectives and Key Results, OKR framework, OKR methodology
OKRs, short for Objectives and Key Results, is a goal-setting framework that pairs a qualitative, aspirational Objective, a plain statement of what a team wants to achieve, with a small set of quantitative Key Results, typically three to five, that define exactly what achieving it looks like. The Objective supplies direction and meaning; the Key Results supply the measurable evidence. Practitioners often phrase the pairing as "I will (Objective) as measured by (Key Results)." The value of the structure is that it forces a team to state a goal in words everyone understands and then commit to numbers that will settle, at the end of the period, whether the goal was met.
The framework was developed by Andy Grove at Intel in the 1970s, where his internal version was called iMBOs, or Intel Management by Objectives: an evolution of Peter Drucker's Management by Objectives concept from the 1950s. Grove documented the approach in his 1983 book High Output Management. John Doerr, who took Grove's internal course as an Intel salesman in 1975, is credited with coining the term OKRs and later, as a venture capitalist at Kleiner Perkins, introduced the framework to Google's founders in 1999. Google has run OKRs on a quarterly cadence ever since, scaling the practice from roughly forty employees to well over a hundred thousand. Doerr's 2018 book Measure What Matters is widely credited with carrying OKRs into the broader startup and technology world. Today they are used across product, marketing, sales, and competitive-intelligence teams as a common language for turning strategy into accountable execution.
How an OKR is structured
An OKR has two parts that do different jobs. The Objective is a single qualitative, concrete, and deliberately ambitious statement of intent, memorable enough that a team can recite it without checking a document. It carries no numbers of its own. Beneath it sit the Key Results, usually three to five specific, measurable, time-bound outcomes that together prove the Objective was reached. If every Key Result is met and the Objective still does not feel accomplished, the Key Results were the wrong ones.
Many teams, following Google's model, score each Key Result on a 0.0 to 1.0 scale at the end of the cycle. For intentionally ambitious stretch objectives, a final score of 0.6 to 0.7 is treated as healthy rather than a failure, because a team that hits 1.0 on everything was probably not aiming high enough. More conservative committed goals are expected to land at 1.0. Two other conventions distinguish OKRs from older goal systems: they are meant to be transparent across the organization, and they are decoupled from individual compensation, so people can set stretch targets without risking their pay.
OKRs vs. KPIs
OKRs and KPIs are frequently confused because both involve metrics, but they answer different questions. A KPI, or key performance indicator, is an ongoing operational measure that monitors business-as-usual health: uptime, churn rate, pipeline coverage, response time. It runs continuously and has no built-in endpoint. A Key Result, by contrast, is a specific target chosen for a defined period and attached to a particular Objective the team has decided to prioritize this cycle.
The two interlock rather than compete. KPIs often become the raw material for Key Results: a standing churn KPI of 4 percent might become the Key Result "reduce churn from 4 percent to 2.5 percent this quarter." But not every KPI belongs in an OKR. Most should stay in the background as health metrics, and not every Key Result survives as a standing KPI once its cycle ends. A useful test is whether the number represents a deliberate push toward a chosen goal, which is a Key Result, or a gauge you would watch regardless of strategy, which is a KPI.
How competitive-intelligence teams use OKRs
OKRs give a competitive-intelligence program a way to convert raw findings into accountable action rather than open-ended monitoring. A CI-relevant Objective states a qualitative competitive aim (closing a pricing perception gap against a named rival, or winning more head-to-head deals against a specific competitor), while the Key Results attach concrete targets such as increasing win rate against that competitor from 30 percent to 45 percent, publishing battlecards for the top four rivals, or cutting time-to-alert on competitor pricing changes to under 24 hours.
Structured this way, OKRs keep a CI function from drifting into unfocused data collection. The Objectives set intelligence priorities (tracking a rival's roadmap, watching pricing moves), and the Key Results quantify success through metrics like win rate, retention, or influenced revenue. The quarterly review cadence then forces the team to demonstrate measurable business impact rather than simply report what it has observed. Continuous monitoring of competitor websites, pricing pages, and job postings supplies the evidence that both sets these targets and tells the team, mid-cycle, whether it is on track.
Common mistakes and limitations
The most common failure is writing Key Results that are really tasks. "Launch the new pricing page" is an activity, not an outcome; a proper Key Result measures the effect the launch was supposed to produce. A second failure is stuffing an Objective with too many Key Results, which dilutes focus and usually signals that the team has not decided what actually matters this quarter. Setting stretch targets while still tying them to individual bonuses is a third: it quietly pushes people to sandbag, which defeats the point of ambitious goals.
OKRs also have boundaries. They set direction and measure progress, but they do not tell a team how to win: knowing you must lift win rate against a competitor says nothing about the messaging or product work required to do it. Their short cycles make them a tactical execution layer, weakest as a long-range planning instrument, which is why they often sit beneath a longer-horizon framework rather than replacing one.
Stop looking terms up. Start tracking them.
meertrack watches your competitors' websites, pricing, and hiring, then alerts you when something meaningful changes.
Frequently Asked Questions
What does OKR stand for?
OKR stands for Objectives and Key Results. The Objective is a qualitative, ambitious statement of what a team wants to accomplish, and the Key Results are a small set of quantitative, time-bound measures, usually three to five, that define what success looks like. The two are often written in the form "I will achieve this Objective as measured by these Key Results," so intent and evidence sit side by side.
Who invented OKRs?
OKRs trace back to Andy Grove, who built the approach while running Intel in the 1970s and labeled his in-house version iMBOs, short for Intel Management by Objectives, itself an outgrowth of Peter Drucker's earlier Management by Objectives idea. John Doerr, who picked it up from Grove as an Intel salesman in 1975, is the one who named the OKR acronym and later brought the method to Google in 1999 from his seat at Kleiner Perkins. His 2018 book Measure What Matters carried it to a mass audience.
How many key results should an objective have?
Most practitioners aim for three to five Key Results per Objective. Fewer than three often means the Objective is not fully defined; more than five usually signals a lack of focus or that tasks are being listed instead of outcomes. Each Key Result should be specific, measurable, and time-bound, and together they should be sufficient: if you hit all of them, the Objective should genuinely be accomplished.
Are OKRs the same as MBOs?
No, though OKRs evolved from Management by Objectives. MBO, from Peter Drucker in the 1950s, is typically top-down, tied to individual performance appraisal and compensation, and reviewed on annual cycles. OKRs, Grove's adaptation at Intel, are meant to be transparent across the organization, decoupled from individual pay so teams can set stretch targets, and reviewed on short cycles, most commonly quarterly.
What is a good OKR score?
When Key Results are scored on a 0.0 to 1.0 scale, the interpretation depends on the goal type. For intentionally ambitious stretch objectives, a score of 0.6 to 0.7 is considered healthy, because consistently hitting 1.0 suggests the targets were set too low. Committed goals that the team fully expects to deliver are instead expected to reach 1.0. The scoring is meant to prompt reflection, not to grade individuals.
Related terms
Quantifiable metrics for evaluating performance. In CI: win rate, displacement rate, intelligence utilization rate.
Balanced ScorecardFramework measuring performance across financial, customer, internal process, and learning/growth perspectives.
Strategic IntentAn ambitious, long-term competitive aspiration that stretches beyond current resources (Hamel & Prahalad).
Competitive Win RateWin rate broken down by specific competitor, showing how often you beat each rival.
CI ProgramA formally resourced initiative dedicated to gathering and distributing competitive insights across the organization.
Actionable IntelligenceInformation processed, analyzed, and contextualized to the point where it can directly inform a specific business decision, as opposed to raw data or general awareness.
Mobility BarriersFactors making it difficult for firms to move between strategic groups (e.g., from budget tier to premium tier).
Second-Order SignalA competitive insight derived from inference rather than direct observation, e.g., a CS hiring surge may signal churn problems, not growth.