Open Data·Open Metrics
Open Data Waterloo Region · Note

Dashboard Color Best Practices: Make It Mean Something, Not Just Look Nice

July 24, 2026 · Uncategorized

On a dashboard, color is not decoration. It is data. The moment you make revenue green and losses red, you have assigned meaning, and every color choice after that either reinforces the meaning or muddies it. Most bad dashboards are not bad because they lack color. They are bad because they have too much of it, all shouting, none of it saying anything.

The goal is a board where a person can sweep their eyes across it and read the state of things before they read a single number. That only works if color is rationed and consistent. Spend it like it costs money.

Use a restrained palette

Start with a neutral base. Grays, a soft off-white or a dark charcoal, and let that carry almost everything, the frames, the text, the gridlines, the tiles that are simply fine. Neutrals are the silence that makes the one loud note audible. When every tile is a different bright color, nothing stands out, because standing out is a relative thing.

Then add one accent for the thing you want people to notice, and the status colors for good and bad. That is close to the whole budget. A dashboard rarely needs more than a neutral base, one brand accent, and a small semantic set. If a chart has eight categories that each demand their own hue, the problem is usually the chart, not the palette, and the chart type guide can help you pick a form that needs fewer colors.

Keep status colors consistent

Pick what green, amber, and red mean, and never let them mean anything else on the same board. Green is on-target. Red is a problem. Amber is watch-this. The second you use red once for “bad” and once just because it is your brand color, you have taught the reader to distrust the color, and now they have to read every label, which is the exact work color was supposed to save.

Note the discipline of reserving red. If half the board is red, none of it is urgent, because urgency is scarce by definition. A well-colored dashboard is mostly calm neutrals with a few deliberate flashes of meaning.

Design for color blindness

Roughly one in twelve men cannot cleanly tell your red from your green, which is a problem when red and green are carrying the entire message. If color is the only thing separating good from bad, a meaningful slice of your readers are looking at a board that says nothing to them.

The fix is cheap: never let color be the only signal. Pair it with a shape, an arrow, a label, a position. An up arrow next to the green, a down arrow next to the red, and now the meaning survives even in grayscale, even printed, even for the reader who sees both as the same muddy brown. Test it by desaturating the whole board and checking that it still reads. If it does, your color is doing extra work, not all the work, which is exactly where you want it.

Color sits inside the larger craft of making a board legible, so pair this with the pillar on dashboard design and the broader habits in data visualization best practices.

← All community notes