Member-only story
When not to call a Blue a Blue — functional colour names for Design Systems

As a contractor, I frequently work with different companies and teams which included some good designers. However, regardless of where each design team might be in terms of skill level, as soon as you start handling multiple designs, organising all the elements between them starts to get tricky.
This is where most people start thinking about organising a design system to follow, a part of which is the colour pallet. This is used to help ensure visual and semantic consistency throughout the project and facilitate both design and development (thank goodness for variables).

Most of the times I’ve seen this style guide take a shape like the one on the side here.
This might seem like the logical way of organising your pallets, but, as I’m about to argue, it comes with its own set of problems.
Why is this a problem?
“But Goncalo, surely it’s alright to name a blue colour ‘Blue’? What else would I call it?”
That is a fair point, so let’s see where that leads by doing a hypothetical project, as a thought experiment.