Red Test

I once worked with someone who had spent time at Bridgewater, and what stuck with me was a habit they carried: the Red Test. Teams were evaluated on how well they spoke clearly about and acted upon what was Red, Yellow, or Green.

Bridgewater is famous for radical transparency to the point of discomfort. Transplanting one of their habits into a normal team was a little like borrowing a recipe from a restaurant kitchen and cooking it on a camping stove. The ingredients were the same. The heat was different. Most teams do not have institutional permission to be blunt, so the practice only worked when the room decided, on its own, to let it.

You can swap in words (On Track, At Risk, Off Track), but colors carried more weight. A single slide turning Red changed the air in the room before anyone said a word.

The slide template never changed. Three columns. Status in bold at the top. A short summary underneath. Yellow almost always came with an extra bullet, a small paragraph explaining why the problem was contained. Green stayed clean. Red stood alone.

What mattered was what happened after the label landed.

In one planning meeting a project manager marked her workstream Red. No hedging, no softening. Just Red, in the same font as everything else. The room went still for a second. A few people shifted in their chairs. Someone closed their laptop halfway, then opened it again.

The question arrived without being spoken.

Would the team treat this as useful information or as a failure of competence? Would someone take ownership of the fix and clear her calendar, or would the next three meetings revolve around how this affected the forecast and what it meant for her review?

I’ve also seen what it looks like when Red doesn’t get named. A project drifted from contained risk to obvious trouble over the course of a few reviews. The status stayed Yellow. Each week the explanation grew longer. Dependencies were “in progress.” Risks were “being monitored.” The color on the slide and the weight in the room stopped matching.

The Slack thread after the meeting stayed polite and thin. A few thumbs up and one “thanks for the transparency.^[1]” No follow-ups. No urgency. By the time the status finally turned Red, the conversation was not about how to fix it. It was about why no one had named it sooner.

Some companies praise early risk in theory and reward clean execution in practice. Performance reviews celebrate predictability. Promotions follow on-time delivery. Under those conditions, Yellow becomes a strategy. Red becomes a bet.

In other environments, Red signals that the system is working. The Slack thread fills with offers to help. Calendars move. The person who raised it does not spend the next month proving they are still competent.

Even then, the balance is fragile. One team treats every Red as an emergency and exhausts itself in permanent escalation. Another grows accustomed to Red until it blends into the background. Transparency without prioritization turns into noise. Judgment withheld until it is convenient turns into theater.

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

And somewhere in the room, before the slide advances, someone is deciding what color to use, scanning the table to see which answer they can afford.