I once attempted to explain cryptocurrency to my brother during a particularly long afternoon at the studio, and I realized about halfway through my description of decentralized ledgers (which is just a fancy way of saying nobody is the boss of the record-keeping) that I was using words I didn’t actually understand to bridge gaps in my own knowledge.
I told him “gas fees” were like a digital toll booth, but I couldn’t explain why the toll changed every five minutes or who was actually collecting the money. We do this often in the professional world-we reach for a word that sounds like a solid, structural beam, only to find out later it was just a decorative piece of balsa wood.
Structural Beam
Balsa Wood
In the world of safety and property management, that word is “standard.” We treat it like a meditation cushion that has been perfectly calibrated for every spine (the kind filled with high-density foam rather than cheap buckwheat hulls that eventually collapse into a dusty pancake). We assume “standard” means “sufficient for my specific needs,” but in reality, a standard is often just the lowest common denominator that a committee could agree upon without starting a fistfight.
The Mirage of Normalcy
Consider a facility manager-let’s call him Marcus-standing in a mechanical room where the primary fire pump has just developed a catastrophic seal leak. The technical term for this is an impairment (the industry’s polite way of saying the building’s heart has stopped beating), and suddenly the “standard” fire prevention systems are offline.
Marcus calls for a quote on coverage to bridge the gap until the parts arrive from a warehouse three states away. He sees the phrase “standard coverage” on the proposal and feels an immediate, physical sense of relief. The word “standard” acts like a psychological anchor, grounding his anxiety in the belief that he is making the “normal” and “vetted” choice.
He imagines that a team of wise elders has looked at every possible building configuration and decided that this specific level of monitoring is the universal gold standard. He doesn’t realize that the standard was likely calibrated for a single-story, modern warehouse with clear sightlines and working exit signs, while his facility is a sprawling, multi-level maze of masonry and partitioned offices.
The clock in his office ticks with a heavy, metallic thud, marking the it took for him to sign a contract that doesn’t actually protect him.
When the Baseline Becomes a Deficit
The danger of “standard” is that it hides the question of “standard for whom?” and replaces it with a generic sense of adequacy. When we talk about safety, we are often talking about mitigation (the act of making a bad situation slightly less terrible), but we forget that the size of the mitigation must match the size of the risk.
In my mindfulness practice, I teach that “standard breathing” doesn’t exist; a breath for a person sitting in a quiet garden is not the same as a breath for someone trying to outrun a sudden storm. Similarly, a safety protocol that is “standard” for a suburban office park is a dangerous joke when applied to a high-rise construction site with open elevator shafts and volatile fuel tanks.
We accept the default because the word “standard” makes the choice feel effortless, but that effortlessness is a screen. It conceals the fact that the baseline was set for the average, and almost no one actually lives or works in a place that is truly average. History is littered with the wreckage of “standard” precautions that met “non-standard” realities, resulting in a total loss of lives.
The Cost of Static Standards
This brings us to a key point in industrial history: the Iroquois Theatre fire of in Chicago. The theatre was billed as “absolutely fireproof,” a claim that met every “standard” of the day (including the standard of the “fireproof” curtain, which was supposed to drop and seal the stage from the audience).
The curtain was made of asbestos and wood pulp, which was the “standard” material at the time, but during the actual fire, a single misplaced light bracket prevented it from dropping more than halfway. The technical term for this is a failure point (the specific spot where the whole plan turns into a disaster), and it happened because the “standard” curtain wasn’t designed for a “non-standard” light placement.
Lives lost within 15 minutes because the “standard” failed to account for complexity.
The people in the audience trusted the “standard” because the word itself was a promise of safety, but that promise was built on a foundation of generic assumptions. The “standard” didn’t account for the complexity of the specific room, just as “standard coverage” today often ignores the specific egress (the path people take to get out) of a complex building. The final death toll was a harrowing people, most of whom died within of the fire’s start.
The problem with accepting a baseline is that it requires you to ignore your own proprioception (your internal sense of where you are in space) and trust a map drawn by someone who has never stepped foot on your property.
When a facility manager accepts “standard coverage” for a fire watch, they are often unaware that the personnel provided may only be trained to walk a basic loop, ignoring the high-risk chemical storage or the outdated electrical panels that haven’t been serviced since the Nixon administration. They are buying a product called “normalcy,” but they are paying for it with their actual security.
If you are operating a site that is complex, high-traffic, or inherently dangerous, the “standard” is actually a deficit. It is the gap between what you have and what you actually need. True protection requires a shift from “what is the normal amount?” to “what is the necessary amount for this specific impairment?” This requires a specialized
that understands the difference between a routine patrol and a high-stakes monitoring mission.
Property Damage Increase (Generic vs. Site-Specific)
+11%
Statistics from the NFPA suggest that localized property damage is 11 percent higher when generic defaults are used instead of site-specific plans.
Professional Sleepwalking
I often think about my crypto mistake when I see businesses choosing their safety defaults. I was trying to look like I belonged in the conversation by using the right jargon, even though I hadn’t done the work to understand the underlying mechanics. When a business owner chooses “standard,” they are doing the same thing.
They are trying to fit into a perceived professional norm, even if that norm is ill-suited to their reality. It’s a form of professional sleepwalking. We move through these decisions on autopilot because the alternative-actually assessing the unique risks of our facility-is exhausting and requires us to confront the possibility that we are more vulnerable than we’d like to admit.
The technical term is complacency (a feeling of smug satisfaction with the status quo), and it is the primary ingredient in almost every industrial disaster. We tell ourselves that because the insurance company or the inspector said the coverage is “standard,” we are absolved of the responsibility to look closer. We forget that the inspector is looking for a checkmark on a box, but we are the ones who have to live with the fire.
In one recent study, a “standard” water tank was found to be nearly 10k gallons short for the specific building it was meant to protect.
The Human Element of Alertness
The “standard” also fails to account for the human element of vigilance (the state of being constantly alert for danger). A generic guard might check a door every hour because the contract says so, but a trained professional looks for the smell of ozone from an overheating transformer or the slight discoloration of a ceiling tile that indicates a hidden leak.
“One is following a script; the other is reading the room.”
In mindfulness, we call this “active presence,” and it is the only thing that actually keeps you safe when the “standard” systems have failed. If you rely on a baseline, you are essentially betting that your disaster will be a “standard” disaster-one that follows the rules and stays within the lines.
But fires don’t read the manual. They don’t care about the “typical” site. They look for the gap, the exception, and the oversight. They look for the gas line that everyone forgot was there.
The standard is a thin blanket that fails to cover the cold reality of a specific impairment.
When you move away from the comfort of the word “standard,” you start to see the architecture of your risk more clearly. You begin to ask about redundancy (having a backup for the backup) and whether your documentation is actually “audit-ready” or just a pile of illegible signatures.
You start to value digital reporting tools like TrackTik, not because they are “the standard,” but because they provide the verifiable, time-stamped proof that someone was actually looking at the high-risk zones when they said they were. This isn’t just about following the fire code; it’s about compliance (meeting the requirements of the law and the insurer) in a way that actually reflects the stakes of your business.
In the end, the word “standard” is just a ghost in the machine of our decision-making. It’s a phantom that tells us we’ve done enough when we’ve only done the bare minimum. We should be looking for the “extraordinary” because that is what a crisis demands.
A building with its sprinklers off is not a “standard” building; it is a vulnerable one. And a vulnerable building doesn’t need a default; it needs a defense that is as unique and complex as the structure itself.
The specific high-risk space we’re actually standing in-one that a “standard” map can never fully capture.
We must stop pretending that the “right” choice is the “normal” one and start choosing the one that actually accounts for the square feet of high-risk space we’re actually standing in.