The Case Against Treating Outcomes as the Only Good Key Results

The article traces OKR’s lineage from Peter Drucker’s Management by Objectives through Andy Grove’s Intel turnaround—where revenue leapt from $1.9 billion to $26 billion—and onto John Doerr’s introduction of the framework at Google. It notes that today many practitioners, citing Christina Wodtke’s “drift” warning and Josh Seiden’s emphasis on behaviour change, insist that key results be framed as outcomes (e.g., reduced support calls) rather than outputs (e.g., “launch feature X”). The author argues that this prescription, while well‑intentioned, can be weaponised: teams may cherry‑pick outcome metrics that look good while ignoring the work that actually drives value, and managers may hide the day‑to‑day activities that are essential for sustainable performance.

Within the broader productivity‑tool landscape, the outcome‑only stance reflects a wave of “impact‑first” thinking that has spread from AI product teams to venture‑backed startups. Companies such as Asana, Notion, and many AI‑focused firms now publish OKR dashboards that spotlight user‑growth or cost‑reduction numbers, sidelining the granular deliverables that enable those gains. This mirrors a larger industry shift away from traditional KPI stacks toward more aspirational metrics, a trend championed in books like *Measure What Matters*. Yet the article reminds readers that the original OKR design, as Grove intended, balanced outputs (milestones) with outcomes, providing a safety net against the “output‑only” tunnel vision that can surface when teams chase headline numbers without clear process visibility.

Looking ahead, organisations that adopt a pure‑outcome OKR regime risk creating blind spots: hidden toil, misaligned incentives, and metric‑gaming that can erode trust and stall long‑term innovation. Leaders should therefore embed a hybrid view—pairing outcome‑oriented key results with transparent output checkpoints—to keep teams accountable for both the “what” and the “how.” Watch for emerging frameworks that blend OKR with lean‑startup or continuous‑delivery metrics, and for a possible resurgence of Drucker‑style objective setting that re‑emphasises the importance of measurable activity as a foundation for impact.