A moment can undo years of trust

I once watched a tech lead blame a junior developer during a post-mortem. The outage wasn't even that bad. In front of the whole team, he pointed at her and said, "This is why we have code reviews."

She'd been there for three months. She left six weeks later, and two of the engineers who saw it happen followed her out.

The team had spent three years building trust. Ten seconds changed how people behaved around that lead.

Comfort can look like trust

Before that post-mortem, the team would have described itself as open and psychologically safe. Most teams I've worked with say something similar while projects are on track and nobody is under much pressure.

Then a deadline slips, a customer complains, or somebody makes an expensive mistake. The response tells you far more than a culture survey does.

I saw the same shift at a startup I consulted with. People genuinely liked each other. There were Friday beers, team off-sites, and plenty of talk about culture as a competitive advantage.

Then the company missed a major product deadline.

The CEO was under pressure from investors. In all-hands meetings, he began asking, "Who signed off on that estimate?" and "Why didn't anyone raise this earlier?" Those are fair questions. The accusation in his voice changed them.

Within a month, engineers were documenting decisions to protect themselves. Managers became careful about what they said in meetings. The friendly culture hadn't been fake, but nobody yet knew whether it could carry any weight. Under pressure, it couldn't.

I've started to think of that earlier comfort as assumed trust. Tested trust is what remains after something goes badly and the first response is to fix it together.

People remember who was sacrificed

Trust usually grows in small, almost forgettable moments. A manager defends a decision when their boss pushes back. Somebody admits they don't understand without being judged. A missed deadline leads to help instead of punishment.

People learn the pattern slowly. Unfortunately, they learn the opposite pattern very quickly.

After the post-mortem, the tech lead did apologize. It was the "sorry if you felt that way" kind of apology, which only made the problem harder to discuss. I don't think he was a bad person. He was under pressure and reacted badly. Still, two years later, people brought up that meeting when they explained why they didn't trust leadership.

The team did recover, but not while he was there. New leadership arrived and said, "We don't do blame here." More importantly, they proved it in several later situations where blaming somebody would have been easy.

That repeated proof mattered. A statement on its own couldn't compete with everybody's memory of what had happened.

Ask for the failure story

I've stopped asking a new team, "How's the culture?" The answer is nearly always some version of "good."

I ask about the last project that went badly instead. What happened? How did the team deal with the mistake? What was the worst meeting that followed?

Some people can tell the story plainly, including the uncomfortable parts and how they worked through them. Others reach for a safe example from years ago or become vague about who did what. Either answer is useful. It tells me whether the team has put its trust under any real load.

What happened the last time something went seriously wrong on your team? That story probably says more about the culture than everything written in the handbook.