Why Design Systems Matter: Boost Efficiency and Collaboration in Product Development

Why We Need Design Systems

Design systems have become essential as the internet matures into core infrastructure, driving rapid B2B growth, cost‑reduction pressures, and open‑source collaboration.

External Environment Changes

China's 14th Five‑Year Plan fuels digital economy growth, creating massive B2B and B2G demand.

Economic tightening forces companies to cut costs and improve efficiency.

Open‑source ecosystems encourage major internet firms to release their design systems, improving product development processes.

User Survey on Design Systems

Over 100 designers and front‑end engineers were surveyed. About 60% of teams are building a design system, 20% have completed and are using it. Nearly 40% of contributors are designers or front‑end engineers, and 16% include product staff. 94% believe design systems improve collaborative productivity.

Real‑World Cases from Alibaba

Alibaba's Fusion Design and Ant Design support hundreds of business lines, increasing designer efficiency by 50% and development efficiency by 30%.

Value of Design Systems

For Companies: Acts as a product foundation and engine for rapid iteration, optimizing production flow and reducing costs.

For Design Teams: Core capability and asset that elevates team influence and becomes a strategic business asset.

For Designers: Enables systematic thinking and is a critical skill for career development.

Three Types of Design Systems

System‑level: OS‑ or browser‑level guidelines that evolve with hardware and technology.

Domain‑level: Solutions for a specific domain, providing shared standards and scalable experiences.

Business‑level: Precise design and engineering guidance tailored to business logic, improving efficiency and reducing waste.

Domain‑Level Example: AWS CloudScape

AWS CloudScape offers 67 components across 10 categories and 35 patterns, providing reusable solutions for complex scenarios and demos for low‑code implementation.

How to Build a Design System

Two main approaches:

Domain‑level construction: Leverage existing component libraries, then abstract industry‑specific components and patterns.

System‑level construction: Focus on mobile scenarios, directly create business‑level assets, and adopt open‑source systems from Alibaba, ByteDance, Tencent, etc.

When to Start Building

Stage 1 – Design Unification: Define design principles, style, basic components, and patterns.

Stage 2 – Design Engineering: Co‑build component libraries with development, create code assets, and centralize management.

Stage 3 – Design Online‑ization: Use low‑code engines to build online tools, embed code assets, and lower usage costs.

Three Phases of Design System Construction

0‑1 Product Build: Apply design‑system thinking to new products; later suggest system construction once the foundation is set.

Newly Launched Product: Coordinate with engineering during iteration to build the system alongside product development.

Legacy Product: Wait for a suitable opportunity; invest when ROI justifies the effort.

Evolution of Designer Roles

From early “graphic artists” to modern “experience designers” and “architecture designers” who focus on system construction, asset management, and design operations.

Responsibilities of Architecture Designers

Design System Construction: Research industry domains, build systems, and ensure engineering integration.

Asset Management: Consolidate system assets (components, guidelines, illustrations) and provide ready‑to‑use resources.

Design Operations: Establish efficient workflows, adopt new tools, and maintain smooth hand‑offs between design and development.

Design systems are not just UI kits; they are strategic assets that drive efficiency, consistency, and innovation across products and organizations.