Colour Branding: Why Your Palette Is a Strategic Decision, Not a Swatch Book

Colour is the first thing anybody notices and the last thing anybody can articulate. People do not say "the blue is doing something." They say "it feels right" or "it feels off," and they are usually more accurate than they have any right to be.

Here is what colour actually has to do, and how to build a palette that survives contact with production, hardware, photography and small screens.

Why colour carries so much weight

Colour is pre-verbal. It is processed before the reader has read a word, and it carries association that varies by culture, category and context. It is also the most expensive element of an identity to change, because it appears on everything: the site, the packaging, the signage, the app, the invoice.

And it is the element most often chosen by taste rather than strategy.

The mistake: the swatch board

The swatch board is where palettes go to die. Here is the process we see constantly:

1. Someone finds a mood on Pinterest.
2. Four colours get extracted from it.
3. They are named — "Deep Ocean", "Sunset Coral", "Forest Mist", "Charcoal".
4. They go on a board with their hex codes.
5. Everyone nods.

And then the brand goes to production, and here is what happens.

The primary colour ends up on a website where it fails contrast against the background text. A secondary colour appears in a place where it cannot be read at all. Nobody can find a third colour that is not one of the four, so something gets improvised. Six months later there are eleven colours in the brand, and none of them is wrong on its own.

Build the palette around jobs, not vibes

A palette is not a set of colours. It is a set of roles, and every colour has one.

Here is the structure we use:

The primary. One colour. It is the brand's main signal — used for the logo, the primary button, the key accent. It has one job: recognition.

The secondary. One colour. It supports the primary, typically in backgrounds, secondary buttons and section washes. It should be recognisably related to the primary but not compete with it.

The neutrals. A scale, not a colour. Typically five or six steps from near-white to near-black. Neutrals do the heavy lifting: body text, surfaces, borders, disabled states. Most of a well-designed interface is neutral.

The accent. One optional colour for the rare thing that must interrupt — a sale badge, a warning, a highlight. Most brands do not need one, and the ones that use two accents have a problem they have not noticed.

The semantic set. Success, warning, error, information. These are functionally determined rather than chosen. The interesting decision is whether they harmonise with the brand or deliberately contrast with it. Both are legitimate; drifting is not.

The dark mode set. If you have a dark mode, you need a decided answer, not an automatic inversion. Some brand colours that work on white will not survive on near-black.

So that is roughly eight to twelve defined values. Not four. The number is not the point — the roles are.

The contrast test is not optional

Colour that fails contrast does not look bad. It looks wrong, and most people cannot say why, which makes it easy to argue about and hard to resolve.

The rule: body text needs a minimum contrast ratio of 4.5:1 against its background. Large text (18pt, or 14pt bold and up) needs 3:1. Interface elements and meaningful graphics need 3:1.

We test every foreground/background pairing in the system, not just the primary ones. This is the step that stops the improvised eleventh colour, because the system already has an answer.

There is a second test that matters just as much and gets skipped more often: the palette has to work in one colour. If your identity collapses into an illegible smudge when printed in black and white, it is over-dependent on colour to communicate structure. That happens more often than it should.

Colour and category

Some colour associations are strong enough to override your preferences.

Financial services read blue, grey and deep green. Healthcare reads blue and green, or increasingly white with a warm accent. Premium spirits read black, gold and cream. Food brands reach for red, orange and yellow because they work.

You can absolutely subvert a category colour — it is often the more interesting choice. But subverting deliberately is a strategy. Subverting accidentally because the founder's favourite was terracotta is not.

The useful question is: what colour will a customer expect to see, and are we deliberately doing something different? If the answer is "no, we just like it," you are leaving recognisability on the table for no gain.

Named colours

Every serious brand names its palette, and the names do real work internally. "Brand Blue 600" is a production instruction. "Deep Ocean" is a vibe.

Use both. The descriptive name is what designers and internal teams use in conversation. The functional token — blue-600, surface-raised, text-muted — is what goes in the CSS and the design system, because it survives the palette changing.

This is the difference between a colour palette and a colour system. The system is what makes the eleventh colour impossible, because there was always a right answer available.

Accessibility is a design argument, not a compliance one

Here is a reframe that changes how teams handle contrast: accessible colour does not constrain you, it extends your range.

A palette with six neutrals and a tested primary gives you dozens of usable combinations. A palette of four colours with no defined roles gives you two, and then you improvise. Accessibility forces the discipline that produces a more flexible brand anyway.

We also make sure the palette survives greyscale, low-end phone displays, and the slightly-yellow cast of cheap LED signage in a retail environment. If it works there, it works everywhere.

Practical steps for a palette today

1. Write down the roles before you pick colours. One primary, one secondary, a neutral scale, an accent, semantics. If a role has no colour, that is a gap.
2. Define neutrals as a scale. Six steps, from near-white to near-black, with a defined use for each.
3. Test every pairing. Foreground against background, at the sizes you actually use. Record the ratios.
4. Test in greyscale. The structure must survive.
5. Test on the worst display you care about. An old phone in a bright room is a fair test.
6. Write the tokens down. Named colours for conversation, functional tokens for code.
7. Check the dark mode answer. Decide it now or decide it deliberately later — do not let it happen by accident.

Colour is one of the highest-leverage parts of a visual identity system, and it is the part most often decided in a single meeting by whoever is most confident about hex codes. If you want it decided properly, with the accessibility testing and the token structure included, that is a conversation worth having.