Identity guidelines or design system
Two different tools, different problems, not all require both.
Identity guidelines answer the question of what the brand looks like and how everyone can apply it correctly. The design system answers how the product team creates a consistent digital interface across multiple screens. If you do not have software or applications continuously developed by an in-house team, identity guidelines are sufficient; a design system is not yet necessary.
- businesses without digital products only need standards
- software company with multiple teams creating stable interfaces
- startups with an unfinalized interface should use a lightweight standard first
- startups that pivot frequently should not invest in a design system
- businesses without digital products are convinced to purchase a design system
You are uncertain about these two concepts because they seem related, and they actually are. However, related does not mean they can be used for the same problem. Sinh Vũ clarifies from the start so you don't pay for something you don't need yet.
Two tools, two problems
Identity guidelines are a set of rules for using the brand: which colors, which fonts, what spacing, and what tone. They are written for marketing, partners, printers, and external agencies. Anyone who picks them up can apply them correctly without needing to ask again.
A design system is the technical infrastructure for the digital product team to create a consistent interface at scale: a component library (reusable interface elements), design tokens (shared design values in code such as colors, spacing, font sizes), and a synchronization process between designers and developers. It is written for in-house software builders.
Design system: Token
color.primary.default = #1A4F8A, automatically pulled into every button component and header throughout the app. Audience: product designers, front-end developers.
Consideration factors
- Is there a digital product continuously developed by the in-house team? If the website is only created once by an agency and left as is, a design system is not necessary.
- How many people interact with the interface? The design system addresses coordination issues; when there is only one designer, that problem does not exist.
- Is the interface stable yet? If the product is still pivoting, the design system will continuously become outdated before it can generate value.
- Is there a long-term budget? The design system requires regular maintenance; it cannot just be created once and left like a static standard.
When to choose which direction
Standardized identity only: Retail, service, manufacturing, F&B, and education businesses with assets primarily consisting of logos, packaging, signage, printed materials, and introductory websites. This represents the majority of small and medium enterprises in Vietnam.
Standards with design system: software companies, SaaS (software as a service), mobile applications with in-house teams regularly developing features and multiple people building interfaces.
No rush for the design system: Early-stage startup, the interface changes every month, the main user flow is not finalized. Create light standards and a basic Figma library first, wait for the product to stabilize before upgrading.
Identity guidelines must always come first. The design system is derived from the guidelines, not a replacement for them.
What If Design, Brand Guidelines vs Design Systems
Common errors
- Calling a token library or Figma file a "design system" overlooks the process, contribution rules, and synchronization between departments. Tokens are materials, not the entire system.
- A startup invested in a comprehensive design system while the interface changed every month. Result: the entire system became outdated, and the team spent time updating instead of developing features.
- Businesses without digital products may be convinced to purchase a design system when a good static guideline set would suffice.
Sinh Vũ's viewpoint
Sinh Vũ clearly distinguishes these two tasks from the project outline stage. Identity rarely fails due to poor design. It fails because no one knows the usage rules, leading everyone to apply their own styles. The guidelines serve as a set of rules for the team and partners to apply correctly without needing to ask each time.
For clients with digital products, Sinh Vũ offers an upgraded level with a Figma library and components. However, if the team is still small or the interface is not stable, Sinh Vũ is straightforward that a full design system is not yet necessary. A static PDF or a simple internal lookup portal is sufficient for that stage and requires much less maintenance.
The right decision is not to choose the more complex option. It is to choose the right problem you are solving.
Decision checklist
Topic: Design guidelines or design systems, when to need which. Sinh Vũ Handbook, 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
What If Design, Brand Guidelines vs Design Systems. UserQ, Design systems vs brand guidelines. Practical experience from Sinh Vũ Studio.
Frequently asked questions
Can the design system replace brand identity standards?
No. The identity standards come first; the design system is derived from them. The primary colors, proportions, and typography in the standards are the source for the design system to encode into design tokens (shared design values used in code). Skipping the standards and jumping straight to the design system is like building a house without a foundation.
Should an early-stage startup invest in a design system right away?
You shouldn't. When the product hasn't found product-market fit, and the interface is constantly changing, the design system will become outdated before it can be used. Create a lightweight identity standard and a basic Figma library first, and wait for the interface to stabilize before upgrading to a full design system.
Do retail businesses or traditional service providers need a design system?
It is almost not necessary. If the main assets are the logo, packaging, signage, printed materials, and the website created by the agency, a good identity guideline is sufficient. Design systems are created to solve the problem of multiple people building the same software interface, not for printing or marketing.