This is the distinction the inspiration boards flatten, and almost every dashboard problem traces back to it. Three colour systems share one screen, each with a different job and a different failure mode.

A brand palette that looks great on a landing page usually supplies one of these — an accent — and none of the other two. That is why the first dashboard screen looks fine and the fifth looks like three products stitched together.

Neutrals carry most of a dashboard, and a thin neutral scale is the single most common structural defect. A dense table needs to separate, at minimum: the page background, the card the table sits in, the header row, the row hover state, the border between rows, primary text, secondary text, and disabled text. That is eight distinguishable values, and "three greys" does not produce them.

Two things make a neutral scale work. First, give it enough steps — nine or so, spaced perceptually rather than by even hex arithmetic, which clusters everything in the middle. Second, tint them. A neutral carrying a small amount of your brand hue reads as part of the design; an untinted grey reads as the framework default, because it is.

Success, warning, danger and info are not decoration. The moment a chart series, a nav highlight, or a marketing banner uses your red, red stops meaning "something is wrong", and users stop scanning for it. This is a one-way door: attention you spend on decoration cannot be reclaimed for meaning.

• Keep them out of the categorical set. If you have four series and one of them is green, that green is now ambiguous on a screen that also shows health status.
• Don't let the accent be a status colour. If your brand is green and green also means success, either the brand or the meaning has to move. Usually the brand: shift the accent's hue or lightness far enough that the two never sit adjacent and read as the same thing.
• Never rely on colour alone. A status needs an icon, a label, or a shape as well. This is an accessibility requirement, and it is also what keeps the interface readable in a screenshot pasted into a support ticket.
• Give each status a surface variant. A danger *badge* and a danger *banner background* are different colours; if you define only one you will get a banner that either shouts or disappears.

Six or seven, and the honest answer is that six is where it starts getting difficult. The constraint is not aesthetic: distinguishable hues at equal lightness are a limited resource, and once about eight of them are on one chart, adjacent series become guesswork and the legend turns into a lookup task.

This is the part a palette generator cannot help with, because the categorical set has to be judged as a group and against the neutrals it will sit on. Below are two dashboard-shaped palettes with their chart-1 through chart-5 roles visible alongside the surfaces — which is the only way to see whether series four is still distinguishable from series two on a card.

Both sets stop at five, which is deliberate rather than a limitation of the format.

What to do instead, in order of preference:

1. Label directly. Put the series name at the end of its line. This removes the legend, removes the lookup, and removes most of the pressure on colour.
2. Group the tail. Show the top five and an "other" bucket. Almost no dashboard reader is comparing series eleven with series twelve.
3. Split the chart. Small multiples — one series per panel, same axes — beat one chart with twelve colours at almost any size.
4. Vary something other than hue. Dash pattern, marker shape, or fill texture, especially in print or when a screenshot may be greyscaled.

Around one in twelve men has some form of colour vision deficiency, and the most common form makes red and green hard to separate — which is unfortunate, because red and green are exactly what dashboards use for bad and good.

The practical rules are short. Vary lightness as well as hue between any two colours that carry meaning, so they remain distinguishable in greyscale. Never pair red and green as the only difference between two states. And for status, always add a second channel — an icon, a plus or minus sign, a word — so the colour is reinforcement rather than the message. A palette that survives a greyscale screenshot survives almost every deficiency.

Dashboards get used in dark mode more than most product surfaces, and a categorical palette tuned for white does not transfer. Mid-tone saturated hues that read cleanly on white tend to vibrate against a near-black background, and the two or three darkest series simply disappear.

Define the series colours per mode rather than converting them. The same is true of your neutral scale: in dark mode raised surfaces are *lighter* than the background, which inverts the instinct that a card is a lighter thing on a tinted page. The specifics — including measured lightness values from shipping palettes — are in dark mode colour palettes that hold up.

Increasingly the dashboard is generated rather than designed — an agent is asked for an analytics screen and produces one. Whatever the brief did not specify, the model supplies, and it supplies it fresh each time.

We sampled 299 public DESIGN.md files, the documents written specifically so a coding agent will follow them. 86% give raw hex values with no semantic role attached, which means the file cannot answer "what colour is a disabled table cell" or "which colour means danger". 69% never mention dark mode. So the agent decides, and it decides differently on the next screen.

The fix is the same whether a person or an agent is building: name the roles, define them in both modes, and write down which colours are reserved. A palette expressed as roles is instruction; a palette expressed as five hex codes is inspiration.

1. 1

   Screenshot the densest table and desaturate it

   If rows, headers, hover and disabled states stop being distinguishable in greyscale, your neutral scale is too flat and your status colours are carrying meaning alone.

2. 2

   Put every status on screen at once

   Success, warning, danger and info together, as badge and as banner. This is where a missing surface variant shows immediately.

3. 3

   Chart eight series on purpose

   Not because you should ship it, but to find where your palette gives up. Whatever number that is, design the "and others" behaviour for one below it.

4. 4

   Toggle dark mode with a chart open

   The two darkest series are the ones that vanish, and they vanish silently.

5. 5

   Count the accent

   On a good dashboard screen the accent appears once or twice. If it is everywhere, it has stopped meaning "this is the action".