Summary of "The OKR TRAP Most Companies Fall Into"

Concise summary

Daniel Terhorst‑North (Modern Software Engineering) warns that many organizations misuse OKRs across three stages — definition, tracking, and quarterly review — which converts aspirational OKRs back into old MBO-style targets that reward low ambition and gaming. Proper OKRs are meant to be moonshots that stretch teams; key results should measure observable behavior change in a target audience and be visceral/meaningful rather than tasks or vanity metrics.

Origins and context

Andy Grove (Intel) reframed Management by Objectives (MBO) into aspirational OKRs to avoid a “race to the middle.”
OKRs should push teams toward ambitious outcomes. Key results must capture behavior change and measurable impact, not task completion or vanity numbers.

OKR fundamentals

Objective: an aspirational outcome — what you want to achieve; punchy and motivating.
Key Result: a measurable indicator of progress toward that outcome — who does what by how much.
KR definition (“Who does what by how much” — Jeff Gothelf & Josh Seiden):
- Who = target audience
- Does what = behavior change
- How much = measurable, observable amount

Weekly OKR review (napkin model)

Use a short weekly cadence structured around four inputs to inform next-week priorities:

Confidence — How confident are we that we’ll hit the KR?
Health metrics — non-negotiables (people, finances, burn, quality).
Heads-up — external/organizational context and risks.
Priorities / next-week actions — decisions informed by the three inputs.

In weekly check-ins, focus on distance-to-goal (“Are we nearly there?”) rather than a list of completed tasks.

Scoring and quarter-end review

Use progress and distance-to-goal as the signal. Ask, “Are we nearly there yet?” rather than tallying tasks.
At quarter end, judge how far the team moved toward an aspiration and celebrate distance moved, not just binary hit/fail.
Example illustration: target = 10, achieved = 8. Treat 8 as meaningful progress — especially if prior best was 5.

Behavioral science cautions

“When a measure becomes a target, it ceases to be a measure.” — Goodhart’s law

When aspiration becomes a fixed target, people optimize the target rather than the underlying outcome — redesign to preserve aspiration.
Loss aversion and extrinsic rewards: tying KRs to promotion/bonus drives lowballing and gaming; extrinsic punishments demotivate.
Favor intrinsic motivators (autonomy, mastery, purpose — Daniel Pink) over carrots-and-sticks that create dysfunctional incentives.

Key metrics, KPIs, targets, and cadence

Cadence:
- Weekly reviews for tracking and course-correction.
- Quarter-end reviews for outcomes, learning, and ambition-setting.
Acceptable KRs/KPIs:
- Behavior-change metrics (who did what by how much).
- Health metrics: spend/burn, team wellbeing/velocity, quality.
- Outcome metrics (conversion rate, churn reduction, time-to-value) if defined as observable behavior changes.
Avoid:
- Vanity metrics and activity/task counts as KRs.

Concrete recommendations

Definition

Write Objectives as outcomes (e.g., “Dominate X market,” “Slash time to value”), not activities.
Define KRs with the “who does what by how much” rule; ensure measurability and a focus on behavior.
Make KRs stretch-yet-feasible — create excitement (“butterflies”), not demoralizing impossibility.

Tracking (weekly)

Run short weekly OKR reviews using the four-quadrant napkin: confidence, health, heads-up → set next-week priorities.
Focus conversation on distance-to-goal and likelihood of achieving outcomes, not on task lists.

Quarterly review

Do not treat aspirational KRs as pass/fail gates for promotion or bonuses.
Evaluate improvement and learning: how far did the team move toward the aspiration? Celebrate stretch achievements even if below target.
Use results to inform next-quarter ambition (raise aspiration if KRs are repeatedly met).

Organization-level policy

Do not tie aspirational KRs directly to compensation or promotion; use other performance measures if needed.
Maintain explicit health metrics to prevent harmful trade-offs (e.g., shipping at the cost of burnout or overspend).

Behavioral guidance

Favor intrinsic motivation (autonomy, mastery, purpose) over extrinsic carrots/sticks.
If converting a measure into a target, redesign it to avoid creating perverse incentives.

Risks, failure modes, and anti-patterns

Reverting to MBO: making OKRs operational tasks or promotion gates leads to lowballing and mediocrity.
Using vanity metrics or activity counts as KRs leads to irrelevant optimization.
Weekly reviews that report only “what we did” bury the signal about whether outcomes are achievable.
Tying KRs to bonuses creates loss aversion and gaming; extrinsic motivation undermines long-term engagement.
Goodhart effect: rigid targets distort behavior away from intended outcomes.

Presenters and referenced thinkers

Presenter: Daniel Terhorst‑North (Modern Software Engineering)
Referenced: Andy Grove, Peter Drucker, Jeff Gothelf & Josh Seiden, Christina Wodtke (Radical Focus), Daniel Pink (Drive), and the concept of Goodhart’s law.