Trust in radical truth and radical transparency

Radical transparency means that reasoning is visible enough for others to examine, question, and learn from — at Bridgewater this extended to recording meetings and making them broadly available inside the firm, so people could see exactly how and why decisions were reached rather than hearing a filtered summary after the fact. The point was never exposure for its own sake; the point was error-correction at a speed that private, filtered communication can't match.

Most organizations run on a quieter, more corrosive system: people say one version of their view in the room and a different, more honest version afterward in private. That gap between the public and private view is a form of dishonesty, and it's expensive — it wastes the group's collective intelligence, breeds cynicism, and lets bad decisions survive because nobody with real concerns raised them where they could actually change the outcome.

This only works with real structure around it. The norm has to be attacking problems and ideas, never the person raising them, and feedback has to be specific and evidence-based rather than either vague praise or personal criticism. Done well, this kind of transparency actually reduces fear inside an organization, because there's less hidden politics to navigate and less energy spent guessing what people really think.

The payoff, when the culture holds, is what I call an idea meritocracy: the best idea wins because it survives open scrutiny from people with the standing to challenge it, not because it came from the most senior person in the room. And because the reasoning behind every major decision is visible rather than assumed, people trust the outcome even when they personally disagreed with it — which is a very different, more durable kind of buy-in than compliance born from hierarchy alone.

One simple rule captures the spirit of it: don't say anything about someone that you wouldn't say to them directly. Transparency still has sensible limits — private personal matters, legal constraints, and information that would cause harm if shared are handled differently — but those exceptions should be rare and explained, not a quiet default that lets the old private-versus-public gap creep back in.