Most CRR content is about the what and the how.

What community risk reduction is. How to build a program. How to make the budget case. How to conduct a Community Risk Assessment. How to get company officers engaged. How to talk to city council members about funding.

I have written about all of those things, and I believe they matter. But this article is about something that rarely gets named directly — the why. Why community risk reduction matters. The personal, specific, often painful moment or realization that transforms prevention from a professional lane into something that actually drives you.

Because without a why — for individuals and for organizations — CRR is just activity. It is programs and metrics and initiatives that look good on paper and quietly fade when the budget gets tight or the champion moves on or the enthusiasm of a new initiative gives way to the grinding reality of sustained prevention work.

The why is what keeps it alive when everything else pushes back.

Where I Came From

I want to be honest about who I was before I had a why.

I came from operations. I loved it. I genuinely, unashamedly loved the excitement of the job — the adrenaline, the high-stakes calls, the culture of people who ran toward what everyone else ran from. There is something about that world that gets into you and does not come out easily, and I am not sure it should.

But there is a thing that the ops culture does not always say out loud, even though everyone in it knows it at some level: the exciting calls are exciting because something has gone very wrong for someone. The structure fire we cannot wait to get dispatched to represents someone’s home, someone’s business, someone’s life — everything they built or owned or loved, on fire. The dramatic rescue we train for and talk about for years is a person in the worst moment they have ever experienced.

I knew this intellectually for years before I felt it.

Then I felt it.

The Moment That Changed Everything

In 2015 I wrote a water safety article on this site that described a near-drowning incident involving my three-year-old son. I am going to share it here again because it is the origin of everything I do in CRR, and I think it deserves to be named as such.

My family was having a party in our backyard — about forty guests, lots of small children, everyone swimming or enjoying themselves. I was watching the pool. I want to be clear about that. I was actively watching the pool. I am a firefighter. I am trained in drowning emergencies. We had fences, locked gates, barriers, everything in place that someone in my position would have.

One of the children climbed out of the pool and became sick. I went to help. I was distracted for a matter of moments. My wife came back outside with snacks and asked where our son was.

We looked at the pool and found him floating face down, not breathing.

I still remember his limp, pale, lifeless body being handed to me. I started CPR on my own three-year-old son.

He is fine. He recovered completely and I am grateful for that every single day. But I want to sit with what that moment actually was before moving past it, because I think it is important.

I was an expert. I was watching. I had done everything right. And it still happened.

Not because I was negligent or careless or unprepared. But because risk does not negotiate. It does not check your credentials before it shows up. It does not wait until you have your eyes on the right thing. It does not exempt the people who know the most about it.

The fire service person who secretly hoped for something exciting on every shift came face to face, on his own back patio, with what exciting actually means for the people on the other side of it.

Everything changed after that.

There Is Something Else Worth Naming

The ops culture I loved also came with something I am less proud of — something I think most honest firefighters will recognize even if they have never said it out loud.

When you respond to emergencies long enough, a certain distance develops. It is partly protective — a psychological mechanism that allows people in high-stress professions to do difficult work without being destroyed by it. But it can slide into something less defensible.

The quiet assessment on the way back to the station. The conversation around the kitchen table about what the family should have done differently. The unspoken — and sometimes spoken — thought that this could have been prevented if people had just paid attention, made better choices, known what we know.

We call it experience. Sometimes it is. Sometimes it is callousness wearing experience as a disguise.

The blame is not always wrong in the technical sense — many emergencies do involve choices that made things worse. But the casualness with which we sometimes apply it says something about the distance we have allowed to develop between ourselves and the people we serve. They became, in some quiet way, cautionary tales rather than people. Their emergencies became job security rather than tragedies. Their suffering became evidence of their own inadequacy rather than a reflection of the risks that exist in every life — including ours.

I was not immune to this. I want to be honest about that.

And then one afternoon it was my son in the pool.

The firefighter who knew everything about drowning prevention. Who had every precaution in place. Who was actively watching.

Humbled completely and immediately.

Whatever distance I had allowed to develop between myself and the people on the other side of an emergency collapsed in that moment. The family who lost a child to a preventable accident was not a cautionary tale. They were me. They could always have been me. They could be any of us — any day, at any party, in any backyard.

That realization is not comfortable. It is not supposed to be.

It is the beginning of a genuine why, scrutinizing why community risk reduction matters.

What a Why Actually Does

There is a version of CRR work that is professional and competent and entirely sustainable without a personal why. You can run programs, track metrics, conduct assessments, and produce outcomes that look excellent on any report — motivated by professional pride, career advancement, or genuine belief in the mission at an intellectual level.

That version is valuable and I do not want to diminish it.

But there is a different version that is available to people who have a why — a lived, felt, specific reason that prevention work matters — and it operates differently. It sustains differently. It recovers from setbacks differently. It makes a different argument in a budget meeting, in a city council presentation, in a conversation with a company officer who thinks CRR is someone else’s job.

When I talk about why prevention matters, I am not reciting a framework. I am remembering my son’s face. That changes how it lands.

Every person in the fire service has their own version of that moment — or has access to one through the experiences of the people they have served. The family that lost everything in a fire that a working smoke alarm might have caught twenty minutes earlier. The elderly resident who was not reached by the notification system in time. The business that never reopened. The child who did not recover the way my son did.

These are not statistics. They are the actual content of what CRR is trying to prevent. And the professionals who can hold that reality alongside the data — who can feel the weight of what they are working to stop — are the ones who tend to sustain this work when others step back.

The Organizational Why

Everything above applies to individuals. But organizations need a why too — and this is where it gets harder.

A fire department’s mission statement almost always contains language about protecting life and property, serving the community, and preventing emergencies before they happen. Most of them do. Read any ten mission statements and you will find some version of that commitment.

Then look at the budget. Look at the staffing allocations. Look at how the department spends its time, its training resources, and its leadership attention on a typical week.

For most departments, the organizational why for CRR is aspirational rather than operational. The mission says it matters. The culture has not fully caught up.

This is not hypocrisy. It is the natural result of an institution that was built around response — where the exciting call is still the thing that defines identity, where the prevention work is still something that competes for attention rather than commanding it organically.

The gap between the stated why and the operational reality is not closed by a strategic plan or a new program. It is closed by the leaders inside the organization who have a personal why strong enough to insist on the alignment — who can make the argument not just with data but with the weight of something they have actually felt.

The chief who watched a family lose a child to a preventable drowning and made pool safety a departmental priority. The captain who lost a crew member to a medical emergency that better community health outreach might have caught earlier. The company officer who noticed a pattern of repeat calls at the same address and could not stop thinking about what was actually happening there.

These are the people who close the gap. Not because they have better programs, but because they have a clearer why.

The Question Worth Asking

If you work in the fire service — at any level, in any role — I want to ask you to sit with this question seriously rather than answering it quickly.

What is your why for CRR?

Not the professional answer. Not the mission statement version. Not what you would say in a budget presentation or a conference panel.

The real one. The specific moment or experience or person that makes this work feel like something more than a job category.

If you have it, hold onto it. Name it to yourself regularly. Let it inform how you talk about prevention to people who have not found theirs yet. Let it be the thing you return to when the budget gets cut or the program stalls or the culture pushes back in ways that make the whole enterprise feel futile.

If you do not have it yet — or if you have been doing this work long enough that the original why has faded into the background noise of daily operations — go looking for it. It is in your call history. It is in the faces of the people you have served. It is in the gap between what you responded to and what a prevention program might have changed.

CRR without a why is just activity.

The why is what makes it matter.

And for me — for everything I have built, every article I have written, every conversation I have had about what it means to reduce risk before it becomes an emergency — the why has a very specific face.

A three-year-old boy, face down in a pool, on a sunny afternoon, while his firefighter father was watching.

That is why.

Brent Faulkner, MAM, FO, is the CEO and Founder of Virtual CRR Inc.
A retired Battalion Chief from Anaheim Fire & Rescue, Brent brings 28 years of fire service experience, including leadership in structure fires, wildland operations, hazardous materials response, EMS incidents, and specialized rescue operations. He also served 17 years on a Type 1 Hazardous Materials Response Team.

A defining moment in Brent’s career came while leading Critical Infrastructure Protection (CIP) efforts at a DHS-recognized Terrorism Fusion Center. There, he oversaw initiatives to safeguard critical infrastructure from terrorism, natural disasters, and emerging threats — an experience that shaped his passion for Community Risk Reduction and ultimately led to the creation of Virtual CRR.

Brent holds a Master’s Degree in Management, a Bachelor’s in Occupational Studies, and Associate Degrees in Hazardous Materials Response and Fire Science.