Brand guideline and digital design system: two different things
Guidelines state how the brand should look, while the digital design system ensures it always appears that way across all screens.
Yes, you still need both, as they solve different problems. The identity guidelines are documents for people to read and interpret, while the design system is the machine-readable version of the same identity, for the technical team to use directly in code. In short: guidelines describe the correct state, while the design system maintains that correct state without anyone needing to remember and recreate it manually.
- there are digital products and each team interprets the guidelines in their own way
- want to change a color or font in one place, the entire system updates accordingly
- a design and technical team looking at two different source standards
- no digital products yet, only publications and social media
- Guidelines are not finalized yet.
This is the question Sinh Vũ encounters most frequently when consulting on the A3 service. You have put effort into creating a polished brand guideline, packaged it nicely, and then wonder: what more is there to the design system that needs to be done? The straightforward answer is: these two serve different audiences, and lacking one will dilute the identity when applied to digital products.
Guidelines and digital design systems what's the difference
The identity guidelines are a language document: it explains what the primary color is, how the font is used, where the logo appears and where it does not. The readers are designers, marketing personnel, and printing partners. They read, understand, and then interpret.
A digital design system is a technical document: it translates the brand identity into values that computers can read. Color is no longer "dark warm blue" but a specific token (value code). Font is no longer a font name but a variable called in code. The users are developers and digital designers. They do not need to read; they need to inherit directly.
Identity guidelines belong to the language and principles layer for people. The digital design system belongs to the execution layer: tokens, components, interactive documents. The same identity serves two different types of users.
Alla Kholmatova, Design Systems (Smashing Magazine)
Why is a guideline PDF not enough for digital products?
The issue is not with the quality of the guidelines. The problem lies in the execution mechanism. When developers take a PDF file and manually input colors into the code, small errors occur at each step. Accumulated over many screens, components, and updates, the actual interface gradually deviates from the original identity. No one intentionally makes mistakes, but without an automated mechanism, errors are inevitable.
Design tokens are the single source of truth for colors, fonts, and spacing. When you want to change a primary color, you only need to edit the original token, and all places inheriting that token will update accordingly, without missing any spots. Guidelines do not have this mechanism because guidelines do not run in code.
A brand looks good on paper but fades when it comes to digital products if there is no automated execution mechanism. The guideline describes the correct state. The digital design system maintains that correct state.
Sinh Vũ, method A3
When to need to do it, when not needed yet
Should create a digital design system when:
- Do you have a digital product, website, or application that is currently running?
- The design and programming teams are interpreting the guidelines differently, leading to an inconsistent interface.
- Each time an identity update requires manual changes in many places, it takes time and is easy to overlook.
- The team is growing larger, with many people working on the interface.
No need when:
- Without any digital products, the main activities are printing and social media. At this stage, guidelines are sufficient.
- The guidelines themselves are still changing, and the identity is not finalized. It is advisable to stabilize the identity first; otherwise, tokens will need continuous revisions.
Common mistakes when confusing two things
- Paying for guidelines does not automatically mean you have a usable system in code. This is the most common misunderstanding Sinh Vũ encounters.
- Export guidelines as a beautiful PDF, but developers still have to measure colors and spacing by eye each time they need to use them.
- Creating a digital design system when the original identity is not stable. Tokens that need constant adjustments according to the identity will double the costs while results remain unstable.
The viewpoint of Sinh Vũ
If you have good guidelines and are operating digital products, the next step is naturally to integrate that identity into the digital design system so the technical team does not have to interpret it themselves. Sinh Vũ calls this service A3: taking the existing identity, casting it into tokens and components for the programming team to inherit directly.
If you do not have a complete guideline, Sinh Vũ can start from scratch: review the current identity in the discovery phase, or consult to create A1 and A2 first to establish a solid foundation, then move on to A3. It is not advisable to reverse that order.
Decision checklist
Topic: If there is already a brand guideline, is a design system still necessary. 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
Alla Kholmatova, Design Systems (Smashing Magazine). Design Tokens Community Group (W3C). Sinh Vũ, service document A3 Digital design system.
Frequently asked questions
If you only export the guidelines as a nice PDF file, can developers not use it?
Developers can still use it, but they must visually measure colors, spacing, and fonts each time. This means each person interprets a bit differently, and cumulatively, the interface on the web and app will gradually deviate from the original identity. A digital design system precisely addresses this issue: developers pull values from tokens without needing to guess.
Can a digital design system be created before the guidelines are finalized?
You should not. If the original identity is not stable, the tokens will need constant revisions with each brand change, resulting in double the effort. Sinh Vũ advises completing the guidelines first or running both tasks in parallel, provided the scope of the identity has been clearly defined.