How to Set OKRs for Software Developers: A Technical Leader's Framework

This article explores how to properly set OKRs (Objectives and Key Results) for software developers, addressing the common pitfalls where code lines are equated with productivity and bug counts are directly linked to performance reviews.

The author presents a framework based on the "first principle" that business objectives are primary for R&D teams. However, this doesn't mean developers should simply mirror product OKRs. Instead, the key insight is: how requirements are completed matters as much as completing them . The author's formula is: "awesome = high efficiency + high quality + sustainability" .

Efficiency (效能) encompasses fast requirement delivery, low/no operational overhead, and rapid future iterations. For example, if build times take 10 minutes, a KR might target reducing this to under 2 minutes.

Quality (质量) includes good user experience (fast response), no financial or data security issues, no production incidents, and low MTTR (Mean Time To Recovery) when issues occur. Quality is the foundation of efficiency—speed without quality is meaningless.

Sustainability (可持续) means that one instance of speed or quality isn't enough; both must be maintained long-term. This may require addressing technical debt.

Measurability (可度量) is critical—OKRs must be objectively quantifiable. Vague goals like "improve development efficiency" are insufficient. Examples include: reducing development time for certain requirement types, or improving payment RTT from 300ms to under 200ms.

The article concludes with two guidelines: 1) Focus on outcome-based rather than output-based metrics; 2) Optimize for team or全局成果 rather than individual or local results.