Product Management 20 min read

Practical Guide to Effective OKR Execution (Part 4)

The fourth part of the “OKR Sword” series teaches teams to continuously refine OKR execution using the ABCDE framework—aligning goals, planning detailed actions, concentrating on critical items, embedding OKRs daily, and persisting over time—while handling personal vs. team OKRs, commitment vs. challenge types, timely adjustments, and remote‑work adaptations for sustained alignment and impact.

vivo Internet Technology
vivo Internet Technology
vivo Internet Technology
Practical Guide to Effective OKR Execution (Part 4)

Author: vivo Internet Platform Product R&D Team

This article is the fourth practical piece in the “OKR Sword” series, focusing on how teams can continuously optimise OKR execution to ensure high efficiency.

1. Preface

Just as a craftsman repeatedly polishes a blade or a jade carver refines a stone, teams must keep refining their OKR processes to achieve excellence.

2. Executing OKR Well – The ABCDE Framework

2.1 Aim in line – Regular communication for shared goals

Teams need frequent, transparent communication (formal OKR meetings, informal coffee‑break chats, top‑down monthly one‑on‑ones, or bottom‑up office‑hour sessions) to ensure everyone understands the objectives, responsibilities and the rationale behind them.

2.2 Be planned – Detailed execution plans

“Preparation leads to success” (《礼记·中庸》). Weekly plans should focus on OKR‑related work, avoid meaningless filler, and be tracked with an OKR management tool (see Figure 2‑1).

2.3 Concentrate – Focus on the few critical items

When setting OKRs, avoid the “I want everything” trap. Prioritise high‑impact items, discard low‑value tasks, and constantly ask: “If we don’t do this, does it affect the goal?” The Apple turnaround under Steve Jobs (cutting 70% of product lines) is a classic example of focus.

2.4 Daily – Integrate OKR into daily work

Make OKRs part of routine activities (e.g., weekly reports) so they stay visible and actionable. High‑ambition goals need continuous feedback; otherwise they become “zombie OKRs”.

2.5 Effect of long time – Persistence yields advantage

Initial OKR cycles may feel like a slow‑acting medicine. Over time, teams develop self‑drive, a challenge‑oriented culture, and stronger execution capability, but the impact emerges only after sustained effort.

3. Key Issues in Different OKR Execution Stages

3.1 Personal vs. Team OKR

Personal OKRs should align with, contain, and extend team OKRs. The “owner” system assigns a dedicated KR owner to track progress.

3.2 Commitment‑type vs. Challenge‑type OKR

Commitment OKRs are more certain, short‑term and tied to daily metrics; challenge OKRs are aspirational, longer‑term, and aim to stretch the organization.

Successful challenge OKRs require managerial support (empowerment and resources) and may span multiple quarters.

4. Adjusting OKRs During Execution

Adjustments are needed when (1) actual progress deviates significantly from the target, or (2) higher‑level strategic shifts occur. Adjustments should be value‑driven, regular, and not overly frequent.

5. OKR Execution Under Pandemic Conditions

Remote work requires daily “morning‑evening” stand‑ups to maintain information flow and team spirit, online OKR meetings with interactive elements, and occasional morale‑boosting benefits.

6. Conclusion

The article summarises practical tips for effective OKR execution, emphasizing continuous improvement, alignment, focus, and adaptability. The next piece will discuss the “hard performance metrics and soft cultural atmosphere” that make OKRs win.

managementAgileOKRgoal settingremote workTeam Execution
vivo Internet Technology
Written by

vivo Internet Technology

Sharing practical vivo Internet technology insights and salon events, plus the latest industry news and hot conferences.

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.