Expert Warns OKR Misuse Undermining Software Engineering Ambition

Daniel Turhors North, an expert with a decade of experience guiding organizations in adopting Objectives and Key Results (OKRs), has observed a “worrying trend” of widespread misuse that fundamentally undermines their purpose. Speaking on Modern Software Engineering, North highlighted three critical areas of failure: how OKRs are defined, tracked, and ultimately reviewed. He traced the genesis of OKRs back to Andy Grove at Intel, who, inspired by Peter Drucker’s Management By Objectives (MBO), sought to rectify MBO’s inherent flaw of rewarding “mediocrity” by punishing ambition. Grove envisioned OKRs with “aspirational rather than operational” objectives and “scary” key results—moonshots not necessarily expected to be fully achieved, but rather to push teams to their furthest potential. Correct definition, North emphasized, means objectives state what to achieve, not what to do (e.g., “Dominate the sector” over “Reduce customer churn”), and key results should be visceral behavioral changes, quantified by “Who does what by how much,” rather than mere vanity metrics.

The pitfalls extend significantly into the tracking and review phases. North noted that weekly reviews often mistakenly focus on activity completion (“how much we’ve done”) instead of progress toward the key result (“are we nearly there yet?”). He endorsed Christina Wodtke’s “Radical Focus” framework for weekly reviews, which balances confidence in hitting key results with “health metrics,” “heads-up” organizational insights, and priority setting. Crucially, North warned against treating key results as absolute targets for promotion or bonuses, as this reverts to MBO’s “loss aversion” trap, punishing ambition and fostering lowballing. Invoking Goodhart’s Law—“When a measure becomes a target, it ceases to be a measure”—he added a corollary for OKRs: “When an aspiration becomes a target, you need to dream bigger.” He stressed that the true value of an OKR review lies in assessing how far a team got, regardless of the initial aim, and urged organizations to prioritize intrinsic motivators like autonomy, mastery, and purpose, as outlined by Daniel Pink, over toxic extrinsic incentives when implementing OKRs.