Establishing a Value‑Loop Management Mechanism at Youzan

Background : Youzan operates a product‑technology team of thousands. Without a clear value‑loop management mechanism, information about business goals, operational plans, actual results, and improvement strategies can become fragmented, leading to low organizational efficiency.

The article outlines the need for a systematic approach to ensure that every stakeholder—business owners, product managers, and engineers—has visibility, evidence, and feedback on the value delivered.

Challenge : Simply hiring more people cannot keep up with rapid business growth. The classic “Brooks’ Law” applies—adding staff to a delayed project often does not help. The company needed a way to allocate limited resources effectively while aligning with strategic direction.

Strategy (Section 2):

1. Establish a value‑loop management mechanism tied to semi‑annual OKR setting. This defines quantifiable business objectives and short‑ and long‑term plans, and aligns all stakeholders (market, operations, product, technology, etc.) around them.

2. Value‑loop activities are organized at three hierarchical levels—company, business‑line, and project—and progress through three phases: planning, implementation, and operation.

Company‑level (2.2.1): During the planning phase, product leaders submit the highest‑priority P1 demands each month. These are evaluated on user and commercial value and mapped to OKR. Implementation guarantees that P1 items receive priority resources and cannot be delayed. After launch, the product team tracks expected vs. actual value (at least T+30 days) and adjusts strategies accordingly.

Business‑line level (2.2.2): Product managers prioritize demands based on expected value and coordinate monthly scheduling with technical leads. Implementation follows the scheduled scope, and operation involves market and operations teams executing campaigns, while product managers monitor KPI achievement and conduct regular OKR reviews.

Project level (2.2.3): Product managers define expected value and post‑launch operational plans in the requirement document. Developers implement the feature with necessary instrumentation. After release, market/operations execute activities, collect data, and perform a value review at least 30 days later.

Outlook : The value‑loop mechanism has transformed Youzan’s management model into an OKR‑driven, end‑to‑end value‑flow process. The platform now provides transparent tracking, enabling timely adjustments and resource optimization. Future work includes deeper strategic project management, long‑term value considerations, and stronger incentive and assessment systems.

Additional reading links are provided for deeper insights into OKR‑based project management, agile transformation, and large‑scale demand management.