The Communications Crisis Nobody Is Naming

Every organization I have ever worked with or advised has faced a version of the same moment. Something happens — in the world, in the industry, in the building — and someone asks: are we going to say something about this?

That question used to come up a few times a year. Now it comes up a few times a week. And most organizations are answering it the same way they always have: case by case, instinct by instinct, with no framework and no consistency. Someone in the room feels strongly. Someone else worries about the precedent. Legal weighs in. The moment passes. Or it doesn't, and the silence becomes the story.

This is not a crisis communications problem. It is a consistency problem. And it is the most undernamed challenge facing institutional leadership right now.

Why Case by Case Isn't Working

Case-by-case decision making sounds reasonable. Every situation is different. Context matters. Nuance is real. All of that is true.

But the people inside your organization are not experiencing your communications decisions as nuanced. They are experiencing them as a pattern. And the pattern they are seeing is: we responded to that but not this. We spoke out then but stayed silent now. We said that mattered but apparently this doesn't.

That perception — whether accurate or not — erodes institutional trust faster than almost anything else. Because what people hear in inconsistency is not nuance. They hear favoritism. They hear hierarchy. They hear that some pain counts and some doesn't.

The Chief Communications Officer is supposed to be the person who solves this. But most CCOs are still operating with a playbook built for a slower world — one where crises were discrete events with beginnings and ends, where you had days to craft a response, where the volume of issues demanding attention was manageable.

That world is gone. And AI finished it off.

What AI Did to the Problem

AI has done two things to institutional communications that haven't been fully reckoned with yet.

First, it multiplied the volume. The number of issues, controversies, and moments that now surface and demand organizational attention — through social media, internal Slack channels, employee resource groups, external advocacy — has increased by an order of magnitude. No communications team, no matter how talented, can respond to everything. Which means every decision not to respond is now visible in a way it never was before.

Second, it changed who is watching. Employees are using AI tools to process their own workplace experiences — to draft complaints, to research their rights, to find language for things that feel wrong but are hard to name. They are more informed, more networked, and more capable of organizing around institutional failures than any previous generation of workers. The days when an organization could manage a difficult internal moment quietly and locally are largely over.

Together these two shifts mean that the consistency problem — which was always there — is now existential. Organizations that don't develop a principled framework for when and how they speak are going to keep losing ground. Not because they said the wrong thing. Because nobody could figure out what they stood for.

Institutional Neutrality Is Not the Same as Institutional Silence

Here is the distinction that most organizations are missing, and that most communications frameworks fail to make: institutional neutrality and institutional silence are not the same thing. Treating them as synonymous is the source of most of the damage.

An institution can decline to take a position on a contested political or social issue — and should, in many cases — without pretending that the people inside it are not feeling something real. The institution's silence on the issue does not invalidate the employee's experience of it. Those are two separate things, and conflating them is what turns a principled communications decision into something that feels like abandonment.

For twenty years, the work that absorbed that gap — holding space for people who felt unheard when the institution stayed quiet, teaching people how to advocate for themselves in ways that wouldn't backfire, providing a place where being heard was enough even when nothing was going to change — that work lived in offices like mine. Diversity, equity, and inclusion offices. Ombudsman offices. Employee relations functions.

It was never called communications work. But that is exactly what it was. It was the infrastructure that made institutional neutrality survivable for the people inside the institution.

The CCO role has rarely been connected to that infrastructure. It should be. Because the organizations that have figured out how to hold both things at once — a principled, consistent position on what the institution will and won't speak to, coupled with genuine responsiveness to the humans inside it — are the ones that have maintained trust through the hardest moments.

What a Framework Actually Looks Like

A principled communications framework is not a flowchart. It is not a policy document. It is a set of questions that get asked consistently, by the right people, before every significant decision about institutional voice.

Those questions include: Does this issue fall within our organizational mission and expertise, or are we being asked to perform a position we don't actually hold? Who inside our organization is most affected by this moment, and what do they need from us that we can actually provide? What is the cost of speaking, and what is the cost of silence — and are we being honest about both? And critically: is this consistent with what we have done before, and if not, can we explain why?

That last question is the one most organizations skip. It is also the one that matters most to the people watching.

Consistency does not mean saying the same thing every time. It means applying the same principles every time. And it means being willing to say, out loud, what those principles are — so that people can hold the institution accountable to them, and so that silence, when it comes, reads as a principled choice rather than indifference.

The Skill Set the CCO Role Actually Needs

The next generation of Chief Communications Officers will need something that has not traditionally lived in communications departments: the ability to hold institutional neutrality and human compassion at the same time, at scale, under pressure, consistently.

That is not a messaging skill. It is not a media relations skill. It is the skill of understanding what an institution owes its people, what it can and cannot promise, and how to communicate both of those things honestly — even when the honest answer is that the institution is not going to act, and the person asking needs to find a different kind of support.

I have spent twenty years developing that skill in contexts that were never called communications. The work of advising organizations on policy and culture, of holding space for people navigating institutional silence, of teaching responsible advocacy to people who have real grievances and limited power — that work is the hardest version of the communications challenge every CCO is now facing.

AI did not create that challenge. It just made it impossible to ignore any longer.

The organizations that hire for that skill set — rather than for media polish or crisis management experience alone — are the ones that will build the institutional trust that everything else depends on.