祝融说。

Welcome to Part Two of this book. In Part One, "Rethinking the Mindset," we established a new strategic mentality: we recognized "optionality" as the core asset, "available margin" as the strategic buffer, and "valuable failure" as the ladder of evolution. We have learned how to "think." Now, we will enter a more challenging domain: how to "act" and "organize."

If Part One was about upgrading the "brain" of the organization, then Part Two is about completely rebuilding the "nervous system" and "musculoskeletal system." We will explore how to translate optionality thinking from a high-level strategic concept into daily practices that empower every individual in the organization.

The starting point of this transformation, and its most critical leverage point, lies in answering a seemingly simple yet fundamentally determinative question:

"Who Defines Success?"

The answer to this question directly determines the flow of power, the allocation of resources, the transmission of information, and the life or death of innovation within an organization. The power to define success is what we call "evaluation rights."

In a traditional, hierarchical organization, evaluation rights are highly monopolized by senior management. Through detailed plans, precise indicators, and periodic performance reviews, they define and measure the "success" of every unit and every individual from the top down. This is a management philosophy rooted in "control," born of the industrial age.

However, in the "Age of Possibility" we described in the introduction — an age full of uncertainty — this monopoly on evaluation rights is becoming the greatest shackle on organizational innovation and adaptability. It acts like a powerful central black hole, sucking all vitality and autonomy from the edges of the organization, ultimately leading to the rigidity and death of the entire system.

In this chapter, we will conduct a thorough anatomy of "evaluation rights." We will first reveal how KPIs — a management tool revered by countless organizations — step by step become "alienated" in practice, transforming from a navigational compass into a noose that strangles innovation. Next, through a deep analysis of the radical case of the Chinese apparel e-commerce company Handu Yishe's "Small Team System" revolution, we will witness the astonishing energy unleashed by "distributed decision-making." Then, we will systematically explain why the "evaluation monopoly" must be broken, and how to truly empower "those closest to the gunfire to make decisions." Finally, we will provide a powerful tool — OKR — and reveal its often misunderstood essence: its purpose is not to quantify everything, but to align goals, providing a framework that balances direction with autonomy for the delegation of evaluation rights.

Section 1: The Alienation of KPIs: How Innovation Dies When the Metric Becomes the Target

Key Performance Indicators — the name sounds so scientific, rational, and irrefutable. Born in the 1990s, evolving from Peter Drucker's "Management by Objectives" philosophy, its original intention was noble: to break down an organization's grand strategic goals into measurable, executable, job-specific indicators, thereby ensuring the entire organization moves in the same direction.

In theory, KPIs are a perfect tool. They provide a clear, quantifiable definition for the fuzzy concept of "success." They allow managers to "follow the map" and employees to "work to the benchmark." Over the past few decades, KPIs have swept the globe, becoming the "standard configuration" of modern corporate management.

In reality, however, this ingeniously designed tool has played out a tragedy of "the farmer and the snake" in countless organizations. The KPI — this snake carefully raised by managers — has, in many cases, not helped guard the house, but instead turned around and bitten to death the most precious child of innovation.

This tragedy is what we call "the alienation of KPIs." It refers to the phenomenon where, when a metric or set of metrics is excessively and rigidly tied to reward-and-punishment mechanisms (salary, promotion), the metric itself replaces the broader goal it was meant to measure, becoming the sole driver of organizational and individual behavior.

Behind this lies a profound sociological law known as "Goodhart's Law," classically stated as:

"When a measure becomes a target, it ceases to be a good measure."

In other words, once people start working to optimize a metric, they will find various ways to "manipulate" that metric, even if these methods harm the actual, more important goal behind the metric.

The Three-Stage Death Spiral of KPI Alienation

The alienation of KPIs typically kills an organization's innovation capacity through three progressive stages.

Stage One: Tunnel Vision — Inability to See Beyond the Metrics

When a team's or individual's bonuses and promotions depend entirely on a few specific KPIs, their cognitive field of vision rapidly constricts, like the aperture of a camera, focusing only on activities that can directly affect those KPIs.

Customer service department's KPI is "average call handling time": To shorten call times, representatives may hang up hastily before the customer's issue is fully resolved, or find ways to transfer complex problems to other departments. They stop caring about the fundamental goal — "whether the customer is truly satisfied" — and only focus on whether their call time data is on target.

Sales department's KPI is "revenue": To hit revenue numbers, salespeople may overpromise to clients or sell products to people who are not a good fit. This boosts sales figures in the short term but severely damages the company's long-term reputation and customer retention.

R&D department's KPI is "lines of code" or "number of features": Engineers may write large amounts of redundant, inefficient code just to pad the numbers, or develop a bunch of "fake features" that users do not need. They stop thinking "are we solving a real problem?" and only care about "how far are we from this month's feature count KPI?"

In this state of "tunnel vision," any innovative activity that is not directly related to the KPIs, is uncertain, or requires long-term investment, is seen as a "distraction" and "waste." Employees instinctively avoid these activities, because they not only fail to "add points," but may even "deduct points" by taking time away from KPI-related tasks.

Stage Two: Short-Termism — Sacrificing Tomorrow to Feed Today

KPIs are typically set and evaluated on a monthly, quarterly, or annual basis. This short evaluation cycle inevitably leads organizations to channel resources and energy into activities that can show results in the short term.

Innovation, especially disruptive innovation, is by nature "non-linear" and "delayed in return." In its early stages, it typically requires significant investment, endures countless failures, and cannot generate any appreciable, quantifiable "performance" for a long time.

You want to explore a new market? Sorry, market research and early user cultivation cannot show up as revenue in this quarter's financial report. The project cannot be approved.

You want to develop a foundational technology? Sorry, that technology may take three years to mature, and our CEO is retiring next year. He needs "bright spots" to boost the stock price this year.

You want to refactor an old but still running system? Sorry, refactoring does not bring new features or directly increase user numbers or revenue. Even though we all know this system is a huge technical debt for the future, as long as it barely works today, we should allocate resources to developing new features that produce more visible "output."

Under the baton of KPIs, organizations systematically "discount the future." Any investment in the future is seen as damaging current performance. The organization becomes addicted to picking "low-hanging fruit" (incremental improvements) and completely loses the ability to "plant trees for the future" (disruptive innovation).

Stage Three: Data Manipulation and Internal Gaming

When the link between KPIs and personal interests reaches its peak, and meeting the KPIs becomes increasingly difficult, the final stage of alienation arrives: people stop trying to achieve the targets through improved work and instead start trying to "improve" the metrics themselves.

This spawns all sorts of bizarre and absurd behaviors:

"Data faking": In the internet industry, to meet the KPI for "daily active users," operations teams may use various "red packets," "check-ins," and other tactics to induce users to perform meaningless "zombie clicks." The data looks good, but the product's real value and user engagement may be declining.

"Data hiding": To make their performance look better, a department may selectively report favorable data and hide unfavorable data. Departments stop sharing real information and become wary of each other, creating "data silos" within the organization.

"Gaming the metrics": During the KPI-setting phase, department heads stop thinking about "how to contribute to the company's overall goals" and instead think about "how to secure the easiest, most advantageous KPI for my department." The KPI-setting process becomes a zero-sum internal political game.

When an organization descends into this stage, KPIs have completely transformed from a management tool into an "organizational corrosive." It destroys the organization's culture of integrity, increases internal communication costs and transaction costs, and causes energies that should be directed outward to be consumed in meaningless internal friction.

Why Is KPI Alienation Inevitable?

We must recognize that KPI alienation is not because managers are stupid, nor because employees are immoral. It is a systemic, almost inevitable trend. The reasons are:

1. "Dimensional Reduction" of a Complex World: Value creation in the real world is complex, multi-dimensional, and often difficult to quantify. KPIs attempt to compress this complexity into a few simple, quantifiable numbers. This "dimensional reduction" inevitably loses a great deal of important but hard-to-measure information (such as team morale, customer word-of-mouth, technical debt, brand value). Once an organization begins to manage only the quantified dimensions, the unquantified but equally important dimensions are systematically ignored and sacrificed.
2. Mismatch Between Static Metrics and a Dynamic World: Once set, KPIs tend to have a certain rigidity. But the world we live in is dynamic. When market conditions, user needs, or the competitive landscape change, a KPI that was important yesterday may become irrelevant or even harmful today. However, because of the tight coupling between KPIs and performance reviews, organizations often cannot flexibly and quickly adjust the metrics, watching helplessly as everyone "efficiently" runs toward an already outdated goal.
3. The Information Gap Between "Evaluators" and "Executors": In the traditional KPI system, there is a huge information gap between the "evaluators" (senior management) who set the metrics and the "executors" (frontline employees) who carry out the tasks. Managers are far from the front lines. Their understanding of the real situation on the ground — the subtle needs of users, the actual technical bottlenecks — is often indirect, delayed, and even filtered and sanitized. The "top-level designs" they create based on this incomplete information are often castles in the air, disconnected from reality.

Summary: The Alienation of KPIs

The alienation of KPIs is the inevitable tragedy of a highly monopolized evaluation system. It attempts to use a mechanical, deterministic, top-down cybernetic model to govern an organic, uncertain, bottom-up emergent complex system. The result is inevitably the loss of vitality and the death of innovation.

This is not to completely dismiss the value of "metrics." Metrics are important; without measurement, there can be no improvement. The problem is not with "measurement" itself, but with "who measures," "what is measured," and "how the measurement results are used."

To break the curse of KPIs, we must undertake a profound organizational transformation. The core of this transformation is to liberate "evaluation rights" from the hands of a few managers and return them to those who truly create value — those closest to the gunfire.

Section 2: Case Study — From "Central Planning" to "Distributed Decision-Making": Handu Yishe's Small Team System Revolution

In Jinan, Shandong Province, China, there is an unassuming apparel e-commerce company called Handu Yishe. It has neither a glamorous background nor a blockbuster fundraising story. Yet between 2012 and 2016, this company, in an almost "brutal" fashion, was the top-selling Chinese internet apparel brand for five consecutive years and successfully listed on the capital market.

Handu Yishe's rise was not due to breathtaking design nor brilliant marketing. Its core secret lay in a radical, thorough organizational transformation experiment led by its founder, Zhao Yingguang. The heart of this experiment was to shatter the traditional, pyramidal "central planning" organizational structure into hundreds of tiny, autonomous "amoeba" units.

This transformation, which Zhao Yingguang called the "Small Team System," is the most vivid and boldest interpretation of the idea of "delegating evaluation rights" in practice. By understanding Handu Yishe's story in depth, we can see the astonishing energy that an organization can unleash when evaluation rights are truly granted to the front line.

Background: The Pain of Traditional E-commerce "Centralization"

Before establishing the Small Team System, Handu Yishe, like all e-commerce companies at the time, used a traditional "centralized" model based on functional departments.

• The Product Department was responsible for selecting styles and design.
• The Operations Department was responsible for creating product pages, listing and delisting products.
• The Marketing Department was responsible for advertising and campaign planning.
• The Customer Service Department was responsible for pre-sales and after-sales.

In this model, "evaluation rights" were highly concentrated in the hands of the directors of each functional department and the founder, Zhao Yingguang. For example, whether a piece of clothing could be listed for sale required approval from the Product Director; how a marketing campaign was run required approval from the Marketing Director.

This model functioned reasonably well when the company was small. But as the business grew rapidly, its drawbacks became increasingly prominent, especially in the fast-moving "fast fashion" sector:

1. Slow Decision-Making, Missed Opportunities: A hot-selling item that had just appeared in the Korean market could take a month to go through selection by the Product Department, photography by Operations, planning by Marketing — by which time competitors had already listed it, and the golden window of opportunity had closed.
2. Siloed Departments, Blurred Responsibility: When a piece of clothing sold poorly, whose fault was it? The Product Department would say: "The Operations page was poorly done, the Marketing promotion was ineffective." Marketing would say: "The Product Department chose terrible styles; nobody likes them." Everyone pointed fingers and passed the buck; no one was fully accountable for the final sales outcome.
3. Misaligned Incentives, Lack of Motivation: Employee salaries and bonuses were determined by their department's overall performance and the evaluation of their supervisors. A talented page designer, no matter how good their work, would not see a significant income improvement if the entire Operations department performed poorly. The connection between individual effort and final reward was weak and indirect.

Zhao Yingguang keenly realized that this "central planning" organization was like a clumsy elephant, completely unable to survive in the fast-fashion jungle, which demanded cheetah-like agility. He needed a revolution.

The Birth of the Small Team System: "Blowing Up" the Company into 200+ "Startup Teams"

In 2008, Zhao Yingguang made a stunning decision: dissolve all core functional departments, completely "break up" the company, and restructure it into a brand new structure based on "product teams" as the basic unit.

Each "product team" typically consisted of just three people:

• 1 "Product Developer" (buyer/designer): responsible for selecting styles and determining designs.
• 1 "Page Designer": responsible for visual design and copywriting of the product detail page.
• 1 "Order Administrator": responsible for inventory management and order tracking.

These three people formed the smallest, complete "startup unit." And the most revolutionary thing Zhao Yingguang did was to delegate "evaluation rights" almost completely and unreservedly to these three-person teams.

What Did the Complete Delegation of Evaluation Rights Entail?

1. Style Selection Rights: Each team had the authority to independently decide which clothing styles to list for sale. They did not need approval from any superior. They could make quick decisions based on their understanding of fashion and data analysis.
2. Pricing Rights: The team could independently decide the selling price, discount rate, and promotional strategy for their products.
3. Inventory Rights: The team was responsible for their own product inventory. How many units to produce initially, whether to reorder if it sold well, and how to clear inventory if it sold poorly — all decisions were made by the team itself.
4. Absolute Unity of Responsibility, Rights, and Interests: This was the core essence of the Small Team System. The team's income was tightly linked to the sales performance of its products. The company established a clear, transparent "revenue-sharing formula":

Gross Profit = Revenue - Product Cost - Marketing Expenses Team Commission = Gross Profit x Fixed Percentage (e.g., 15%)

Under this formula, the team's fate was perfectly and directly tied to its own decisions.

If they chose good styles and set reasonable prices, and the products sold well, the team's income would be substantial.

If they chose poor styles or made inventory judgment errors, leading to unsold products, they would receive no commission and might even incur "negative gross profit," requiring future earnings to cover the loss.

From "Working for the Boss" to "Starting a Business for Yourself"

This transformation fundamentally changed the internal rules of the game.

The subject of responsibility changed: Previously, employees were responsible to their department and to KPIs. Now, the team was fully responsible for the ultimate commercial outcome (gross profit) of its own products.

The incentive model changed: Previously, it was a fixed salary plus a vague bonus. Now, it was an entrepreneurial-style commission with "no cap on upside, no floor on downside."

The decision-making mechanism changed: Previously, it was top-down approval. Now, it was bottom-up, autonomous decision-making based on market conditions on the front lines.

Handu Yishe's 200-plus product teams were like 200-plus "micro-companies" operating as internal startups on the company's platform. They were no longer cogs in a massive machine; they were captains of their own small ships. Their mindset had completely shifted from "working for the boss" to "starting a business for myself."

What Did the Delegation of Evaluation Rights Unleash?

This revolution brought about visible, astonishing changes at Handu Yishe:

1. Extreme "Speed": Team decisions required no approval. They could react with lightning speed to market changes. The latest styles seen at Seoul's Dongdaemun market could be listed on Handu Yishe's online store in as little as three days. This speed was unattainable by any "central planning" competitor.
2. Extreme "Variety": Over 200 teams acted like 200 parallel "market sensors." Their individual aesthetics, preferences, and judgments created enormous "cognitive diversity." This allowed Handu Yishe to test a vast range of clothing styles simultaneously, using a "wide-net" approach to capture uncertain "hit" opportunities. Handu Yishe launched over 30,000 new styles annually — dozens of times more than traditional apparel brands.
3. Extreme "Accuracy": Each team was like a shrewd businessperson, intently tracking their own sales data, inventory data, and conversion rates. Because this data directly affected their income, they would spontaneously learn data analysis, study user reviews, and optimize every decision. The entire organization's "market sense of smell" became unprecedentedly sharp.

The Role of the "Big Platform": From "Commander" to "Service Provider"

So, under the Small Team System, what role did the company headquarters and the former functional departments play? Zhao Yingguang redefined them as the "Big Platform."

This "Big Platform" was no longer a "command center" issuing orders, but a "logistics department" and "arsenal" providing support and services to the 200-plus front-end teams. Its responsibilities included:

Providing Infrastructure: For example, a robust IT system, warehousing and logistics, a customer service center, photography studios — public resources that individual teams could not build on their own.

Providing Professional Support: For example, establishing a dedicated "Marketing Support Department" to provide teams with professional advertising advice and tools, while the final decision-making authority over advertising remained with the teams.

Setting the Rules of the Game: Headquarters was responsible for designing and optimizing the core "revenue-sharing formula," ensuring the rules were fair and transparent, and guiding team behavior to align with the company's long-term interests.

Cultivating and Empowering: Building an internal training system to help new employees quickly grow into qualified team leaders.

Headquarters' "evaluation rights" shifted from evaluating "specific business matters" to evaluating "team health" and "platform efficiency." They no longer cared about "whether this piece of clothing looks good," but about "whether our team incubation and elimination mechanism is healthy" and "whether our IT system can support faster product launches."

Summary: Case Study Analysis

Handu Yishe's Small Team System revolution is a quintessential business fable about "delegating evaluation rights." It tells us:

Delegation of power must be synchronized with the binding of responsibility and interests. Granting power without sharing benefits or imposing responsibility only leads to chaos.

Frontline employees often understand the market and users better than managers far from the battlefield. Give them autonomy, and they will create results that exceed your imagination.

The organization of the future may no longer be a "company plus employees" model, but an ecosystem model of "platform plus individuals/small teams." The value of the platform lies in empowering the creators at the front end, not controlling them.

Of course, Handu Yishe's model is not universally applicable. It suits areas where markets change rapidly and require high agility and diversity. But its core idea — breaking the evaluation monopoly and giving the power to define and measure value to those who create it — has profound universal significance.

It challenges every manager to reflect: In your organization, are evaluation rights too concentrated? Are you playing the role of a "micromanager" who oversees every detail, or are you building an "empowerment platform" where countless "Handu Yishe teams" can thrive?

Section 3: Breaking the "Evaluation Monopoly": Let Those Closest to the Gunfire Make Decisions

Handu Yishe's case shines a harsh light on the darkest, most rigid corner of traditional organizational structures — the "evaluation monopoly."

An evaluation monopoly is when the power to define and judge "what is good," "what is important," and "what is success" is disproportionately concentrated in the hands of a few senior managers. This monopoly is a natural product of the industrial-age "command-and-control" management model, but today it has become the biggest obstacle to organizational adaptation and innovation.

The Split Between "Evaluators" and "Executors"

Under a system of evaluation monopoly, the organization is split into two disconnected strata:

A small number of "Evaluators" (senior management): They are responsible for setting strategy, defining goals, allocating resources, and evaluating performance. They are the "thinkers," the ones playing chess.

The majority of "Executors" (middle managers and frontline staff): They are responsible for carrying out orders from above, completing assigned tasks, and meeting set targets. They are the "doers," the chess pieces on the board.

This split creates a fundamental, unsolvable structural problem: those with information have no decision-making power; those with decision-making power have no information.

Frontline employees are closest to the gunfire. They deal with real users every day, handle real technical problems every day, and feel the real temperature of the market every day. They possess the most vivid, real-time, detailed "situational information" about the battlefield. But they have no authority to adjust their actions based on this information. All they can do is report this information up the chain.

Senior managers are farthest from the gunfire. The information they see has been filtered, summarized, refined, and even "beautified" by their subordinates into second-hand reports. These reports are abstract, delayed, and lack detail. Yet they are expected to make major decisions affecting the entire organization based on this "imperfect" information.

This is like a general sitting in a command center a thousand miles away, looking at a blurry old map, trying to direct a soldier engaged in street fighting who can clearly see every enemy position on how to shoot. The result is inevitably missed opportunities and absurd decisions.

Breaking the evaluation monopoly is essentially a revolution of "information rights." Its core is to move decision-making power from the "mountain top" where information is poorest down to the "battlefield" where information is richest.

Why Let Those Closest to the Gunfire Make Decisions?

1. Speed: In a rapidly changing market, speed is life. When decision-making power is delegated to the front line, the organization eliminates the long, inefficient cycle of "information reporting → awaiting approval → instruction transmission." Frontline teams can make real-time, autonomous decisions and adjustments based on real-time changes on the battlefield. The organization's reaction speed can be elevated from the "day" level to the "hour" or even "minute" level.
2. Quality: Better information leads to better decisions. Decisions made by frontline employees based on their rich "situational information" are often far more practical, relevant, and effective than "top-level designs" based on abstract reports from senior management.
3. Innovation: Anomalous signals are often first detected at the front line. A customer service representative engaged in deep conversation with a customer may be the first to discover an unmet new need. An engineer obsessed with new technology may be the first to see a technology's disruptive potential. If these people have no authority to run small-scale experiments, these precious sparks of innovation will be quickly extinguished in bureaucratic processes.
4. Responsibility and Engagement: When employees are given genuine autonomy and decision-making power, they cease to be "passive execution" employees and become "active creation" owners. Their work is no longer about completing a superior's task, but about achieving a goal they themselves recognize and help define. This shift from "I have to" to "I want to" can dramatically unleash intrinsic motivation, a sense of responsibility, and creativity. Gallup surveys consistently show a strong positive correlation between employee "engagement" and their perceived "autonomy."

How to Break the Evaluation Monopoly? — Three Key Empowerment Levers

Breaking the evaluation monopoly is not a simple slogan about "delegating authority." It requires systematic organizational design and cultural change. Here are three key empowerment levers:

Lever One: Information Transparency

If frontline employees do not have the information needed to make high-quality decisions, delegating decision-making power will only lead to chaos. Therefore, the first step in breaking the evaluation monopoly is to break the information monopoly.

Transparent Financial Data: Like Handu Yishe, let every team clearly see their product's real-time sales, costs, gross profit, and other data. Let employees learn to read financial statements like a CEO and understand the nature of business.

Transparent Strategic Goals: Ensure the company's highest-level strategic goals are communicated clearly and without dilution to every employee. Employees must understand "why we are fighting this battle" in order to make decisions on their own turf that are aligned with the overall strategy.

Transparent Customer Feedback: Establish mechanisms so that all employees, regardless of their position, can directly and unfilteredly see and hear the voices of real users. For example, let engineers take turns working in customer service, or push user reviews and complaints in real time to the company's internal communication tools.

Information transparency is the foundation of empowerment. It provides a shared, fact-based "context" for distributed decision-making.

Lever Two: Contextualized Power

Breaking the evaluation monopoly does not mean plunging the organization into anarchy. It does not mean eliminating all hierarchy and authority. Rather, it means shifting power from a static authority based on "position" to a dynamic authority based on "context" and "knowledge."

"Whoever knows, decides": In a specific decision-making context, the person with the greatest decision-making authority should not be the one with the highest rank, but the person or team with the deepest knowledge and the most complete information about that issue.

The Changing Role of Leaders: The leader's role is no longer "decision-maker," but "context shaper" and "coach." Their job is not to tell subordinates "what to do," but to provide clear "intent" — explaining "why we are doing this" and "what the criteria for success are" — and ensure the team has the resources and information they need. They ask good questions, challenge the team's assumptions, and help them think at a higher quality. They offer advice and support when needed, but leave the final decision to the team.

Former U.S. Navy SEAL officers Jocko Willink and Leif Babin describe this model as "decentralized command" in their book Extreme Ownership. The general's duty is to set the macro intent of the operation; the specific decisions of how to fight in the streets are entirely up to the lieutenants and soldiers on the ground.

Lever Three: A Culture of Tolerance

If the organization cannot tolerate the "valuable failures" that come from delegating decision-making power, then so-called "empowerment" is empty words. Frontline employees will quickly discover that they only have the "right to be right," not the "right to experiment." They will retreat to the safe mode of "always ask the boss for instructions."

Therefore, breaking the evaluation monopoly must be built on the "antifragile" culture we discussed in Chapter Three.

Celebrate "Smart Failures": Openly and conspicuously reward experiments that, while they failed, brought valuable learning to the organization.

Institutionalize "Retrospectives": Establish a "blameless" retrospective culture, turning every success or failure of frontline decision-making into a learning opportunity for the entire organization.

Leaders Lead by Example: Leaders must be the first to admit their own mistakes and uncertainties. If a leader is always "brilliant and infallible," they cannot create a "psychologically safe" environment where subordinates dare to take risks.

Summary: Breaking the Evaluation Monopoly

Breaking the evaluation monopoly and letting those closest to the gunfire make decisions is a profound organizational paradigm shift from "control" to "empowerment." It requires information transparency, contextualized power, and a culture of tolerance.

This is undoubtedly a difficult path. It challenges the sense of authority and control that managers have long been accustomed to. But it is also the only path to the future. Because in an increasingly complex and uncertain world, an organization's intelligence can no longer reside in a single "super brain." It can only exist in a fully empowered, high-speed "distributed neural network."

Does your organization want to be a slow-reacting "centralized empire," or a vibrant, fast-adapting "distributed league of city-states"? Your choice begins with whether you are willing to share the power to define "success."

Section 4: Toolbox 4 — The Essence of OKR: Aligning Goals, Not Quantifying Everything

Once we decide to break the "evaluation monopoly" and delegate decision-making power, a major challenge immediately emerges: how do we ensure that these hundreds of empowered, autonomous "Handu Yishe teams" do not become a pile of loose sand? How do we ensure that their "distributed" efforts converge into a powerful, unified force?

In other words, how do we achieve both "autonomy" and "alignment" in an organization of thousands of people?

This is precisely the problem that KPIs tried to solve but ultimately failed at due to their rigid "control" nature. We need a new tool — one designed specifically for "empowerment" and "alignment."

That tool is OKR (Objectives and Key Results).

OKR was invented by former Intel CEO Andy Grove and later introduced to Google by early investor John Doerr, spreading globally with Google's enormous success. However, like KPIs, OKR has been subject to much misunderstanding and misuse in its dissemination and application.

Many companies simply treat OKR as a "trendy version of KPI." They change the headings on the spreadsheet, but the underlying top-down, bonus-linked "control" logic remains exactly the same. The result is, naturally, old wine in a new bottle — or worse, because OKR setting is often more complex, it leads to even greater management confusion.

To truly harness the power of OKR, we must understand its often-overlooked but crucial essence. John Doerr, in his book Measure What Matters, summarized it with a simple formula:

OKR = Objective + Key Results

Behind this formula lies a deeper philosophy: the soul of OKR lies in the "Objective's" inspiring and directional nature; its skeleton lies in the measurability and verifiability of the "Key Results." More importantly, the ultimate purpose of OKR is not "evaluation," but "alignment" and "communication."

The Fundamental Difference Between OKR and KPI: From "Passive Control" to "Active Alignment"

Understanding these fundamental differences, we can begin to learn how to properly set and use OKR, making it the ideal companion for "delegating evaluation rights."

How to Set a Good OKR?

A good OKR is like two sides of the same coin, both indispensable.

O (Objective): Answers "Where do we want to go?"

Nature: An Objective must be qualitative, inspiring, and challenging. It should be a "battle cry" that ignites the team's passion, a "North Star" that everyone can look up to when lost.

Bad O: "Increase quarterly sales by 15%" (this is a KR, not an O), "Complete the XX project development" (this is a task, not a goal).

Good O: "Create an onboarding experience that users love," "Become the recognized best employer in our industry," "Win the decisive battle against our number one competitor this quarter."

KR (Key Results): Answers "How will we know we are getting there?"

Nature: Key Results must be quantitative, measurable, and verifiable. They must be specific, time-bound, and their completion must be an objective, indisputable fact.

A good KR must pass the "one-sentence test": at the end of the quarter, anyone can unambiguously answer "did we achieve this KR?" (yes or no) and "what was the completion rate?" (0-100%).

Bad KR: "Improve user satisfaction" (how to measure?), "Optimize product performance" (to what extent?), "Build relationships with more partners" (how many is "more"?).

Good KR: "Increase new user day-1 retention rate from 30% to 40%," "Reduce average page load time from 3 seconds to 1.5 seconds," "Sign annual agreements worth over $1 million with 3 top channel partners."

A complete, good OKR example: O: Launch a disruptive new version that redefines the industry standard for "ease of use." KR1: Increase new user first-operation success rate from 60% to 90%. KR2: Increase Net Promoter Score from 20 to 45. KR3: Obtain positive, in-depth coverage from at least 5 major industry media outlets.

Implementing OKR: A Continuous Cycle of "Dialogue" and "Alignment"

Setting good OKRs is only the first step. The true power of OKR lies in its continuous implementation process throughout the quarter. This process is essentially a cycle of "top-down" goal-setting and "bottom-up" path-exploration in dialogue and continuous alignment.

Step One: Set Company-Level OKRs (Top-Down, Providing Direction)

Before each quarter begins, the company's top management sets and announces 3-5 of the company's most important OKRs for the quarter, based on the annual strategy.

These OKRs provide a clear, shared "North Star" for the entire organization. They tell everyone: "This quarter, as one team, these are the most important battles we need to win."

Step Two: Set Team-Level OKRs (Top-Down Alignment, Cross-Functional Coordination)

After the company-level OKRs are released, each department and team holds their own OKR-setting meetings.

Their task is not to passively "take on" indicators from above, but to proactively think: "To support the company's most important Objectives, what unique contribution can our team make?"

Teams draft their own team-level OKRs from the bottom up. About 50% of these OKRs should support the company-level OKRs, while the other 50% can be goals defined by the team itself as important.

In this process, "horizontal alignment" is crucial. Interdependent teams — product, engineering, marketing — need to sit down together, discuss and align their OKRs, and ensure their goals are synergistic, not conflicting.

Step Three: Set Personal OKRs (Optional, Inspiring Individuals)

After team-level OKRs are finalized, some companies encourage employees to set their own personal OKRs.

Personal OKRs are not for managers to micromanage employees' tasks. They are for helping employees think: "How do my personal growth and contributions align with my team's and the company's goals?"

Step Four: Continuous Follow-Up and Review (Through the Quarter, Dynamic Adjustment)

OKRs are not documents to be set and shelved. They are a "living" management tool.

Weekly team meetings should have "reviewing OKR progress" as the core agenda. The team examines the completion rate of each KR, discusses obstacles encountered, and dynamically adjusts the next action plan.

At the end-of-quarter review meeting, the team scores each of their KRs (usually 0-1.0) and conducts a "blameless" retrospective: What did we do well? What did we learn? How can we improve next quarter?

How OKR Empowers the "Delegation of Evaluation Rights"

Now, let us return to the core of this chapter. How does the OKR tool perfectly serve the goal of "breaking the evaluation monopoly"?

1. It separates "Goals" from "Tasks": Company leadership and managers set clear "Objectives" (where to go), but leave "how to get there" (specific tasks and paths) entirely up to the front-line teams to decide. This provides maximum autonomy for "distributed decision-making."
2. It provides a common language for "Alignment": Transparent OKRs are like a company-wide "strategy map." Any employee can clearly see what the CEO and other teams are working on, and how their own work fits into the big picture. This means "collaboration" no longer relies on layers of approval and meetings, but can be based on shared goals, with spontaneous, peer-to-peer communication and alignment.
3. It encourages "Stretch" and tolerates "Failure": OKR's decoupling from compensation, and its encouragement of "stretch" goals (70% completion considered success), institutionally create space for "valuable failure." Teams dare to set difficult, aspirational goals without fear of punishment for not achieving 100%.
4. It shifts the focus of evaluation from "individual performance" to "team contribution": OKRs are primarily set and evaluated at the team level. This guides people from "how to make my performance look better" to "how to help my team collectively achieve the goals we committed to together."

Summary: Toolbox

OKR is not a simple performance management tool. It is an organizational philosophy about goals, alignment, and autonomy. It is the "baton" in the symphony of "delegating evaluation rights."

With clear and inspiring "Objectives," it points the distributed fleet toward a common destination. With objective and measurable "Key Results," it provides each ship with a dashboard to calibrate its course. With transparent and continuous "dialogue," it ensures the entire fleet, though each sails independently, forms a powerful and cohesive formation.

When your organization truly masters the essence of OKR, you will possess an "operating system" that can both grant individuals maximum freedom and unite them into a powerful whole. Within this system, evaluation rights will no longer be a monopoly of the few, but a compass in the hands of every creator to define and achieve success.