Imagine you are walking through a forest and a snake bites you.
You have a choice to make in that moment. You can treat the wound — find help, clean the bite, get the antivenom. Or you can turn to the snake and begin building your case. You document the bite. You tell the other animals what the snake did. You find ways to work around the snake’s territory without ever crossing it again. You become very, very skilled at avoiding the snake.
Meanwhile, the venom spreads.
This is not a story about snakes. This is a story about what fear does to otherwise intelligent, well-meaning people inside organizations — and how that behavior, modeled from the top, becomes the culture everyone inherits whether they wanted it or not.
The Anatomy of Avoidance
When something goes wrong between people in a low-trust organization — a missed expectation, a dropped handoff, a decision that landed badly — there is a fork in the road.
One path leads toward the problem. It requires a conversation, which requires vulnerability, which requires the belief that the other person is capable of hearing feedback and that the relationship can survive honesty. It is uncomfortable and direct and usually short.
The other path leads around the problem. It involves processing the situation with third parties, building alignment with allies, documenting what happened in case it becomes relevant later, and finding subtle ways to reduce your dependence on the person who disappointed you — all without ever speaking to them directly. It feels strategic. It feels safe. It feels, if you squint at it right, like professionalism.
It is none of those things. It is fear with good posture.
And in organizations where leadership consistently chooses the second path, everyone eventually learns to walk it too. Not because they are cowardly. Because they are watching. Because culture is not what you put in a handbook — it is what you see rewarded and what you see survive.
How the Venom Spreads
Here is the pattern, and it is worth naming precisely because it is so easy to be inside it without seeing it.
Something goes wrong. It might be a product decision, a missed deadline, a communication breakdown. The facts of what happened are, in isolation, recoverable. But instead of addressing what happened, the energy goes into assigning what happened. Who dropped it. Whose fault. Who should have known better.
The search for the villain begins.
And here is the insidious part: finding the villain feels productive. It has the shape of problem-solving — investigation, evidence, conclusion. It produces something: a narrative, a consensus, a shared understanding of who is responsible. Teams bond over it. Leaders feel decisive.
But nothing has actually been solved. The problem that created the situation in the first place — the unclear ownership, the misaligned expectation, the process gap, the unspoken tension — is still there, untouched, waiting to produce the next incident.
Villain-seeking is not problem-solving. It is problem-postponing dressed in problem-solving’s clothes.
The Snake Doesn’t Know
Here is the part of the story that is hardest to sit with.
When you go around someone, when you quietly reroute work to avoid them, when you have the conversation about them rather than with them — they usually know. Not the details, perhaps. But they feel the temperature drop. They notice the slight rerouting of information. They register the absence of feedback that should have come.
And they are confused. Because nobody told them anything was wrong.
So they do what people do when they sense something is off but have no information to work with: they fill in the gap themselves. They develop their own narrative. They become, in response to your silence, defensive — not because they were defensive to begin with, but because defensiveness is the rational response to threat you can’t see clearly.
Now you have a defensive snake. And you point to the defensiveness as evidence that the direct conversation was never possible. The avoidance has created the very outcome it was trying to avoid.
This is how distrust compounds. Not through dramatic betrayals, but through small silences that harden over time into walls neither person remembers building.
Management as Mirror
In the organizations where this pattern is most entrenched, it almost always flows downward.
Leaders who avoid difficult conversations model avoidance as sophistication. Leaders who seek villains instead of solving problems teach their teams that the right response to failure is prosecution, not repair. Leaders who work around people rather than with them demonstrate, clearly and repeatedly, that this is how adults handle conflict.
Employees are not naive. They watch what actually happens, not what the values poster says. And what they see, they learn.
The junior developer who watches their manager respond to a production incident by immediately identifying who is responsible — rather than who can fix it — learns something that no onboarding document can undo. The team that watches leadership handle an interdepartmental conflict through political maneuvering rather than direct conversation learns that honesty is for people who don’t understand how things work.
And so the culture reproduces itself. Every new person who joins finds the pattern already in place, already rewarded, already the path of least resistance. Most of them adapt. Some of them leave. A very few try to change it and find out how deep the roots go.
The tragedy is that nobody in this organization thinks of themselves as the problem. The leader avoids the conversation because the stakes are too high to risk it. The manager seeks the villain because accountability matters. The employee works around the colleague because the direct approach has never worked here. Everyone has a reason. Everyone is doing what makes sense given what they’ve been shown.
And the venom keeps spreading.
What Feedback Silence Actually Costs
There is a version of this that gets talked about in psychological safety research, but it deserves to be said plainly.
When people cannot give honest feedback — when the culture makes directness dangerous and silence strategic — the organization loses access to its own reality. Problems are known, but not spoken. Risks are felt, but not raised. The gap between what people say in meetings and what they say in private grows wider, and all that unspoken information has nowhere to go except into the rumor economy, the resignation letter, and the postmortem where everyone admits they saw it coming.
The cost is not abstract. It is the product decision nobody challenged because challenging things here gets you labeled a problem. It is the toxic dynamic that persisted for eighteen months because everyone could see it except the person with the authority to address it, and nobody told them directly. It is the resignation of the person who had tried, twice, to raise something important and had been handled rather than heard.
Silence is not neutral. Silence is a tax on every decision the organization makes — because every decision is made with incomplete information, and the missing information is sitting, unspoken, in the minds of people who have learned that speaking it is not safe.
The Turn: What Good Actually Looks Like
Here is the hopeful part, and it is genuinely hopeful because none of this is complicated. It is just uncomfortable, and uncomfortable is not the same as hard.
The conversation is almost always shorter than the avoidance.
The difficult conversation that you have been constructing in your head for three weeks — the one with all the possible objections and the imagined defensiveness and the narrative you’ve been building to support your position — that conversation, when actually held, almost never goes the way you feared. Not because the other person is easy. But because they are also carrying the unspoken thing, and they also feel the temperature, and when someone creates the space to address it directly, most people meet that with relief rather than hostility.
Not always. But far more often than fear predicts.
Feedback is a gift that compounds.
The team that can tell each other the truth — about the work, about the dynamics, about the decisions — gets smarter faster than the team that can’t. Every piece of honest feedback is a correction that prevents a larger error downstream. The manager who can hear “that decision landed badly and here’s why” can adjust. The manager who never hears it keeps making the same decision until the evidence is too large to ignore, by which point it is much more expensive to fix.
Feedback is not comfortable. But comfort is not the goal. Growth is the goal, and growth requires information, and information requires safety, and safety requires someone to go first.
The villain search ends when the question changes.
The single most powerful shift available to a leader in a low-trust culture is changing the first question after something goes wrong. Not “who is responsible?” but “what happened, and what do we need to change so it doesn’t happen again?”
This is not about avoiding accountability. People should own their decisions and their impact. But accountability in service of learning is entirely different from accountability in service of blame. One produces a better system. The other produces a better alibi.
The team that asks “what do we change?” after a failure becomes, over time, a team that fails less. The team that asks “who dropped it?” becomes, over time, a team that hides failures better.
How to Build Something Different
If you lead people, you are the culture. Not the culture you intend — the culture you model.
Go first. The direct conversation, the honest feedback, the admission that something didn’t land the way you meant it — these have to come from the top before they become possible at any other level. Every time a leader chooses the hard conversation over the workaround, they move the culture slightly. It is slow and it is unspectacular and it is the only thing that works.
Name the pattern when you see it. When a team meeting turns into a villain search, name what’s happening. Not as an accusation — as a redirect. “We’ve spent twenty minutes on who dropped this. Let’s spend twenty minutes on what we change.” Said once, it’s a correction. Said consistently, it becomes the new norm.
Make feedback safe by receiving it well. People will give you the feedback that your response history has told them is safe to give. If honest feedback has been met with defensiveness, rationalization, or subtle retaliation — people will stop giving it. The way to rebuild a feedback culture is to receive the next uncomfortable thing you hear with genuine curiosity rather than self-protection. Not once. Consistently, until people believe it.
Treat the wound before you investigate the bite. When something goes wrong, the first question is always: what do we need to do right now to make this better? The retrospective — the honest, blameless examination of what happened — comes after the immediate need is addressed. This sequence matters. It signals that outcomes matter more than narratives.
The Forest After the Snake
Back to the forest.
You were bitten. It hurt. And the snake — whatever the snake represents in your organization — may or may not have intended harm. That part doesn’t actually matter for what you do next.
What matters is the venom. What matters is treating it quickly, directly, with the people who can help. What matters is that you don’t spend your recovery time building a case, because the case won’t heal you and the wound won’t wait.
The organizations that build something worth building are not the ones without snakes. Every organization has conflict, failure, misalignment, people who disappoint each other. The difference is what they do in the moment after the bite.
Do they turn to the wound, or do they turn to each other?
The answer to that question, played out in a thousand small moments across a thousand interactions, is the culture. Not the values. Not the handbook. Not the all-hands speech about psychological safety.
The answer to that question, in the moment, every time.
The Series in Two Sentences
Build a culture where the tracker serves the team, not the team’s anxiety. Build a culture where the conversation happens before the workaround, the feedback before the silence, the question “what do we fix?” before the question “who do we blame?”
That culture doesn’t happen by accident. It is built, one behavior at a time, by leaders who understand that the most expensive thing in any organization is not the tools, not the process, not even the people who leave.
It is the truth that nobody said.
Part 1: If It’s Not in the Tracker, It Didn’t Happen — how distrust turns process into a tax on every team.