How Organizations Normalize Warning Signs Without Realizing It

Blog Post – Based on Leading Through Chaos by Sal Lifrieri

I want to share something I’ve seen happen more times than I care to count, and it never gets easier to watch. I worked to break this pattern down in Leading Through Chaos. Organizations don’t decide to ignore danger. They drift into it, one small rationalization at a time, until ignoring the obvious becomes just “how things work around here.”

It usually starts with an analyst or a staff member who raises a flag. Leadership waves it off and nothing blows up. Just like that, the person who spoke up earns a reputation for “crying wolf.” Everyone else in the room sees what happened. They file it away. They learn to stay quiet.

After a few rounds of that, the early warning system is gone, not because the problems went away, but because raising them became too costly. The signals are still there. The organization just stopped listening. This is exactly where workplace violence prevention efforts either succeed or fail.

This is how normalization happens. Not the loud, obvious kind where someone announces they’re cutting corners. The quiet kind. A small deviation becomes routine. A routine deviation becomes standard practice. Standard practice becomes “just how we do things here.” And nobody can pinpoint when the shift happened, because it never happened all at once.

I watched this play out in an organization that received clear warnings about an employee who was making staff feel unsafe. Security professionals recommended action. In strong organizations, this is where structured threat assessment comes into play. Leadership called it an overreaction. What should have taken minutes, pulling the person in, interviewing them, and getting the threat assessment experts involved, stretched into days. By the time they moved, fear had already spread through the whole staff. The warnings were there the whole time. The organization had just gotten very good at not seeing them.

Leadership ego makes it worse. A leader makes a bold call, the disaster doesn’t materialize, and they feel like a hero. Then they dismiss the people who raised the alarm, because “nothing happened.” That teaches exactly the wrong lesson. Instead of building a culture where people shout about danger, you build one where they go quiet and hope for the best.

Over forty years of working with good leaders in the NYPD, intelligence operations, and emergency management, I’ve found they all shared one habit. When someone flagged a concern that turned out to be nothing, they said thank you anyway. They treated warnings as intelligence, not inconveniences. They understood that the absence of a disaster doesn’t mean the system is working. Sometimes it means you got lucky. Sometimes it means someone lower in the organization quietly fixed the problem before it reached you. And sometimes it means the disaster is still coming.

What holds organizations together isn’t elegant design or airtight processes. It’s judgment, adaptability, and the individual dedication of people who care enough to speak up, even when incentives push them to stay quiet. Acknowledging that isn’t defeatist. It’s the only honest starting point for building something genuinely resilient.

So here’s the question I’d leave you with: The last time someone on your team raised a concern that turned out to be nothing, did you thank them, or let them feel, even a little, like they’d wasted your time? That answer tells you more about your organization’s future than any risk assessment ever will.