OKR (Objectives and Key Results)
OKR (Objectives and Key Results) is a goal-setting framework where teams define concise objectives and measure progress through a small set of quantifiable key results, reviewed quarterly (bib).
Structure
An OKR consists of two parts:
- Objective — what you want to achieve. Concise and engaging, framed as an outcome rather than an activity.
- Key Results — how you measure achievement. A small number of metrics with clear targets, measurable on a timely basis.
John Doerr’s formula: “I will ________ as measured by ____________.”
Lineage
OKR refines Peter Drucker’s Management by Objectives (MBO, 1954). The shift: MBO was top-down (manager reviews organizational goals, sets worker’s objectives), OKR is collaborative (teams refine high-level objectives for their area). Popularized at Intel in the 1970s by Andy Grove, spread to Google and the broader tech industry by Doerr.
Three types
- Committed — non-negotiable, must be achieved.
- Aspirational — stretch goals; scoring 0.7 on a 0–1 scale counts as success.
- Learning — focused on experimentation and discovery. Parallels the learning goals distinction in goal-setting research.
OKR as a feedback loop
From a control theory perspective, OKR is a closed-loop system with a quarterly sampling rate: the objective is the reference signal, key results are the sensor output, the quarterly review is the comparator, and team action is the effector.
The user’s xettel frames this as a thermostat that checks once a season — functional, but slow. Compared to Scrum (sprint-length loops) or Kanban (continuous flow), OKR operates at the lowest frequency in the management feedback spectrum.
Connection to goal-setting theory
OKR is an organizational implementation of goal-setting theory. The parallels are direct:
- Specific, difficult goals → OKR requires concrete objectives with measurable targets, scored so that 0.7 = success (i.e., targets are deliberately set above comfortable attainment).
- Feedback → quarterly review provides the comparison between goal and actual state.
- Goal commitment → collaborative goal-setting enhances strategy formulation (consistent with Locke & Latham’s finding that participation’s benefit is cognitive, not motivational).
- Discrepancy production → aspirational OKRs deliberately create a gap the team cannot fully close, echoing Bandura’s discrepancy production model.
See also
- Atlassian OKR Guide — source summary
- 2039585611682918581 — OKR: 90-day feedback loop
- 2039585794495803405 — OKR as a thermostat that checks once a season