Color systems that scale with confidence
Building a flexible palette that stays coherent across products and platforms.
Claire Smith
Senior Designer
Category
Design
date
length
5 min read
Systems, not swatches
A handful of colours can carry a small project, but as products grow the palette has to work much harder. It needs to cover states, surfaces, and accessibility requirements without turning into an unmanageable list of one off values.
The solution is to think in systems rather than swatches. Defining roles such as surface, text, and accent, then mapping tokens to those roles, lets the same underlying decisions scale from a single button to an entire design language.
Naming with purpose
Naming is where a good system earns its keep. Semantic names that describe purpose rather than appearance mean you can adjust the palette later without rewriting every screen, because the intent stays stable even as the value changes.
Accessibility should be built into the system, not bolted on afterwards. Checking contrast as you define each pairing ensures the palette is usable for everyone from the start, and saves painful retrofits once the product is live.
