Silence Is a Signal

I worked with a hospital once where staff routinely raised concerns.

Some involved physician behavior. Others involved coding and billing practices. Documentation concerns surfaced regularly. None of these issues were secret, and none were particularly surprising to the people doing the work every day.

The concerns made their way through the appropriate channels and onto the right agendas.

And then, more often than not, nothing happened.

Excuses were made. Issues were minimized. Sometimes they were dismissed. Sometimes they were acknowledged and quietly set aside. Whatever the response, the outcome was largely the same.

Over time, staff learned something.

Raising concerns didn't matter.

Not because the concerns lacked merit. Many were legitimate observations raised by people with firsthand knowledge of the problem. Nor was it because patient care wasn't important or because leadership was intentionally ignoring the issues. What people learned was far simpler: raising concerns rarely led to meaningful action.

Over time, that lesson became part of the culture.

People continued showing up every day and doing the work. They cared for patients, supported their colleagues, and carried out their responsibilities with the same professionalism they always had. What changed was their willingness to invest energy in raising concerns they no longer believed would be addressed.

Slowly, the culture shifted from one where problems were surfaced to one where problems were managed quietly. Speaking up felt less productive. Keeping your head down felt more practical.

It simply became the way things worked.

No one announced the change.

Why would they?

Speaking up takes effort. It requires people to risk disagreement, challenge assumptions, and occasionally place themselves in uncomfortable situations. Most people are willing to do that when they believe it will make a difference.

It's much harder when experience suggests otherwise.

Years later, I can still remember how quiet things became.

At first glance, that quiet could have been mistaken for stability. Meetings were easier. Fewer concerns were raised. Less time was spent debating difficult issues.

But the underlying problems hadn't gone anywhere.

The questions about physician behavior were never fully resolved. Documentation concerns continued surfacing. Coding and billing risks remained part of the organization's reality. The difference was that fewer people were talking about them.

Eventually, some of those issues resulted in compliance findings, terminations, and repayment obligations.

None of those outcomes were surprises to the people closest to the work.

Many had seen the issues coming long before.

They had simply stopped talking about them.

That experience completely changed the way I think about silence in organizations.

Silence is not the absence of problems. More often, it's information.

When people feel heard, silence can signal confidence and trust. But when concerns have been repeatedly minimized or ignored, silence can signal something entirely different.

It can signal that people have stopped believing their voice will make a difference.

That's why I've come to see silence as more than a communication issue. It's often a cultural one.

Cultures are shaped by what people experience. When raising concerns leads to meaningful discussion and action, people continue speaking up. When it doesn't, the culture shifts.

And when people stop raising concerns, the most important question isn't:

"Why is nobody speaking up?"

It's:

"What have they learned from speaking up in the past?"