It’s Not Who’s Right. It’s What’s Right.

Field Notes Industry Perspective
Issue No. 001  ·  Industry Perspective

It’s Not Who’s Right.
It’s What’s Right.

After 40 years in fire alarm and life safety, the most dangerous words I’ve heard on a job site aren’t “I don’t know.” They’re “trust me, I’ve always done it this way.”

“It’s not who’s right.
It’s what’s right.”
The five words that stopped me cold

I saw something recently on another platform — five words, posted without context, no explanation needed. “It’s not who’s right. It’s what’s right.” It stopped me cold. Not because it was new. Because it named something I have watched this industry get wrong for four decades.

Fire alarm and life safety work attracts strong personalities. People who have been doing this a long time develop strong opinions. That’s not a flaw — experience is supposed to produce conviction. The problem comes when conviction stops being about the system and starts being about the person.

The most dangerous words on a job site

In forty years, I have heard a lot of dangerous things said on job sites. Wrong wiring methods. Misread code requirements. Devices placed without calculation. But the phrase that has caused more callbacks, more failed inspections, and more genuinely unsafe conditions than any of those is one you’ve probably heard too:

“Trust me. I’ve always done it this way.”

That sentence ends conversations. It shuts down the tech who just read something in NFPA 72 that contradicts what the senior guy is doing. It dismisses the engineer who flags a spacing issue on a submittal. It silences the inspector who asks a question that deserves an answer. And sometimes — not always, but sometimes — it lets something genuinely wrong walk out the door into a building where people sleep.

Ego is not a code reference

The code doesn’t care how long you’ve been doing this. The fire doesn’t negotiate. A smoke detector placed two inches outside the required coverage area performs exactly the same as one placed twenty feet outside it — which is to say, it may not perform at all when it matters.

I have sat on the NFPA 72 SIG-PRO Technical Committee. I have been on both sides of the AHJ table. I have designed systems, installed systems, inspected systems, and managed systems for the Department of Defense in locations where a failed fire alarm isn’t a liability issue — it’s a mission failure. In all of that, the people I trusted most were never the ones who were most certain. They were the ones who were most rigorous.

The field note

Rigorous means checking your work against the code, not against your memory. It means welcoming the question from the junior tech, because sometimes the junior tech just read something you haven’t looked at in three years. It means being more committed to getting it right than to being right.

What this site is actually about

I started detect2protect.us because I believe the people responsible for life safety systems deserve access to real expertise — not guesswork, not brand loyalty, not the way it’s always been done. The tools I recommend are tools I have used. The code interpretations I share are grounded in the actual text, not tradition. The training perspective I bring is shaped by forty years of watching what happens when things go right and when they go wrong.

This isn’t about being the smartest person in the room. It’s about making sure that the rooms people sleep in, work in, and spend their lives in are protected by systems that actually work — designed, installed, and maintained by people who care more about what’s right than who’s right.

Five words. That’s all it took to put it perfectly. I’ll be building everything on this site around that idea.


Industry Perspective NFPA 72 Life Safety Professional Standards Field Notes
BJ

Brian Jarvis

NICET Level IV  ·  CFPS  ·  NFPA 72 SIG-PRO Committee Member  ·  40+ Years in Fire Alarm & Life Safety

From a Simplex field technician in 1982 to federal AHJ SME/Team Lead, system designer, and NFPA committee member — Brian has spent four decades at the intersection of fire alarm code, field practice, and professional standards. detect2protect.us is built on that foundation.

Up next in Field Notes
Reading NFPA 72 — what the code actually says vs. what people think it says
Coming soon
Work with Brian directly

Have a project that needs
a second set of eyes?

Code review, submittal feedback, system design support — reach out. This is what the site is here for.

Get In Touch →