Every brand changes eventually. The question is whether your product changes with it in a week or in a quarter. After helping several teams through a rebrand, we’ve found the answer is decided long before the new logo arrives — it’s decided by how the design system names things.
Name the intent, not the value
A token called blue-600 is a fact about today’s palette. A token called action-primary is a decision about the product. When the brand moves from blue to green, only one of those names still tells the truth.
We structure tokens in three tiers:
- Primitives — the raw palette, type scale and spacing. Brand-specific, freely replaceable.
- Semantic tokens — surface, text, border, action, feedback. They point at primitives.
- Component tokens — only where a component genuinely needs its own knob.
Components may only consume semantic or component tokens. The day a component reaches for a primitive, you’ve created a place a rebrand will have to find by hand.
Test the system against a fake rebrand
Before launch, we swap in a deliberately ugly alternative palette and a different typeface. If anything in the product still looks “on brand”, it’s hard-coded somewhere. This ten-minute exercise catches more debt than any audit.
If changing the brand colour requires a pull request in more than one file, the system isn’t finished.
What a good rebrand looks like
- New primitives land in a single change, behind a theme flag.
- Semantic mappings are reviewed by design, side by side, in light and dark.
- Illustration, motion and photography guidelines update in the same release — tokens alone don’t make a brand.
A design system is not a component library with nice documentation. It is the agreement that lets a brand evolve without the product falling behind.