Your organization might be traumatized. Here's what to do about it.

There's a pattern I see in certain organizations that is hard to name and easy to mistake for something else. Staff turnover that never quite stops. A board that can't seem to make decisions, or makes them and immediately second-guesses them. An executive director who is working harder than anyone should have to, holding things together through sheer force of will. Meetings that feel heavy before they start. A collective sense, unspoken, that something is wrong — but no one can say exactly what.

What I'm often looking at, in those moments, is organizational trauma.

What organizational trauma is

The researchers Shana Hormann and Patricia Vivian developed a framework for understanding how trauma — the kind we usually associate with individuals — can take root in organizations. Their work describes organizational trauma as the result of events or conditions that overwhelm an organization's capacity to respond: sudden crises, chronic underfunding, leadership betrayal, structural racism, repeated failure without adequate support, the accumulated weight of doing hard work in a world that underpays and undervalues it.

The key insight of their framework is that trauma doesn't stay in individuals — it becomes embedded in the culture, the systems, and the collective behavior of the organization. It shows up as hypervigilance (constant crisis mode, even when there's no crisis). It shows up as avoidance (refusing to have the conversations that need to happen). It shows up as fragmentation (teams that don't communicate, decisions that don't connect). And it shows up as burnout — the gradual depletion of people who care deeply about the mission but have no reserves left to draw on.

Why naming it matters

One of the most important things I've learned from working with organizations in distress is that the inability to name what's happening is itself part of what keeps people stuck. When staff don't have language for what they're experiencing, they tend to personalize it. They conclude that they're not good enough, not resilient enough, not committed enough. They leave — and take institutional knowledge and hard-won relationships with them. Or they stay and go quiet, which is its own kind of loss.

Naming organizational trauma doesn't mean assigning blame. It doesn't mean the leadership failed or the board was negligent or the founders did something wrong. Organizations that do the hardest work in the most under-resourced conditions are often the most vulnerable to it — because the work itself is traumatic, and because the people drawn to it frequently have their own histories of caring more than the system supports.

But naming it creates something crucial: the possibility of a different kind of conversation. When a team can say "we are carrying something heavy and it has a name," they can begin to look at it together rather than each carrying it alone. That shift — from private suffering to shared recognition — is often where healing begins.

What it looks like in practice

Organizational trauma can look like a lot of different things on the surface. A strategic planning process that keeps stalling. A board that can't recruit new members. Staff surveys that show low morale but no one will say why in public. An executive director who has been described, by multiple people in multiple conversations, as "the only one holding this together" — which is almost always a sign that something structural has broken down.

It can also look like a founder who built something remarkable and, in doing so, inadvertently made it impossible for anyone else to lead. Or a past crisis — a financial scandal, a leadership departure under bad circumstances, a public failure — that was never fully processed, that still shapes how people behave even years later.

What can actually change

The good news — and I want to say this clearly — is that organizational trauma is not a permanent condition. Organizations can and do recover. But recovery requires honesty about what happened, structured space to process it, and leadership that is willing to sit with discomfort rather than paper over it.

In my work, this often means creating a container — a facilitated process, sometimes a Circle, sometimes a structured retreat — where people can speak honestly about what the organization has been through and what they need. It means building in the time and the psychological safety for that conversation to happen. And it means being willing to look at the systems and structures that either allow healing or prevent it.

Hormann and Vivian's framework offers something rare in organizational consulting: it treats people in organizations as whole human beings who carry history, not as interchangeable parts in a system that just needs better management. That framing matters. It's the difference between an organization that survives its hard chapters and one that gets defined by them.

If any of this resonates with what you're seeing in your organization, the first step is simply to name it. You can't address what you can't talk about. And in my experience, the moment a team finds language for what they've been living with — the relief in the room is something you can feel.