What Nobody's Saying Speaks Louder Than Words

Silence in a team isn't neutral.

It's easy to treat it that way. When nobody pushes back in the meeting, when the group moves forward without objection, when everything seems fine on the surface, it's tempting to read that as alignment. As trust. As things working.

But... often it isn't. Sometimes silence is disagreement that doesn't believe it has a home.

Culture researcher Gustavo Razzetti has a useful term for what accumulates when teams go quiet: conversational debt.

Every conversation a team avoids doesn't disappear. It compounds. Like financial debt, the longer you carry it, the more expensive it gets.

He also has a name for what that debt looks like in practice. He calls it the stinky fish. It's the thing everyone knows about but nobody says out loud. The failed project that never got debriefed. The decision a few people quietly disagreed with but went along with anyway. The dynamic that's been making the work harder than it needs to be for months.

Everyone can sense it. Nobody wants to be the one to name it. So it just sits there, getting worse.

The reason this happens usually isn't fear, it's something more subtle.

People want to belong to the team, and belonging feels like going along.

They've raised concerns before and nothing changed. They don't want to be the one who slows things down, especially when everyone else seems to be on board.

You can't solve this with a policy. You can put "psychological safety" on a values slide and it won't change much on its own. The real question is what you do when someone actually says the hard thing.

Leaders undermine safety through small, repeated signals. The redirect that happens before a concern is fully heard, the eye-roll when feedback arrives at an inconvenient time, or the subtle pattern of whose voice gets taken seriously and whose gets noted and moved past.

None of it feels like a big deal in the moment. Together, it teaches people what's actually safe to say.

​Lindy Elkins-Tanton led the NASA Psyche mission, a $1.2 billion spacecraft built by 800 people over more than a decade.

Her team's operating principle was simple: the best news is bad news brought early.

The person who finds the problem is the hero. She told me that twelve days before launch, one engineer looked at some data a fifth time and said they just wasn't confident about a specific component. That concern, raised out loud, may have saved the entire mission.

That's what it looks like when the culture is working.

Here's a question worth asking yourself this week: when was the last time someone on your team brought you genuinely bad news?

Not a minor setback. Something that required real courage to say.

If it's been a while, it might mean everything is going well.

Or, it might mean the stinky fish has been in the room so long that nobody wants to be the one to point at it.

This week, be brave enough to figure out which it is.

P.S. If you lead a creative team and you’re not already listening to the Herding Tigers podcast, this week is a great time to start. The new episode is out now wherever you get your podcasts.

Listen on Spotify or Apple Podcasts (or wherever you get your shows)