Showcase website or digital design system: choose the right one from the start.
The boundary is not about the size of the company but about the level of repetition and the number of teams interacting with the interface.
If you only have a promotional website and no digital products, that website is sufficient; the digital design system will be redundant and at risk of being neglected. A digital design system is only worth investing in when the same interface components are being recreated by many people and teams in various places. The decision threshold is based on the frequency of repetition and the number of teams, not on brand names or company revenue.
- only have one introduction page, no multiple digital products created by the team
- want to standardize colors and fonts first (using the Foundation tokens layer)
- multiple products, multiple teams, the same component is being recoded in many places
- a technical team with fewer than three members or products without real users
The question Sinh Vũ receives the most is not "what does a digital design system include" but rather "do I need it?" This is the right question, as a digital design system is not something that is better to have more of. If placed incorrectly, it wastes budget, takes up team time, and ends up being neglected.
A question that decides everything
Do you have more than one digital product (app, platform, internal tool), and do you have more than one team working on the interface?
If the answer is no, then you do not need a digital design system yet. The decision threshold is based on repetition and team size, not revenue or how famous the brand is. A beautifully designed introductory website is just a facade. A digital design system only returns value when used in multiple places; a single facade does not create that multiplication.
Not every system requires enterprise-level polish. A component-based approach is still good for simple sites, but that does not constitute a complete digital design system.
Brad Frost, Design Systems Q&A
Four factors to check beforehand
- Type of digital product: Do you have a real user application or platform, or just a company introduction website?
- Number of teams and individuals: How many people are interacting with the interface? Fewer than three people means the design system will be heavier than the benefits it brings.
- Repetition level: Are the same interface components being rewritten in many places? If not, a system is not yet needed.
- Stability of the product: Is the product already being used by real users and stabilizing, or is it still searching for direction? In a phase of frequent changes, a rigid system slows down rather than supports.
When to choose which direction
Select a showcase website (P1): You only need a page to present the company, services, and project portfolio. No digital products, no multiple teams building interfaces. This is the right choice for most service businesses, consumer brands, and creative studios in Vietnam today.
Select foundational tokens first: You have one or two small digital products and want to standardize colors, fonts, and spacing before a larger team. This is the most practical entry point when starting to build the system.
Select a complete system: Many products, many teams, with the same interface component being rewritten in multiple places. At this point, the inconsistent costs have exceeded the costs of building and maintaining the system.
Common errors
- Buy a digital design system when you actually only need a simple website, just because it sounds more professional.
- Building a system when the technical team has fewer than three people: there aren't enough people to maintain it, and the system is neglected after a few months.
- Creating a system for products that have no real users, while those resources should be focused on the MVP (minimum viable product).
- Confusing brand guidelines (documents for readers, describing brand identity) with a digital design system (machine-readable documents for the technical team to use in code). The two complement each other but do not replace one another.
Sinh Vũ's viewpoint
Sinh Vũ communicates this boundary clearly with clients from the first consultation. If you only need an introductory page and do not have a digital product yet, we will suggest the P1 website, not the digital design system package. We also decline to build systems when the technical team is too small or the product does not have real users, as the final result will be a beautiful document that no one uses.
When you meet the qualifications, we often recommend starting from the foundational tokens first, standardizing color variables and fonts in the code, and then expanding to the full system according to actual needs. Purchasing the highest level right from the start is often less effective than climbing each level when the organization is truly ready.
In the idea generation or frequent pivot stage, rigid systems can backfire as they slow down progress. It is advisable to start with a lean version once there are signals of product-market fit.
Nielsen Norman Group, Small by Design: The Strength of Lean Design-System Teams
Decision checklist
Topic: When you only need an introductory website instead of a digital design system. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Brad Frost, Design Systems Q&A; Brad Frost, The Design System Ecosystem; Nielsen Norman Group, Small by Design: The Strength of Lean Design-System Teams; practical experience at Sinh Vũ Studio.
Frequently asked questions
My company is quite large, but we only have one introductory website. Do we need a digital design system?
Company size is not a deciding criterion. If you are only operating a promotional website without many products being developed by a large team, then a well-structured website is sufficient. A digital design system only returns value when applied across multiple use cases; a single storefront does not create that multiplication.
I already have a brand guideline, so does that mean I have a digital design system?
Not yet. Brand guidelines are documents for readers, clearly stating colors, fonts, and logo usage. The digital design system is the machine-readable version of the same identity, for the technical team to use directly in code. The two complement each other but do not replace each other.
I am working on an MVP (minimum viable product), should I build a digital design system in parallel?
Sinh Vũ advises against it. At the stage of finding product-market fit, a rigid system can slow you down because every product change necessitates a system change. Focus on the MVP; only when you have genuine user signals should you consider the foundational tokens, and then move on to a full system.