Skip to content

[Anchor Proposal]: OKR (Objectives and Key Results) #635

Description

@rehsack

Proposed Term

OKR (Objectives and Key Results)

Context

A goal-setting framework that originated at Intel under Andy Grove ("iMBOs") and was popularised at Google and beyond by John Doerr (Measure What Matters, 2018). Each Objective (qualitative, ambitious, time-bound) is paired with 3–5 Key Results (quantitative, measurable outcomes). OKRs are typically set on a quarterly cadence, deliberately stretch ("ambitious"), are transparent across the org, and are kept decoupled from compensation to avoid gaming.

Fits strategic-planning; relatives in the catalog: hoshin-kanri, impact-mapping, kano-model, goodharts-law (cautionary — measuring KRs can become a target).

Sources: John Doerr, Measure What Matters (2018) · Andy Grove, High Output Management (1983).

LLM Activation Test Result

Model: Claude (Opus 4.8)
Prompt: "What concepts do you associate with 'OKR'?"
Response: Objective + Key Results; quarterly goal-setting; measurable, outcome-based key results; ambitious/stretch goals (~70% as "good"); transparency and alignment; Andy Grove / Intel origin, John Doerr / Google, Measure What Matters; contrasted with MBO and KPIs; cautioned by Goodhart's Law. Rich, consistent, strongly attributable activation.

Pre-submission Checklist

  • I have searched existing anchors and this term is not already included
  • This term refers to a well-established concept (not something I invented)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions