Why Traditional Performance Reviews Miss the Mark and How OKR Can Change the Game

After hearing several colleagues’ frustrations with performance reviews, the author reflects on why many feel demoralized: the standards used by companies often differ from employees’ expectations, and discussions with managers or HR can feel like personal condemnation.

Two core viewpoints are presented:

Performance goals are meant to improve organizational and individual efficiency, not to serve as a judgment tool.

People are complex and fluctuate in state; assessments should focus on tasks, not on the person.

The author argues that performance scores should be assigned to projects, products, departments, or code rather than to individuals, noting that current management practices often target people, leading to a “public shaming” atmosphere.

Illustrative Examples

Historical anecdotes (e.g., Su Buqing, Hua Luogeng, Zheng Yuanjie, Leo Tolstoy) and sports figures demonstrate that early failures do not preclude later success, just as exam scores do not fully represent a person’s potential.

Comparing performance scores to school exam grades, the author stresses that a low score at one moment does not define a person’s lifelong capability.

Recent trends show major tech and consulting firms abandoning strict KPI systems in favor of more flexible approaches such as OKR (Objectives and Key Results). Notable leaders (Tencent’s Zhang Xiaolong, Baidu’s Li Yanhong, Xiaomi’s Lei Jun, Wang Shi) have publicly warned against KPI‑driven cultures.

OKR Characteristics

0) Proposed by employees.

1) Goal‑oriented.

2) Shared across the organization.

An example OKR is provided:

Objectives: Enhance user experience. Key Results: Reduce user steps by >20%. Decrease support tickets by >40%. Maintain 99.9% of operations under 100 ms response time.

The author shows how such objectives can be broken down for product and backend teams, ensuring transparency and allowing anyone to question or improve the goals.

The pitfalls of KPI are highlighted: treating it as a post‑hoc check leads employees to chase metrics without understanding purpose, stifling innovation and personal growth.

Historical practices (e.g., Panasonic’s long‑term planning) are contrasted with today’s rapid product cycles, where frequent strategic shifts leave employees unclear about their targets.

Ultimately, the author advises individuals to treat performance scores like exam grades—useful for feedback but not definitive of worth—and to focus on personal development, doing the right thing regardless of metrics.

“Do the right thing, wait to get fired.” This mantra, quoted from Brendan Sterne’s article and the book *Team Geek*, emphasizes that true growth comes from aligning with purpose, not from chasing scores.