OKRs: The Ultimate Guide (Atlassian)

source
okrgoal-settingmanagementagile

A practitioner guide by Rich Sparks (Atlassian) covering OKRs — Objectives and Key Results (bib).

Key content

Definition: “I will ________ as measured by ____________” (John Doerr). An OKR combines a concise, engaging objective with a small number of measurable key results, reviewed on a quarterly cadence.

Origins: OKRs refine Peter Drucker’s Management by Objectives (MBO). Where MBO was top-down and bureaucratic, OKRs are collaborative — teams take high-level objectives and refine them for their area. Popularized at Intel in the 1970s, spread through tech via Doerr.

Three types: committed (must be achieved), aspirational (stretch goals), and learning (experimentation and discovery). The learning type parallels the learning vs performance goals distinction in goal-setting research.

Scoring: 0–1 scale. 0.7 = success. Consistently scoring 1.0 suggests targets are not ambitious enough. This deliberately sets the bar above comfortable attainment — echoing goal-setting theory’s finding that difficult goals outperform easy ones.

Process over artifact: The article emphasizes that the OKR process (regular review, revision, realignment) matters more than the goal document itself. “Static goals that aren’t regularly reviewed and revised as the operating environment changes quickly become stale and meaningless.”

Connection to the knowledge base

The user’s xettel frames OKR as a 90-day feedback loop and a thermostat that checks once a season. The Atlassian guide confirms this: quarterly review is the recommended cadence. From a feedback control perspective, OKR is a closed loop with a very low sampling rate — the comparator fires once per quarter.

The guide’s emphasis on “did we achieve the objectives?” over “did we deliver the things we said we’d deliver?” maps to the distinction between outcome goals and output goals — a theme that connects to learning vs performance goals.

See also