How Youzan Merges Functional Teams and Feature Teams for Agile Collaboration

Background

Traditional functional organizations group people by specialty (e.g., product, sales, service). While this yields clear expertise, rapid market changes in the internet era demand a more flexible, end‑to‑end delivery model. The article describes a hybrid approach that combines long‑living functional teams with cross‑functional Feature Teams (FT) organized as virtual layers.

Problems with Functional Organization

Team expansion raises coordination cost and slows response

As functional teams grow, a single backlog becomes massive. Coordinating planning and evaluation across roles incurs high overhead, and urgent projects often wait for scarce resources, degrading business responsiveness.

Ad‑hoc project groups lack long‑term goal awareness

Temporary project teams focus on immediate deliverables. When members rotate, the broader business purpose of the work becomes unclear, leading to fragmented outcomes.

Departments prioritize internal goals over overall business objectives

Functional departments tend to optimize for their own daily work, overlooking cross‑departmental issues and providing insufficient support for shared initiatives.

Feature Teams (FT) Overview

When is a Feature Team appropriate?

Highly competitive markets that require rapid response to change.

Unexplored domains where innovation and experimentation are needed.

Large, cross‑functional initiatives with long decision‑making chains and bottlenecks.

Definition

Feature Team is a long‑living, cross‑functional, cross‑component team that delivers end‑to‑end customer features.

The goal of FT is to maximize response speed, minimize dependencies, and reduce collaboration cost. In practice, Youzan builds multiple FT layers: a business‑level FT that behaves like a startup team, and a product‑research FT that focuses on specific product modules and is configured in an internal efficiency platform.

Hybrid Virtual‑Real Team Model

1. Align business goals; functional teams act as expertise back‑stop

FT OKRs are derived from the overall business OKRs, ensuring that every FT member is accountable for the same high‑level objectives. Functional teams (e.g., product‑research, sales, service) concentrate on deepening professional capabilities, preventing bottlenecks caused by a single specialty.

2. Self‑organization within FT

During each iteration FT holds retrospectives, gradually establishing its own conventions, culture, and best‑practice documentation. Successful practices are propagated by product managers to other teams, reducing the sense of a temporary project group and lowering communication overhead.

3. Planning and communication mechanisms

FT members work full‑time on FT tasks, accepting lower overall utilization in exchange for higher response speed. Monthly planning is retained but scoped inside the FT; projects that depend on external resources are flagged, centrally coordinated, and only scheduled when FT capacity permits.

4. Shared‑resource decision group

Resources such as designers or middle‑platform engineers are contested by multiple FT. A higher‑level decision group—typically composed of business leaders and functional team leads—coordinates resource distribution, establishes regular communication, and aligns planning to reduce ad‑hoc coordination.

Conclusion

The key trade‑off is between “using people to get things done” and “empowering people to get things done.” A hybrid model that couples virtual, business‑oriented FT with professional functional teams improves agility while preserving deep expertise. Organizations should assess their own scale, market pressure, and decision‑making latency to determine the most suitable structural optimization.