How to Build a Team's Collective Judgment, Not Just Each Individual's
A team of individually excellent engineers does not automatically add up to a team with good collective judgment. Judgment built in isolation stays trapped in each person's head unless something deliberately connects it to everyone else's.
Individual judgment and collective judgment are not the same thing. One engineer’s hard-won experience from a specific project, the kind that takes years to build, stays locked to that person unless something deliberately moves it into the team’s shared understanding. Nothing about working near other engineers automatically transfers what any one of them has learned.
What happens without deliberate connection
Left to itself, each engineer independently rediscovers similar lessons on separate projects, sometimes years apart, because nothing carried one person’s hard-earned insight to the others who could have used it earlier. The organisation pays for the same lesson to be learned multiple times, by multiple people, when it only ever needed to be learned once.
The actual mechanism
Judgment becomes collective through a specific pathway, not through proximity or good working relationships alone. An individual’s experience gets shared and discussed thoroughly as a lesson learned, and critically, that lesson does not stay as a story told once in a meeting. It gets transformed into something durable, a guideline or a process that outlives the conversation where it was first raised. Without that transformation, the lesson remains a memory a few people happen to share, not something the team can actually rely on going forward.
The champion method
One effective way to make this happen is identifying the person who holds strong judgment in a particular area and making them the champion for it, the person other engineers go to, and the person who leads how a guideline is actually applied in practice. This benefits more than the engineers learning from that champion. It also benefits the champion directly, because teaching and defending their own judgment to others forces them to examine it more closely, exposing them to challenges and situations from other engineers that widens their own view beyond what they would have encountered working alone.
Why documentation is what separates judgment from folklore
There is a real difference between judgment that exists as a vague, half remembered sense that a team generally believes something, a belief or a thumb rule nobody can quite trace back to its origin, and judgment that has been documented into an actual guideline or process, something that can be followed as a concrete action, tested, and improved over time. Undocumented judgment degrades into folklore. Documented judgment remains something the team can act on reliably, long after the person who first learned the lesson has moved on.
The cost of never doing this
Without lessons converted into guidelines, and without champions who carry judgment forward, a team’s experience drains the moment any one engineer leaves. The organisation loses not just a person, but everything that person had accumulated that was never transferred to anyone else. Several individually strong engineers can spend years working side by side while each one independently knows only a fraction of what the team as a whole has actually learned, with no single person, and no team process, ever holding the complete picture.
The equal and opposite danger
Having built the case for collective judgment, it is worth being just as clear about its own failure mode, because this is not a case where more is automatically better. A guideline built from one past failure can be misapplied to a new situation that only superficially resembles the old one. A team weighed down by too many rigidly applied past lessons can find its design progress slowed, or its actual design considerations derailed, all in service of avoiding a problem that does not genuinely apply to the situation in front of it right now. This is the same underlying danger already covered elsewhere, a rule extracted from one specific context, applied too literally outside the situation it was actually written for.
Why collective judgment still requires judgment
A team can fail in two directions, not one. Too little collective judgment, and experience drains away the moment someone leaves, forcing the same lessons to be learned again from scratch. Too much collective judgment, applied rigidly without question, and the team loses the ability to see a new situation clearly, treating every past lesson as an unquestionable rule rather than a starting point for evaluation. Real collective judgment sits deliberately between these two failures, recording what has genuinely been learned, while still being willing to ask, every time, whether it actually applies to what is in front of the team right now.