How colour systems survive a rebrand

When a company announces a rebrand, the public sees a new logo. Inside, engineers brace for something less glamorous: finding every place a colour was ever written down.

Teams that have been through it once tend to adopt the same cure, which is to stop thinking in colours and start thinking in roles.

The problem with hex codes

A hard-coded value such as a particular green says nothing about why it was chosen. Is it the primary action colour, a success message or a decorative accent? Over years the same value gets used for all three, and changing one means breaking the others.

Tokens give colours jobs

A design token is a named decision. Instead of using a specific green, a button uses something like the primary action colour, defined once and referenced everywhere.

Tokens usually come in layers. A raw palette holds the available colours. Semantic tokens assign meaning, such as text, surface, border and danger. Component tokens, where needed, tailor those for a particular element.

• Raw palette: the paints on the shelf.
• Semantic tokens: what each paint is for.
• Component tokens: exceptions, used sparingly.

Dark mode for free

Once roles exist, a second theme is another set of values for the same names. The interface does not need to know which theme is active. This is also how teams adjust contrast for accessibility without redesigning individual screens.

Guardrails

Systems decay without rules. Good teams add automated checks that flag colours used outside the token set and test contrast ratios for every pairing that appears on screen.

Naming matters

Names like blue-500 describe appearance and become wrong the moment the brand turns green. Names like action or surface describe purpose and stay correct.

Name the job, not the paint.

Start small

You do not need an enterprise design system to benefit. Define a dozen semantic colours for your next project, use them consistently, and you will thank yourself on the day someone says the brand needs refreshing.