Why OKRs Fail on Project-Based Models and How Outcome Funding Can Fix Them
Many organizations adopt OKRs but keep output-based roadmaps and decision-making, so objectives end up as slides while teams still receive prioritized feature lists. The article attributes this to companies adopting outcome goals without shifting to the product model that OKRs assume, citing SVPG's Marty Cagan. Common failure patterns include deliverable-style key results, leader-chosen initiatives, committing to solutions before discovery, annual project budgets unlinked to progress, and teams held accountable for outcomes they cannot influence. The author recommends rewriting key results as measurable outcomes with baselines, allocating funding by outcome goal, and releasing funds in stages as evidence of progress appears. A six-question checklist is offered to diagnose whether OKRs are working, and the author suggests fixing discovery and team autonomy before abandoning OKRs.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in