Red Test

The slide template never changes. Three columns, bold status at the top.

Green usually fits on one line.

The work is on track. The date still holds. Nothing needs deciding.

Yellow needs more room. The status appears at the top, followed by a sentence explaining that the risk is contained, then another explaining the mitigation, then maybe a bullet about the dependency that should clear by Friday. The project may be in trouble, but the slide is already making the case that nobody should react too strongly.

Red rarely needs an explanation. Everyone knows what it means, which is why people avoid using it.

I learned this as the Red Test from someone who had spent time at Bridgewater. Teams were constantly and regularly evaluated on how clearly they spoke about and acted upon what was Red, Yellow, or Green.

Bridgewater is/was famous for radical transparency to the point of discomfort. Most companies don't have the same institutional permission to be blunt. The test worked only when the people in the room believed that naming a problem would improve their chances of solving it.

A status color measures two things at once: the condition of the work and the cost of describing that condition accurately.

That makes Yellow unusually useful. It records the existence of risk without requiring anyone to absorb it. The owner has technically raised the problem while preserving the possibility that it resolves without escalation. The rest of the room gets to acknowledge it without owning any part of it. Everyone has now been informed. Nobody has yet been forced to change a plan.

Red removes that option.

In one room, the first question is what needs to change. A deadline moves. Scope gets cut by someone with authority. The status has done its job by forcing the project and the surrounding plans to adjust.

In another room, the questions point backward. When did the owner first know? Why wasn't this raised sooner? Was the original plan realistic? The project may still receive help, but the person who named the problem now has a second problem to manage.

People learn the difference quickly.

I've seen projects drift from contained risk to obvious trouble over several reviews while the status stayed Yellow. Each week the explanation grew longer. Dependencies were "in progress." Risks were "being monitored." Mitigations were "underway." The color on the slide and the weight in the room stopped matching.

The Slack thread afterward stayed polite and thin. A few thumbs up and one "thanks for the transparency.^[1]" No changed deadline or evidence that the information had altered anyone's plan.

By the time the status finally turned Red, the conversation had shifted from how to fix the project to why nobody had named the problem sooner.

In some companies, Red quietly follows the person who raised it into their next evaluation. The slide moves on, but the association doesn't. After a while, people learn which problems can be named and which ones need to be managed until they're too visible to deny.

In other companies, Red signals that the system is working. Calendars move. Threads fill with offers to help. The person who raised it doesn't spend the next month proving they're still competent.

Red can become useless in other ways. Some teams treat every Red as an emergency and exhaust themselves in permanent escalation. Others use it so often that the label stops changing anything. A useful Red has to be safe to raise and difficult to ignore.

The slide template never changes. Three columns. Bold status at the top.

What changes is what people have learned to expect after a color goes up.