R&D Management 14 min read

The Rise and Fall of OKR: When a Popular Goal‑Setting Framework Becomes a Burden

The article examines how OKR, once hailed as a revolutionary performance‑management tool by companies like Google and ByteDance, has become a source of misalignment, double‑counted KPIs, and cultural friction, and outlines which types of enterprises can still benefit from it while warning that blind adoption may backfire.

DevOps
DevOps
DevOps
The Rise and Fall of OKR: When a Popular Goal‑Setting Framework Becomes a Burden

Last May, Google announced a reform of its employee performance‑management system, replacing the cumbersome OKR process with a new framework called GRAD after employee surveys showed that only 53% found the previous OKR process worthwhile and many complained about its time‑consuming nature.

Similarly, in February ByteDance’s CEO Liang Rubo announced a shift from bi‑monthly OKRs to quarterly OKRs, arguing that the company’s mature business lines no longer needed such frequent adjustments.

These moves have been interpreted by many managers as a sign that the once‑celebrated OKR system is losing its appeal and becoming a "Chinese countryside KPI"—a tool that looks good on paper but creates new problems in practice.

From OKR to "Chinese Countryside KPI"

OKR (Objectives and Key Results) originated at Intel, was popularized by Google, and later adopted by ByteDance. While it promises autonomy and creativity, many employees find the process overly burdensome, leading to misalignment, excessive meetings, and a perception that OKRs are merely another layer of performance assessment.

How OKR Can Undermine Companies

Alignment Overhead : Proper alignment requires time‑consuming discussions between managers and employees, often resulting in superficial agreements or top‑down imposition of objectives.

Double Assessment with KPI : Although OKRs are meant to be non‑evaluative, many firms covertly tie them to performance reviews, creating a double‑burden when combined with traditional KPI metrics.

Unrealistic Ambitions : Leaders sometimes set overly ambitious objectives that employees cannot realistically achieve, turning OKR into a punitive tool rather than an inspirational one.

When OKR Fails

OKR works best when leaders have a long‑term vision and employees are highly motivated. In companies lacking transparent culture, strong talent pipelines, or a willingness to engage in open communication, OKR can become a bureaucratic burden.

Examples of failure include small startups where founders set unrealistic "industry‑leading" objectives, or enterprises that frequently adjust OKRs (e.g., three times per quarter), eroding trust and focus.

Which Companies Are Unsuitable for OKR?

Industries with slow change where traditional goal‑setting (KPI, SMART) suffices.

Highly regulated sectors (medical, finance, aviation) where rapid trial‑and‑error is risky.

Organizations lacking a collaborative culture or talent system to support transparent goal‑setting.

Which Companies Can Benefit from OKR?

1. Internet startups – need flexible, fast‑moving goals to discover product‑market fit.

2. Innovative firms – benefit from rapid iteration and learning cycles.

3. Project‑driven organizations with flat structures – can avoid hierarchical bottlenecks.

4. Companies undergoing transformation – require clear, shared objectives to guide change.

When applied thoughtfully, OKR can clarify priorities, improve progress tracking, and foster teamwork; however, it remains a tool whose success depends on proper cultural fit and disciplined implementation.

leadershipGoogleOKRorganizational cultureperformance managementByteDance
DevOps
Written by

DevOps

Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.