Integrating OKR with Agile Practices for Effective Value Delivery

The author, a former senior project and technology manager at Alibaba, argues that without quantifiable goals, management cannot allocate resources, track costs, or verify whether work delivers real business value. He cites Peter Drucker’s principle that "without measurement, there is no management" and illustrates the risk of pursuing goals based solely on intuition.

Two main challenges are identified: (1) quantitative targets (data metrics) often capture only a fragment of business value, and (2) these targets are estimates that may not reflect true strategic outcomes. A historical analogy from the Three Kingdoms demonstrates that achieving a metric (capturing two provinces) does not guarantee the intended strategic result (reviving the Han dynasty).

The proposed practice combines OKR with agile activities. At the strategic level, company‑wide OKRs are derived from mission and vision, broken down into five major value dimensions, and linked to annual objectives (the "O") and key results (the "KR"). These feed into quarterly tactical OKRs, which drive project and business OKRs, forming a hierarchical network that aligns every team and individual.

Implementation steps include:

Defining OKR activation zones and agile activation zones, ensuring that OKRs generate key actions that become inputs for agile work.

Running weekly business meetings to review OKR progress, adjust actions, and synchronize with project status.

Conducting demand briefings where each demand is linked to a specific KR, prioritised, and added to iteration backlogs.

Executing iterative development cycles (requirement preparation, pre‑research, development, release) with continuous value delivery.

Three common pitfalls are highlighted: (1) failing to uncover the true user need behind expressed requirements, (2) setting only core metrics without health indicators (e.g., retention, session length), and (3) treating OKR as a KPI rather than a flexible framework.

To mitigate these, the article recommends a "three‑continuous" approach: continuous delivery (embedding OKR into iteration goals), continuous inspection (adding health metrics to validate true value), and continuous optimization (regularly revisiting the original five value pillars and adjusting OKRs accordingly).

Finally, the author outlines a comprehensive OKR‑driven workflow that starts from value definition, proceeds through deep user‑need analysis, integrates agile activities, and uses data‑driven retrospectives (weekly, monthly, quarterly) to refine strategy, tactics, and execution, ensuring that every effort contributes to measurable business outcomes.