Expertise

Expertise digital design system

How can design and code be synchronized to avoid discrepancies? A knowledge repository provides evidence for you to make the right decisions before starting.

How can design and code be synchronized to avoid discrepancies? A knowledge repository offers evidence, helping you understand the options and trade-offs before starting.

Should we create it, and when?

8/8 articles

The original question group: does the business really need a digital design system, when is the right time to invest, and when should you wait? This is the first filter to prevent clients from pouring money into a system only to abandon it.

Should we create it, and when?

When does a business truly need a digital design system?

A digital design system is not something every business needs immediately. Sinh Vũ identifies the real signals for you to decide the right timing.

Xem →
Should we create it, and when?

If there is already a brand guideline, is a design system still needed?

The identity guidelines and digital design system solve two different problems. Sinh Vũ analyzes when both are needed and when they are not.

Xem →
Should we create it, and when?

How many digital products are worth investing in a design system?

There is no fixed user threshold for investing in a design system. What matters is the level of repetition and the number of surfaces that need to remain synchronized.

Xem →
Should we create it, and when?

How small does a team need to be for the design system to be neglected?

The issue is not the number of people, but whether anyone is assigned to maintain the system. Sinh Vũ analyzes team models and signs that indicate when to stop.

Xem →
Should we create it, and when?

You should create a design system early or wait until the product stabilizes.

Creating a design system too early can lock in decisions that should not be finalized yet. Creating too late leads to a backlog of interface debts. Sinh Vũ analyzes when to start and at what level.

Xem →
Should we create it, and when?

Costs, time and return on investment when creating a design system

There is no universal number for a design system. Costs depend on the scope, returns come from avoided costs, and both depend on the actual application rate of the team.

Xem →
Should we create it, and when?

Signs that the business is losing money due to a lack of design system

The cost of lacking a system does not appear on an invoice. Recognizing early signs helps you decide the right time to act.

Xem →
Should we create it, and when?

When not to create a digital design system

A digital design system is not always the next right step. This page helps you recognize when to prioritize other tasks first.

Xem →

Choose what to do first.

7/7 articles

Questions about investment boundaries: how far to expand, where to start, what to do first and what to do later. This helps clients avoid the trap of creating something grand with a low usage rate.

Choose what to do first.

Complete the package at once or break it down into smaller phases.

Choosing to create a design system all at once or in multiple phases directly affects the actual usage rate. Sinh Vũ analyzes this for you to make the right decision based on the context.

Xem →
Choose what to do first.

Should you start with tokens or components in the design system?

When building a design system, many businesses wonder whether to create color and typography tokens first or to establish a component library right away. Sinh Vũ explains why tokens should come first and when it is permissible to do both simultaneously.

Xem →
Choose what to do first.

How many components are enough in the design system?

The number of components does not equate to a good design system. Sinh Vũ explains why quality is more important than quantity and how to determine the appropriate scope for your team.

Xem →
Choose what to do first.

Is a pattern library needed in the design system?

A pattern library helps the team solve complex interface situations that repeat without having to rethink from scratch. However, not every product needs to be created immediately.

Xem →
Choose what to do first.

Standards for WCAG compliance that your industry needs to achieve

Most industries only need to aim for WCAG 2.2 level AA. This article helps you determine the correct level to achieve, avoiding waste and legal risks.

Xem →
Choose what to do first.

You should try it on a sample product first before scaling up.

When starting to implement a design system, many businesses want to move quickly, applying it simultaneously across all products. Sinh Vũ analyzes why it is advisable to test a sample product first and when this step can be skipped.

Xem →
Choose what to do first.

Is Storybook or a static file sufficient?

When is an interactive Storybook-style document needed, when is a static file sufficient. Sinh Vũ analyzes based on the nature of the system, not on tool trends.

Xem →

Token and multi-platform.

7/7 articles

The original technical question group that clients still need to decide: how to organize a single source of truth, light and dark, and multi-brand, covering how many platforms. This part determines how long the system can survive and whether it can scale.

Token and multi-platform.

What are design tokens and why do they determine the entire system?

A design token is a named design decision saved as data. Skipping this layer will cause the entire interface system to break when changes are needed.

Xem →
Token and multi-platform.

What is the neutral DTCG JSON token standard and why should it be followed?

Explain the standard token format of W3C, when it is necessary to follow it, and common errors when applying it to real projects.

Xem →
Token and multi-platform.

Light and dark, multi-brand: should it be considered from the start or added later?

The decision to have a structured semantic token from the beginning or to leave it for later directly affects the cost of expanding the design system. Sinh Vũ explains why it is advisable to leave room from phase one.

Xem →
Token and multi-platform.

Only web coverage or both iOS and Android for the design system.

The decision on the scope of the design system: when is it sufficient to just have a website, when should it expand to iOS and Android, and what are the actual costs.

Xem →
Token and multi-platform.

Does the design system align with your team's technology?

Neutral tokens, components adhere to the stack. Understanding this boundary correctly helps avoid delivering a system that no one can maintain.

Xem →
Token and multi-platform.

Transition from the old interface to the new design system without starting from scratch.

Practical guidelines for gradually transitioning from the old interface to the new design system through incremental replacement, without halting products or starting over.

Xem →
Token and multi-platform.

Is Figma Code Connect required?

Figma Code Connect helps Dev Mode display real component code instead of auto-generated code. This page helps you decide whether to set it up and when the right time is.

Xem →

Do it yourself, hire, or hand it over to the team.

7/7 articles

Questions about implementation and handover: build in-house or outsource, use existing platforms or create custom ones, and how to ensure your team can operate independently after handover. The focus is on adoption, not just delivery.

Do it yourself, hire, or hand it over to the team.

Build it yourself or hire a studio to create a design system

When to build an in-house design system, when to hire an external studio, and why a hybrid approach is often the most sustainable.

Xem →
Do it yourself, hire, or hand it over to the team.

Using an existing template or building a design system from the ground up

When to use a pre-built foundation like Material or Carbon, and when to build from scratch. Sinh Vũ analyzes based on each business context.

Xem →
Do it yourself, hire, or hand it over to the team.

How can the team operate independently after the design system handover?

The success of a design system handover is not measured by the launch event, but by whether your team can use and expand it independently.

Xem →
Do it yourself, hire, or hand it over to the team.

Internally, who should own the design system?

The design system needs to have a clear owner; it cannot be communal. Sinh Vũ analyzes three ownership models and helps you choose the right one based on scale.

Xem →
Do it yourself, hire, or hand it over to the team.

How to measure the percentage of the team actually using the design system

Most teams measure incorrectly: they count available components instead of measuring how many products are actually using the system to ship features. Sinh Vũ explains which metrics truly matter.

Xem →
Do it yourself, hire, or hand it over to the team.

Why the team quietly returned to manual work and how to prevent it

When using the right system is more labor-intensive than DIY, the team will DIY. This article points out the root causes and how to make the right path easier than the shortcut.

Xem →
Do it yourself, hire, or hand it over to the team.

How many onboarding coaching sessions does the technical team need to use the design system?

There is no fixed number, but mentoring is the core factor that determines whether the system is used or neglected. Sinh Vũ explains how to calculate the right number of sessions for your team.

Xem →

Management and long-term operations

7/7 articles

Questions about maintaining the system after launch: how to approve changes, versioning, choosing a governance model, and when long-term collaboration is needed instead of hiring for individual tasks. This part determines whether the system will gradually dilute.

Management and long-term operations

How to prevent the system from becoming diluted over time?

The design system cannot live on its own. To avoid dilution, it needs an owner, an approval process, measurement of application levels, and the standard path must be easier than the custom path.

Xem →
Management and long-term operations

The process of proposing and approving RFC changes in the design system

Explain the RFC (request for comment) process in the design system, when it should be applied, and how to choose the appropriate level of rigor based on team size.

Xem →
Management and long-term operations

Choose a design system governance model: centralized, federated, or hybrid.

Centralized, federated, or hybrid: three governance models for design systems, each suitable for different stages and scales. Sinh Vũ analyzes directly for you to choose correctly.

Xem →
Management and long-term operations

Evaluating the version and handling breaking change in the design system.

Guidelines for setting versions according to semantic standards and handling disruptive changes in the design system, including visual disruptions that are often overlooked.

Xem →
Management and long-term operations

When is long-term collaboration needed instead of hiring for individual tasks?

The design system is a living product, not just a completed project. Sinh Vũ helps you distinguish when long-term collaboration is necessary and when hiring for individual tasks is sufficient.

Xem →
Management and long-term operations

What is a reasonable annual maintenance cost for the design system?

Maintaining the design system is a recurring cost that should be considered from the beginning, not an additional expense. Sinh Vũ explains the calculation framework and influencing factors so you can make the right budget decision.

Xem →
Management and long-term operations

Health metrics that need to be reviewed quarterly

A guide to selecting the right metrics to review the health of the design system each quarter: from output to coverage, application levels by team, and execution quality.

Xem →

Industry lens

6/6 articles

Industry-specific questions: while it is a digital design system, banks, e-commerce platforms, SaaS, or direct-to-consumer brands have distinctly different challenges regarding compliance, performance, multi-segment, and campaign rhythm. This lens helps clients identify which group they belong to.

Industry lens

How much do multi-product B2B SaaS need a digital design system?

The investment in a digital design system depends on the number of products, team size, and your product stage, not ambition.

Xem →
Industry lens

The digital design system for banks and e-wallets: compliance and multi-segment.

When facing compliance and multi-segment issues, how should digital banks and e-wallets build their design system? Sinh Vũ explains from the token layer to governance.

Xem →
Industry lens

What do marketplaces and e-commerce websites prioritize in the digital design system?

For sales platforms and websites, the digital design system needs to cover the most frequently repeated blocks in the purchase funnel, not just create as many components as possible.

Xem →
Industry lens

How flexible does a D2C brand's design system need to be for high campaign rhythms?

Direct-to-consumer brands operate on continuous campaigns. This article shows you how to build a design system flexible enough to change its appearance seasonally without breaking the foundation and the order flow.

Xem →
Industry lens

How should a multi-brand group using a common codebase organize its system?

When many brands use the same source code, the organization of the design system determines whether it remains consistent after two years or turns into chaos. Sinh Vũ explains the architecture and suitable team models.

Xem →
Industry lens

When only an introductory website is needed instead of a digital design system

Not every business needs a digital design system. Sinh Vũ helps you define the right boundaries to avoid over-purchasing or missing out.

Xem →