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 an introductory website and no digital products, then that website is sufficient; a digital design system would be excessive 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 deciding threshold is the level of repetition and the number of teams, not the brand name or company revenue.
- only have one introduction page, no multiple digital products created by the team
- want to standardize colors and fonts first (using a foundational layer of variables, tokens)
- multiple products, multiple teams, with the same interface components being coded in many places
- a technical team with fewer than three members or products without real users
The question that business owners often ask is "do I need it or not," not "what does a digital design system include." That is the right question because a digital design system is not something that is better to have more of. If placed incorrectly, it wastes budget, consumes team time, and then gets neglected.
A question that decides everything
Do you have more than one digital product (application, platform, internal tool), and do you have multiple teams working on the interface?
If the answer is no, then you do not need a digital design system yet. The deciding threshold is the level of repetition and the number of teams, not revenue or how famous the brand is. A beautifully designed introductory website is just a facade. A digital design system only holds value when reused across multiple products; a single facade does not provide that.
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 people: How many people are interacting with the interface? Fewer than three people usually means the digital design system is more cumbersome 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
Choose an introductory website: You only need a page to present your company, services, and project portfolio. There are no digital products, and no multiple teams are developing the interface. This is the right choice for most service businesses, consumer brands, and small creative studios.
Choose the foundational layer of tokens first: You have one or two small digital products and want to standardize colors, fonts, and spacing before scaling up the team. This is the most practical entry point when starting to build the system.
Choose a complete system: Many products, many teams, with the same interface components being rewritten in various places. At this point, the cost of inconsistency has exceeded the cost 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 a product that doesn't have real users, while those resources should be focused on a minimum viable product (MVP).
- Confusing the brand guideline (a document describing brand identity for readers) with the digital design system (a machine-readable version for the technical team to use in code). The two complement each other but do not replace one another.
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
Tick each item that applies or that you can already answer, 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.
Frequently asked questions
My company is quite large, but we only have one introductory website. Do we need a digital design system?
The size of the company is not a deciding criterion. If you only operate an introductory website and do not have many digital products being developed by multiple teams, then a well-structured website is sufficient. A digital design system only holds value when reused across multiple products; a single facade does not provide that.
I already have a brand guideline document, so do I already have a digital design system?
No. A brand guideline is a document for readers that clearly outlines colors, fonts, and logo usage. A digital design system is the machine-readable version of that same identity, for the technical team to use directly in code. The two complement each other but do not replace one another.
I am working on a minimum viable product (MVP), should I build a digital design system in parallel?
Usually not. At the stage of finding product-market fit, a rigid system can slow things down because every product change necessitates a system change. Therefore, focus on the MVP; only when there are real user signals should you consider the foundational layer of tokens first, then move on to a complete system.
This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.