The article examines how leading tech companies are abandoning Scrum and traditional agile ceremonies in favor of more flexible, outcome‑focused methods such as OKRs, a "no formal methodology" approach, and Shape Up, highlighting economic pressures, talent dynamics, and the evolving role of agile professionals.
This article explains how to differentiate goals from plans, align objectives with strategy using SMART and OKR principles, apply Work Breakdown Structure (WBS) to break down goals into concrete actions, and use time‑management techniques like the Eisenhower matrix for effective execution.
This article traces the evolution of OKR in Chinese internet giants—from its 2013 introduction and peak popularity to its recent decline and conflation with KPI—while highlighting management theory origins, employee experiences, and concluding with a promotion for the IDCF DevOps conference.
Developers often struggle with vague OKR metrics, so this article outlines a comprehensive framework—grounded in first principles—to define, measure, and achieve developer OKRs by focusing on efficiency, quality, sustainability, and clear, objective metrics that align with business goals.
The article proposes a technical‑leader framework for developer OKRs that prioritizes business outcomes over raw output, defining “awesome” as the sum of high efficiency, high quality, and long‑term sustainability, and urging measurable, outcome‑focused KRs that emphasize team‑wide results rather than individual line counts.
This article explains the purpose of OKR, how it addresses focus, transparency, measurement, and motivation, outlines the iterative top‑down and bottom‑up process for creating OKRs, discusses when to include launch dates, and compares OKR with the OGSM framework for strategic planning.
This article outlines a comprehensive approach for technology leaders to enhance software development efficiency through strategic R&D planning, OKR setting, organizational structure, performance measurement, process optimization, architecture, technical capability, quality and stability management, tailored to different business stages and team sizes.
This article examines how corporate goals function as incentives, tracking mechanisms, and evaluation tools, tracing their evolution from MBO and SMART to OKR, and argues that while goals consume significant resources, they often fail to motivate, improve performance, or provide accurate progress data.
This article examines the shift to multi‑entity, cross‑stage collaboration in enterprises, outlines the resulting inefficiencies and resource constraints, and presents a three‑step solution—measurement, analysis, improvement—implemented through a unified R&D efficiency management platform that standardizes workflows, integrates OKR and metric dashboards, and drives digital transformation for sustained productivity gains.
This article explains how to combine OKR and agile activities to set measurable business goals, avoid common pitfalls, and create a continuous loop of planning, execution, review, and optimization that aligns strategic objectives with day‑to‑day value delivery in R&D projects.
The article explains how misleading metrics like “watermelon‑type” KPIs can mask poor system availability, introduces the OKRa framework that adds activities to traditional OKRs, and promotes a nationally certified DevOps engineering program to improve end‑to‑end R&D efficiency.
By defining clear, measurable objectives and key results, aligning them with strategic goals, and continuously testing, prioritizing, and iterating actions, R&D teams can maintain focus, avoid distractions, and translate vision into tangible outcomes through a systematic OKR workflow.
This guide outlines common communication pitfalls and offers a structured approach—including awareness of concept alignment, RASCI role positioning, appropriate communication channels, positive expression techniques, logical frameworks, sequencing methods, fact‑finding principles, and goal‑setting tools like OKR and KPI—to boost collaboration efficiency in teams.
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.
The article outlines how to run effective OKR retrospectives by treating them as non‑punitive, team‑centric reviews that use simplified self‑assessment templates, short sharing sessions, transparent feedback, positive reinforcement and modest awards, ensuring honest reflection, continuous improvement, and better planning for the next quarter.
This article shares the practical methods a R&D team used to create a strong organizational atmosphere, align responsibilities, empower members, and drive performance through OKR, offering concrete steps, case studies, and actionable insights for sustainable growth.
The article explains that successful OKR implementation relies on a dual‑wheel drive—cultivating a positive atmosphere and delivering strong performance—so that each reinforces the other, and outlines how managers can foster this balance through trust, fair evaluation, empowerment, and shifting from tactical to strategic mindsets.
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.
This article explains the history and principles of OKRs, outlines a step‑by‑step process for defining a technical department’s purpose, identifying internal customers and their needs, reviewing past OKRs, and establishing practical guidelines for drafting, iterating, and communicating new OKRs.
Google has replaced its twice‑yearly performance reviews with a once‑a‑year GRAD (Google Reviews and Development) system that emphasizes employee impact, reduces paperwork, and builds on the OKR framework, while the article also promotes an upcoming IDCF DevOps hackathon in Hangzhou.
Drawing on three years of product‑team experience, the article outlines how OKR tracking evolved through a “Do‑Not” start, process consolidation, and an information‑driven timeline, emphasizing weekly summaries, bi‑weekly meetings, monthly celebrations, quarterly reviews, a lightweight “callme” tool, and core principles of transparency, positive incentives, and a happy team culture, while urging each team to tailor its own rhythm for continuous improvement.
The guide advises building a flexible, module‑based structure with an internal OKR coach, strengthening backup and onboarding, ensuring full‑team participation and a happy, proactive atmosphere, granting front‑line decision authority while maintaining oversight, and using a warm‑up checklist to create an empowered, supportive culture for successful OKR execution.
This first practical installment of the OKR Sword series explains how the 3C formulation principles—Concentrated, Challenging, Controllable—guide objective creation, outlines three sources of goals, and presents a four‑step process (background input, collaborative drafting, alignment, personal definition) for aligning team cognition, motivation, and performance.
This article outlines Ctrip's hotel R&D team's systematic approach to boosting development efficiency through OKR alignment, MVP-driven value delivery, agile practice upgrades, and DevOps automation, detailing challenges, solutions, measurement metrics, and continuous improvement strategies.
The article advises teams to adopt OKR gradually with minimal friction, using simple, phase‑appropriate tools instead of heavyweight solutions, while steering clear of tool‑centric traps, bureaucratic formalism, and short‑termism, and focusing on transparent formulation, regular tracking, and reflective review to embed OKR habitually.
This article details Vivo's internet platform product R&D team's experience introducing OKR, outlining cultural prerequisites, positive and negative impacts, practical steps, pilot execution, common challenges, and guidance for other organizations seeking to adopt the framework.
The article details how vivo’s Internet Platform Product R&D team introduced OKR in 2019 by aligning it with core values, selecting pilot teams, addressing challenges such as performance linkage and contract workers, and following a step‑by‑step, leadership‑backed process that balances flexibility with unified thinking to achieve organization‑wide goal alignment.
This article details how the Vivo Internet Platform product R&D team introduced the Objectives and Key Results (OKR) framework, the challenges they faced before its adoption, and the six major improvements—including clearer goals, value‑focused challenges, enhanced collaboration, a stronger learning culture, continuous innovation, and higher employee productivity—that resulted from the OKR implementation.
By adopting OKR, Vivo’s Internet Platform R&D team aligned strategic goals, prioritized high‑value initiatives, streamlined collaboration through the HuoLi platform, fostered a robust learning culture, spurred internal innovation, and boosted productivity, creating a virtuous flywheel that positions the team as a self‑organizing, high‑performance benchmark.
This article shares concrete OKR templates, step‑by‑step formulation, implementation, tracking methods, and performance‑linkage advice, offering actionable guidance and visual examples for teams that already have a vision and mission in place.
Google has replaced its bi‑annual OKR‑based performance reviews with a once‑a‑year GRAD system that focuses on employee impact, aiming to cut paperwork, streamline feedback, and better align talent development with company goals.
Integrating a dynamic load‑testing model into the OKR workflow dramatically streamlines performance testing by allowing flexible pressure control, manual intervention at safe thresholds, and reducing the fatigue and errors associated with traditional static ramp‑up strategies.
This guide outlines a four‑step framework for taking over a new technical team, detailing six key tables for people, talent pipelines, development plans, responsibilities, and project mapping, and explains how to align goals, communicate effectively, and track progress with OKR/KPI mechanisms.
This guide outlines a four‑step process for new technical managers—identifying people, defining work, linking people to tasks, and setting clear goals—supported by six practical tables such as member information, talent ladder, development plans, RASCI matrix, and OKR tracking.
The article argues that performance evaluations often demoralize employees because they focus on individuals rather than objectives, advocates shifting scores to projects, products, or teams, critiques the misuse of KPI and OKR, and offers personal reflections on finding growth beyond corporate metrics.
This article analyzes the efficiency challenges faced by Youzan’s mid‑platform approach, identifies three major pain points in demand planning, development cycle length, and uneven value delivery, and presents five practical interventions—including a company‑wide backlog, OKR alignment, proportional resource support, and co‑development—that reduced overall delivery time by 10% and highlighted new coordination issues for future improvement.
This article explains the differences between OKR and KPI, offers practical guidance on defining clear objectives and key results, shares common challenges and solutions, and provides examples and stories to help teams adopt OKR as a goal‑setting framework.
Guo Xinyi shares how Xianyu’s PMO transformed its project‑management through evolving agile squads, data‑driven OKR‑Scrum‑DevOps integration, and technical branding such as Flutter, establishing feedback loops and metrics that lifted delivery efficiency into the top‑30 % of peer teams while avoiding superficial OKR use.
Drawing from recent training and classic management books, this article shares twenty actionable lessons for CTOs, covering general management principles, effective meeting practices, team structuring, performance evaluation, and technical leadership to boost productivity and align technology with business goals.
This article details a systematic redesign of an internal OKR management tool, covering business analysis, user research, scenario mapping, design solutions, messaging strategy, implementation results, and key lessons for creating efficient enterprise product experiences.
This article examines common misconceptions in software development performance management, critiques the blind worship of KPI and OKR, and proposes a first‑principles framework consisting of three goals—delivering more value, fostering end‑to‑end collaboration, and stimulating intrinsic motivation—to guide effective R&D performance evaluation.
This article presents a curated list of ten insightful resources covering Google’s OKR guide, code coverage best practices, code health principles, software product team efficiency metrics, unit testing responsibilities, quality assurance case studies, effective code review, Microsoft’s testing transformation, agile misconceptions, and related engineering topics.
The PODE (Product + OKR + DevOps + Empower) framework, created by China Unicom’s Operations and Scheduling Center, restructures product teams, aligns objectives with measurable results, adopts DevOps practices, and empowers staff, dramatically improving collaboration, efficiency, and product quality across distributed teams.
This article analyzes the roles, differences, and suitable scenarios of OKR and KPI, explaining how each framework drives performance, the contexts in which they thrive, and why OKRs are not simply a modern replacement for KPIs.
The article explains how OKR, unlike KPI, helps organizations navigate uncertainty by separating inspirational objectives from measurable key results, discusses practical examples, layering challenges, and offers guidance on integrating OKR with KPI while warning against deterministic thinking.
The article examines why large companies like Alibaba are abandoning mandatory weekly reports and PPTs, offers practical advice on writing effective reports, explains what leaders expect, and proposes OKR as a more transparent alternative for information flow in modern organizations.
This article analyzes Youzan’s hybrid organizational model that blends functional teams with Feature Teams, detailing the shortcomings of traditional functional structures, the criteria for adopting Feature Teams, and practical steps for aligning goals, self‑organizing, resource planning, and decision‑making to achieve more agile collaboration.
In complex, highly specialized organizations, cross‑team collaboration often suffers from misaligned goals and delayed issue detection, but applying OKR with clear alignment, regular reviews, and timely re‑calibration can dramatically improve coordination and reduce hidden losses.
This article explains the origins, core concepts, implementation steps, scoring methods, common pitfalls, and complementary practices such as CFR for Objectives and Key Results (OKRs), offering practical guidance for organizations aiming to improve focus, alignment, and performance.
Demand value closed-loop management integrates OKR alignment with R&D efficiency by linking company strategy, business‑line OKRs, and specific implementation demands through macro, meso, and micro practices—using value tags, quantifiable targets, and review processes—to focus limited resources on the highest‑value initiatives and enable timely adjustments.
Improving organizational efficiency hinges on both invisible drivers—fair compensation and a shared mission—and visible practices such as OKR‑aligned goals, hypothesis‑validation value loops, and digital collaboration tools, which together enable cross‑functional teams to coordinate, iterate rapidly, and translate specialized labor into cohesive, high‑performance outcomes.
The talk explains how OKR and Agile, when combined with system thinking and thoughtful organizational design, create iterative, value‑driven processes that align teams across hierarchical layers, adapt to complexity, and transform mission and vision into concrete actions for greater efficiency.
The article examines Google’s adoption of Objectives and Key Results (OKR), outlines seven reasons why the framework drives clarity, transparency, alignment, discipline, continuous management, standardized processes, and employee growth, and shows how other organizations can apply these insights to improve strategic execution.
This article presents a comprehensive guide based on Google's OKR playbook, explaining the purpose of Objectives and Key Results, detailing practical rules for writing good OKRs, highlighting typical mistakes, and offering self‑assessment tests to help teams implement OKRs successfully.
This article explores how OKR can enhance remote work by outlining its advantages, challenges, and practical implementation steps—including weekly cycles, scoring methods, and integration with tools—while comparing OKR to KPI and offering real‑world examples from leading tech companies.
ByteDance’s Vice President Xie Xin shares how 50,000 employees worked from home during the pandemic, detailing rapid tool development, health‑reporting apps, the evolution of Feishu’s communication suite, innovative meeting formats, OKR‑driven goal management, and the human‑focused practices that kept productivity high.
The article argues that software testing quality cannot be fully captured by quantitative metrics alone and should instead be guided by customer expectations, project goals, and OKR‑based priorities, emphasizing the need for thoughtful test case design and continuous improvement of tester skills.
Since 2017 Youzan has built its own Efficiency Platform, evolving from a basic data‑unification tool into a comprehensive collaboration and workflow system that integrates demand management, agile practices, merchant SLA, prioritization, value‑loop analytics, and internal services, embodying efficiency, collaboration, and continuous improvement.
Youzan introduced a semi‑annual OKR‑driven value‑loop management system that aligns company, business‑line, and project teams around prioritized demands, tracks expected versus actual outcomes, and enables transparent, end‑to‑end value flow for efficient resource allocation and continuous improvement.
The article shows how Scrum’s empirical control theory—through transparent goal setting, systematic inspection of driving points via a growth‑flywheel model, and adaptive, data‑driven reviews and dynamic team composition—can replace linear strategic project management with a rapid, responsive process suited to uncertain market conditions.
Facing rapid growth, Youzan’s Efficiency Improvement team built a value‑stream system to manage the full demand lifecycle—from business and product planning through research, analysis, scheduling, implementation, and post‑launch value review—reducing information asymmetry, boosting cross‑team trust, and aligning outcomes with OKRs.
Youzan scales demand backlog management from a single product to multiple lines by aligning OKR‑driven strategic goals with stakeholder inputs, centralizing ownership in a product‑owner‑led backlog that integrates information, uses user‑story, impact‑mapping and MoSCoW prioritization, employs fixed Scrum/Kanban cycles, splits large backlogs by domain, and leverages electronic kanban tools while continuously refining granularity and value‑loop closure.
This article examines ByteDance’s unique management model—transparent information flow, trust‑based culture, context‑over‑control principles, and rigorous OKR practices—that together enable a 5‑digit employee base to scale quickly while maintaining high performance and innovation.
This article explains the fundamentals of OKR, compares it with KPI, outlines the philosophical differences, presents the 70% principle, and provides practical steps for implementing OKR in teams to boost focus, agility, transparency, and innovation.
This article explains the OKR framework, its origins, why it outperforms traditional KPI, how to design feasible OKRs using SMART and the 5‑4 rule, provides real‑world examples, and offers common pitfalls and actionable tips for sustainable adoption.
This article explains the OKR work method, its practical impact on a testing team, how to set effective Objectives and Key Results, and contrasts OKR with KPI to help organizations adopt goal‑oriented management practices.
Management, like technology, blends technical rigor—task execution, business assurance, and strategic OKR alignment—with artistic sensibility—trust-building, talent nurturing, and self-development—so leaders must master both mind and heart to drive results, foster collaboration, and continuously refine objectives through iterative reviews.
In a 2019 GTLC Beijing talk, Zhang Chu, Vice President of Technology at Mafengwo, explains why measuring engineers is essential, outlines five dimensions of their work, warns against common metric pitfalls, and shares practical frameworks like OGSM and OKR to create goal‑focused, balanced performance evaluations.
This guide compares OKR and SMART goal‑setting frameworks, explaining OKR’s objective‑key‑result‑action structure, its hierarchical alignment across company, team and project levels, and how it differs from SMART’s specific, measurable, achievable, relevant, time‑bound criteria, helping managers choose the right approach for project process management.
This guide shows how to integrate the Objectives and Key Results (OKR) framework into project management by decomposing long‑term goals into measurable milestones, aligning resources and teams through regular daily, weekly and monthly check‑ins, and combining agile practices such as Scrum and Kanban to keep projects on track, reduce waste, and ensure transparent progress.
This article explains how Fangduoduo’s R&D team creates an empowering platform by gathering creative talent, fostering a self‑driven culture, integrating product thinking into engineering, and applying DevOps, OKR, and Scrum practices learned from leading Silicon Valley companies.
In this interview, PingCAP co‑founder and CTO Huang Dongxu shares how his team recruits talent, cultivates engineers through open‑source contributions, uses OKR instead of KPI for performance, and leverages community events to grow the TiDB distributed database project, while also promoting the upcoming GIAC conference.
The article discusses how QA teams can enhance their effectiveness by restructuring weekly meetings, adopting OKR methodology, focusing on problem‑solving and leadership development, and provides practical guidelines and examples for implementing these practices in R&D environments.
This article explains the OKR framework, why it matters for organizations, the qualities of good objectives and key results, provides a startup fundraising example, and offers practical steps to implement and monitor OKRs for better goal achievement.
The article critiques conventional performance evaluations, argues that goals should improve organizations rather than judge individuals, explores the pitfalls of KPI, and shows how OKR, when properly applied, can foster transparent, purpose‑driven work while encouraging personal growth.
This article details Ctrip's four‑year journey of using the OK system and OKR framework to create agile OK teams, drive high‑efficiency operations, implement entrepreneurial incentive mechanisms, and cultivate talent through the Huangpu training camp, ultimately reshaping corporate culture and sustaining rapid growth.
This article describes how Ctrip’s Train Ticket SBU introduced the OK organizational model and OKR goal‑setting framework, along with a performance‑based “投名状” incentive and the Huangpu training camp, to maintain agility, drive growth, and foster an entrepreneurial culture within a rapidly scaling R&D organization.
This article shares a former Facebook engineer’s deep dive into the company’s 12‑year evolution, revealing how hack culture, a balanced design‑engineering approach, open data policies, OKR‑driven performance reviews, and strategic talent management have shaped a world‑class engineering organization and offer lessons for Chinese tech firms.
In his 2015 startup community conference speech, Li Kaifu shares eight practical lessons drawn from his experiences at Apple, Google, and Microsoft, covering vision setting, versatile leadership, product methodology, talent acquisition, retention strategies, smart‑person management, proactive downsizing, and the importance of precise forecasting for sustainable growth.
Discover Wandoujia’s comprehensive R&D management framework, covering five essential steps—from project initiation and OKR goal setting to progress control, team leadership, and interference elimination—along with the tools, processes, and cultural practices that enable rapid, high‑quality product delivery.
This article explains the OKR framework, contrasts it with KPI, outlines its benefits, prerequisite conditions, step‑by‑step implementation, and common mistakes, providing practical guidance for organizations seeking focused, measurable goal management.
