Why “Happy Work” Is the Core Assumption Behind Ant Design 4.0

Ant Design’s Basic Assumption

Lin Wai begins by asking the audience whether they enjoy their work. Although many respond positively, he points out that work often feels less enjoyable than simply lying down, because the challenge‑skill balance is frequently mismatched.

Three main reasons for work dissatisfaction are identified: (1) work is perceived as serving the boss, (2) reliance on external feedback and the relationship with one’s direct manager, and (3) a mismatch between challenges and skills, leading to anxiety when challenges exceed skills and boredom when skills exceed challenges.

In the digital world, this mismatch is amplified. Early computers solved simple problems, but today’s devices far exceed the capabilities of those early machines, while human memory limits remain unchanged, creating a gap between challenges and skills.

When challenges match skills, work becomes enjoyable—like a game where each level improves abilities, creating a continuous sense of fun and growth. This “happy work” concept becomes the core assumption of Ant Design.

Ant Design’s Design Values

The philosophy splits happiness into two parts—pleasure and fun—and derives four design values: naturalness, certainty, meaningfulness, and growth‑orientation.

Only two values are discussed in depth due to time constraints: certainty and naturalness.

ETCG 2.0: Ant Design’s Design Methodology

ETCG stands for Function Example, Template, Component, and Guides. The methodology upgrades the original ETCG by providing a unified reasoning process for all roles, ensuring consistent solutions across the product.

Templates abstract business scenarios, and template components allow developers to generate complete UI sequences with a single line of code when needed.

The “four tables and one board” framework (lists, tables, charts, forms, and layout) covers over 80 % of enterprise‑level product requirements and is open‑source for community use.

Components have evolved over five years, with nearly 1,000 contributors and 60 % of the top 50 contributors coming from the community, boosting development efficiency for thousands of enterprises.

The two “G” elements are:

Component style abstraction, enabling rapid theme changes (e.g., switching from blue to orange with one line of code).

Guides, which encode interaction rules so machines can assist users by automatically generating appropriate UI elements based on data.

This approach reduces the need for designers in routine product creation, dramatically improving design and development experience.

Making Design More Natural

Natural design is defined as behavior that feels intuitive without conscious effort. Traditional WIMP interfaces require users to remember thousands of functions, leading to cognitive overload.

To address this, Ant Design promotes proactive interactions that surface functions to users automatically, reducing reliance on conscious recall.

Examples include:

Automatic image upload prompts when a large portion of a document is edited.

Context‑aware UI transformations in Alipay’s payment flow.

Proactive services can be invisible to users yet continuously improve the experience, such as virtual keyboards that anticipate intended input.

By distinguishing between active and passive system functions and adding proactive interactions, Ant Design aims to make massive feature sets feel natural and reduce mental effort.

Conclusion

The talk summarized three main points: (1) Ant Design’s basic assumption that everyone seeks happy work, (2) the derived design values—especially certainty and naturalness—and (3) the practical outcomes of these values in component libraries, visual assets, design tools, and proactive services.

Lin Wai thanked the audience and highlighted the open‑source nature of Ant Design.