OKRs Are Bullshit
Objectives and Key Results (OKRs) are criticized here as a cargo-cult management fad that incentivizes metric-chasing, encourages performative planning, and often misaligns with the messy, qualitative reality of building products and organizations. Many contributors argue that OKRs are frequently misapplied—used for everything, pushed down to individuals, tied to performance reviews, or imposed without real strategy—turning them into demotivating bureaucracy rather than a tool for focus and alignment. A minority view holds that when used sparingly, with clear strategy, autonomy, and good management culture, OKRs can help large organizations communicate priorities and coordinate cross-team work, but even supporters stress that implementation quality and incentives matter far more than the framework itself.
Skepticism about OKRs and Metric-Driven Management
- Many see OKRs as “cargo cult” management: adopted because successful companies used them, not because they fit the local context.
- Strong concern that over‑measuring leads to ignoring important but hard‑to‑measure work (craft, intuition, long‑term quality, team health).
- Metrics are easily gamed: people optimize the number (page speed, signups, watch time) at the expense of user value or long‑term outcomes.
- Stretch targets and the “70% completion is success” idea often feel demoralizing or absurd, especially for binary tasks (migrations, launches).
- In some orgs OKRs become thinly disguised performance‑management tools or “permanent PIPs,” not strategy tools.
Defenses of OKRs and When They Help
- Supporters argue OKRs are a neutral tool for:
- Communicating strategy across large hierarchies.
- Aligning cross‑team dependencies on multi‑quarter work.
- Giving teams a basis for saying “no” to random requests.
- They can be useful for:
- Focusing on a few priorities.
- Providing measurable feedback loops.
- Structuring negotiations between teams that must cooperate.
Management, Culture, and Incentives
- Recurrent theme: no framework survives bad culture or incentives.
- OKRs can’t fix weak leadership, misaligned rewards, or lack of strategy; they often just surface those problems.
- Some argue “good people with light process” beats any formal system; others counter that process is essential at scale and to avoid heroics.
Common Implementation Problems & Failure Modes
- Top‑down, vague, or euphemistic objectives (“customer first”, “grow revenue”) that justify anything.
- Cascading OKRs that ignore capacity, producing huge wish‑lists and end‑of‑quarter theater.
- Forcing numeric KRs where numbers don’t fit, or treating them as immutable even when reality changes.
- Confusing OKRs (organization‑level change) with routine work, or demanding OKRs from every team/person every quarter.
- Tying OKRs directly to performance reviews, which encourages sandbagging, metric gaming, and dishonesty.
Alternatives and Process Minimalism
- Some prefer simple, explicit roadmaps, short fixed‑time/variable‑scope projects, and clear ownership over heavy frameworks.
- Others view OKRs as one option in a toolbox, useful when kept simple (few goals, regularly reviewed, not over‑formalized) and decoupled from individual evaluation.