Definition

OKRs, or Objectives and Key Results, are a system for setting and tracking goals. Each OKR connects a qualitative objective, which describes the change to be achieved, with several quantitative key results that make progress verifiable over a defined period.

The system helps express priorities and observe outcomes, but it does not replace strategy, initiative planning, or daily management. A key result should measure a verifiable change, not merely list tasks, meetings, or deliverables.

Origin of OKRs

OKRs developed from the management by objectives system used at Intel under Andy Grove during the 1970s. Grove separated what had to be achieved from the measures used to determine whether it had been achieved.

John Doerr learned the method while working at Intel, named it Objectives and Key Results, and introduced it to the founders of Google in 1999. Google’s adoption helped spread it among technology companies and later among organizations in other sectors.

This history does not establish one mandatory implementation. Cadence, scoring, visibility, and the expected level of ambition vary among organizations, while the central relationship between an objective and observable results remains.

Components of an OKR

An OKR brings together distinct elements that need a causal relationship. Achieving the key results should provide reasonable evidence that the objective has advanced:

Objective: states a specific, understandable, and time-bound direction.
Key results: describe measurable outcomes with a starting value, target value, and calculation rule.
Initiatives: group the projects or actions intended to influence those outcomes, but do not measure achievement.
Owners: maintain the data, coordinate dependencies, and explain contextual changes.

A KPI and a key result may use the same metric, but they serve different purposes. A KPI continuously monitors an aspect of performance; a key result specifies the expected change in that measure within a particular objective and period.

The formulation needs a starting baseline. “Increase conversion” cannot be evaluated without an initial value, measurement scope, source, and target. A metrics baseline makes the start and end of the cycle comparable.

Working cycle

OKRs are often organized into cycles so teams can revisit priorities without turning every weekly variation into a new goal. The full cycle combines definition, tracking, and closure:

Definition: a small number of priorities are selected and measures, sources, and owners are agreed.
Alignment: dependencies and possible conflicts among company, team, and functional objectives are reviewed.
Tracking: key results are updated at a known frequency, with blockers and contextual changes documented.
Closure: achievement is calculated and its causes are examined without treating a score as a complete explanation.
Learning: the organization decides what to continue, reformulate, or remove in the next cycle.

A dashboard can support tracking when it retains the definition and provenance of each figure. A visual update does not by itself correct a poorly chosen metric, a measurement delay, or a conflicting objective.

Scoring may use percentages, a decimal scale, or categories, but it needs a stable rule. Partial achievement has a different meaning when the objective was deliberately aspirational than when it represented an operational commitment that had to be completed.

Organizational contribution

The system can improve conversations about priorities when the organization has an understandable strategy and access to consistent data. Its contribution depends on design quality, not on using the acronym:

Focus: limits the number of priority changes tracked during the cycle.
Transparency: shows what each team is pursuing and what evidence will be used to assess progress.
Coordination: exposes dependencies, incompatible objectives, and shared responsibilities.
Learning: compares hypotheses, initiatives, and outcomes to improve later decisions.

OKRs do not guarantee motivation, collaboration, or better decisions. If they are imposed without participation, changed continuously, or mechanically tied to individual incentives, they may encourage unrealistic goals, negotiation over figures, or the selection of measures that are easy to improve.

Examples of OKRs

The following are illustrative cases, not goals attributed to specific companies. They show how an objective connects to outcomes and how initiatives remain separate from measurement.

For an ecommerce business, the objective might be “provide a smoother purchase experience.” Key results could reduce cart abandonment from 68% to 60%, increase mobile payment completion from 72% to 80%, and cut monthly contacts about payment errors from 420 to 250. Redesigning the form would be an initiative, not a key result.

For a content team, the objective might be “increase the usefulness of the resource center.” Results could raise the share of sessions that consult a second guide from 35% to 50% and reduce internal searches with no results from 18% to 10%. Publishing ten articles only describes an activity; it does not demonstrate that the resource center is more useful.

For customer support, the objective might be “resolve inquiries with less waiting.” A coherent set would measure first-response time, first-contact resolution, and reopened cases, preventing a single metric from encouraging fast but incomplete replies.

Limitations of the system

Measurement can distort behavior when it becomes the purpose of the work. An easily counted result does not always represent the intended value, and a vanity metric may improve without changing customer experience or economic performance.

Problems also arise when there are too many OKRs, results have no owner, data arrives late, or dependencies lie outside the team’s control. Tracking should distinguish observed progress, attributable effects, and external circumstances, especially when several initiatives influence the same measure.

Closure is not just a matter of assigning a score. It should explain which hypothesis was supported, which data was insufficient, what the progress cost, and which unintended effects appeared. OKRs then operate as a framework for direction and learning, rather than as a task list or an automatic assessment of individuals.