When not to create a digital design system
There are times when investing in a digital design system is right, but there are also times when doing it early can be more costly than not doing it.
You shouldn't create a digital design system when you don't have a real digital product to apply it to, when the product is still finding its shape and has no users, or when the team is too small and no one is assigned to maintain the system after launch. In those cases, budget and effort should be focused on making the product functional, or standardizing the core identity first. Sinh Vũ proactively advises clients not to proceed when the timing isn't right, because a beautiful system that is neglected is even more wasteful than having no system at all.
- Prioritize product development when there are no real users yet.
- standardizing identity (A1, A2) when the original identity is unstable
- only create a concise token level when not meeting the full system requirements
- a team that is too small and cannot sustain itself after launch
- doing it due to pressure to resemble large companies
- there are no real digital products to apply
Sinh Vũ receives numerous requests for design system consulting from businesses in the brand-building phase. And the honest answer is sometimes: it’s not the right time. Not because design systems lack value, but because implementing them at the wrong time often results in a well-invested system that is left unused. This page helps you recognize specific signs to postpone and prioritize the right tasks.
A digital design system needs a foundation to stand strong
The digital design system (a set of rules and interface components used across all digital products) is not a starting point, but a standardization of things that are already stable. To standardize, there must be something stable enough to standardize first.
This means that if you do not yet have a real digital product, or if you have a product but the interface keeps changing after each round of user testing, then building the system now is standardizing something unstable. The result: the system will need to be redone, or worse, abandoned because it no longer reflects the actual product.
Similarly, if the original brand identity (colors, typography, image tone) is still being adjusted, then any decisions in the system can be reversed. It is advisable to finalize the original identity first, then digitize it.
When should you not create a full system?
Below are situations where Sinh Vũ often proactively advises clients who have not yet activated a complete design system:
- No real digital products. If you only have printed materials, social media, or a purely introductory website, then the digital design system has no place to apply. This is a case where you should prioritize creating the core identity (A1, A2) or the website (P1) instead of A3.
- Products without real users. In the exploratory and testing phase, the interface will change significantly. According to Dan Mall in Practical Design Systems, at this stage, focus on building a real flow and systematizing it later, without rushing to abstract.
- The team is too small and no one is assigned to maintain the system. Nathan Curtis from EightShapes points out that without an owner and a budget for maintenance, the system will become diluted and neglected. If the team consists of only one or two designers working on real projects, the key question is who will update the system, control quality, and train new members. If there is no clear answer yet, it’s best not to fully launch the system.
- Pressure to "look like a big company". This is the most common reason leading to a stagnant system. Big companies have design systems because they have many parallel teams that need coordination. If you do not have that problem, the design system has not solved any real issues for you.
You should prioritize what to replace.
Instead of a full system, consider lighter options that are more suitable for the current stage:
If the original identity is not stable: prioritize standardizing the identity at level A1 (basic identity system) or A2 (expanded). This is the foundation upon which everything else, including coefficients, will be built.
If there are no digital products: Prioritize creating an introductory website (P1) to establish a basic digital presence, rather than investing in a system for products that do not yet exist.
If you want to standardize lightly but do not have the full system in place: only implement at a token level, meaning standardizing colors, fonts, and spacing into common variables, without building a complete component library yet. This is a practical starting point that can be expanded later.
Don't rush to abstract something that isn't stable. Prioritize making the flow functional, and systematize later.
Dan Mall, Practical Design Systems
Common errors when deciding the wrong timing
- Creating a complete design system before having a digital product to apply it to, resulting in a system that stands still and no one uses.
- Ignore the question of who will sustain the system after launch, leading to one-time investment followed by decline.
- Using a design system as a signal of "we take this seriously" rather than a tool to solve specific problems.
- The digitized identity is not finalized, and everything will need to be redone if the original identity changes.
The viewpoint of Sinh Vũ
Sinh Vũ specifies in the comparison section of service A3 the cases where a different direction should be chosen: for a purely introductory website, use P1; if the technical team has fewer than three people, the system risks being neglected; if the product has no real users, focus on developing the product first.
Proactively advising clients not to proceed at the wrong time is not about rejecting opportunities, but about maintaining consulting credibility. Clients investing in the right things for their stage will see real results, which lays the foundation for returning to create the right design system later.
If you are uncertain, the most practical question is: Who on the team will be responsible for maintaining this system after it is completed, and do they have the real time to do it? The answer often clarifies what stage you are in.
Decision checklist
Topic: When you shouldn't create a digital design system yet. 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
Dan Mall, Beware premature optimization (Practical Design Systems). Nathan Curtis, Team Models for Scaling a Design System (EightShapes). Sinh Vũ, service document A3, section Counterpoint and Boundaries.
Frequently asked questions
Should a recently launched startup create a design system immediately?
You shouldn't, unless the digital product has real users and the interface is relatively stable. In the early stages, products often change rapidly: colors, flows, and components can all be disrupted after a few rounds of user testing. Creating a system at this stage means standardizing something that isn't stable, which is likely to require rework. Prioritize establishing a real flow and systematizing later.
If the brand identity is not finished, should a digital design system be developed in parallel?
No. A digital design system is essentially a digitization of established elements: background colors, typography, spacing, and visual tone. If the original identity is still being adjusted, the systematization will need to be redone accordingly, causing double waste. It is advisable to finalize the original identity at A1 or A2 level first, then build the system.
If the team only has two designers, is that enough to sustain the system?
Usually not sufficient if those two people are still running real projects. Maintaining a digital design system requires a clearly assigned person with actual time dedicated to updating, quality control, and training new users in the team. If that cannot be arranged, it is better to start with a compact token rather than a full system.