I used to use red. Every quality dashboard I built had the standard traffic-light system — green for good, amber for warning, red for bad. It is the universal language of performance reporting. Everybody understands it. And it is one of the most destructive design choices I ever made in a quality system.

It took me about ten years to figure out why.

What red does to people

I was in a management review meeting presenting supplier quality data. One supplier had gone red — their PPM had spiked three months in a row. I put the slide up and the procurement director immediately went into defence mode. "That supplier had a tooling issue, it is resolved, the data is lagging." The plant manager jumped in. "Why are we singling out one supplier? The overall trend is positive." Within two minutes, the conversation was not about the supplier problem. It was about the colour on the slide.

Red does not start conversations. It ends them. Red triggers a threat response. People stop thinking analytically and start thinking defensively. The discussion shifts from "what is causing this and what do we do" to "why is this red and whose fault is it." I watched this dynamic play out in meeting after meeting, in company after company, for years before I understood what was happening.

Red does not communicate urgency. It communicates blame. And blame is the enemy of problem-solving.

The experiment

I was setting up the quality reporting system for a 900-employee greenfield plant and I decided to try something. I kept the data identical. I kept the thresholds identical. But I replaced the traffic-light colour scheme with a single design choice: every metric was blue, and deviations were marked with a small arrow and the actual number. No red, no green, no amber. Just data, presented neutrally, with the trend visible.

The first management review was a revelation. When the slide showing a supplier PPM spike came up, nobody went into defence mode. The procurement director leaned forward and said "what happened in week twelve?" The plant manager asked about containment. The conversation lasted twenty minutes and ended with an action plan. Same data. Same problem. Completely different response.

The colour had been the problem. Not the metric, not the data, not the presentation. The colour.

What I use instead

I am not suggesting you hide bad news. I am suggesting you present it in a way that invites inquiry rather than defence. Here is what I have settled on after fifteen years of iteration:

Show trends, not thresholds. A metric that crossed a threshold is less informative than a trend line that shows the direction and rate of change. Trends tell stories. Thresholds tell you nothing except that an arbitrary line was crossed.

Use neutral colours with clear annotations. Blue for everything. When a metric deviates, mark the deviation with a label — not a colour. "Target: 50 PPM. Actual: 180 PPM. Cause: tooling wear, corrective action in progress." The annotation carries the meaning. The colour carries the emotion. You want the meaning without the emotion.

Separate the metric from the judgement. A number is not good or bad. A number is a number. The judgement — "this is unacceptable and requires action" — should be expressed in words, not in colours. Words invite discussion. Colours trigger reflexes.

Always pair deviation with context. When a metric moves, show why. If you do not know why, say so. A dashboard that shows a red light with no context is a dashboard that generates fear and no action. A dashboard that shows the same data with a brief note — "investigation underway, suspected root cause: raw material variation" — generates collaboration.

The cultural cost of red

The deeper problem with red is cultural. When people know that a red metric triggers a painful conversation, they start optimising to avoid red. They negotiate looser thresholds. They reinterpret data. They delay reporting until the metric recovers. The dashboard becomes a political instrument rather than an operational one.

I have seen plants where the quality metrics were almost entirely green, and the customer complaint rate was climbing. The metrics were green because the thresholds had been set so generously that everything passed. The thresholds had been negotiated downward over years by people who were tired of defending red numbers in management reviews. The dashboard had become a lie, and the colour system was the mechanism that made lying rational.

Stop using red. Use data. Use words. Use trends. The conversation you get will be different, and the quality system you build on that conversation will be better. Twenty years of dashboards taught me this. The colour was never the point. The conversation was always the point. Design for the conversation, not the colour.