I Stopped Rewarding the Firefighters for Fires They Started
Why the modern organization craves the high drama of the rescue while ignoring the quiet expertise of prevention.
was the year the Vienna General Hospital became a graveyard for the living, though no one could quite explain why. In the First Obstetrical Clinic, women were dying of puerperal fever at a rate that climbed toward 18%, a terrifying lottery for any expectant mother. Across the hall, in the Second Clinic, the mortality rate was barely 2%. The only difference was the personnel. The First Clinic was the training ground for medical students; the Second was for midwives. It took a man named Ignaz Semmelweis, a Hungarian physician with a penchant for counting what others ignored, to notice the physical traversal of death. He watched the students walk directly from the autopsy room, their hands still slick with the organic residue of the deceased, to the delivery beds of the laboring women.
18%
FIRST CLINIC (Medical Students)
2%
SECOND CLINIC (Midwives)
The staggering “lottery of death” observed by Semmelweis before the introduction of antiseptic protocols.
He didn’t suggest a new miracle drug. He didn’t perform a heroic, midnight surgery to save a dying patient. He simply demanded that the students wash their hands in a solution of chlorinated lime. Within months, the death rate in the First Clinic plummeted to match the Second. Semmelweis had solved one of the greatest medical crises of his era through the radical act of prevention. Yet, his reward was not a promotion or a statue. He was ridiculed, eventually dismissed, and died in an asylum. The medical establishment of the 19th century didn’t want a man who quietly prevented deaths through hygiene; they wanted the high drama of the surgical theater, the visible struggle against an invisible enemy.
The Friction of Design
I thought about Semmelweis this morning when I walked into my office and pushed a door that clearly said “PULL” in brass letters. I felt that familiar, dull heat of minor embarrassment-the tiny friction of being out of sync with the design of the world. It is a small thing, but it’s symptomatic of a larger rot in how we perceive work. We are biologically and culturally wired to reward the rescue, even when the rescuer is the one who left the door unlocked, the stove on, or the server unpatched.
412 individual panes of 14th-century stained glass are currently spread across the workbench of Mason B., a conservator who speaks about lead and light as if they were temperamental children. To watch Mason work is to witness the antithesis of the modern corporate “hustle.” He moves through the studio in a specific, chronological order, beginning with the cleaning of the external crust-a mixture of soot, pigeon droppings, and sulfuric acid rain-before addressing the structural integrity of the lead cames.
If Mason does his job perfectly, the window looks exactly as it did before it began to fail. His success is defined by the absence of his own footprint. If he succeeds, the congregation will look at the window and see the Virgin Mary or a patron saint, never thinking for a second about the man who spent ensuring the glass didn’t succumb to “glass disease” or thermal expansion.
The Elias vs. Marcus Archetype
This is the central paradox of the modern organization. We claim to value stability, but we pay for drama. In the tech sector, I have watched this play out with a rhythmic, almost insulting consistency. An engineer-let’s call him Elias-spends his year writing clean, boring code. He updates dependencies before they become security risks. He documents his work. He goes home at every day because his systems are so well-tuned they don’t require him to be there.
ELIAS (The Maintainer)
✓ Clean, boring, documented code
✓ Proactive security patching
✓ Home by 5:15 PM
REWARD: 2% Raise
MARCUS (The Firefighter)
! “Clever” undocumented code
! Monthly system collapses
! 4:14 AM “Updates from the trenches”
REWARD: Promotion & Hero Status
At the end of the year, his manager looks at his metrics and sees… nothing. No outages. No emergency patches. No Slack notifications. Elias is seen as a “steady” but uninspired performer. He gets a 2% raise and a lukewarm “meets expectations.” Meanwhile, across the hall, there is Marcus. Marcus writes “clever” code that only he understands. He ignores documentation and treats security patches as a suggestion. Naturally, his systems collapse once a month.
When the database crashes on a Friday evening, Marcus stays in the office until Sunday morning, fueled by cold pizza and the adrenaline of the savior. He sends “updates from the trenches” to the entire leadership team at . By Monday, he is a hero. The VP of Engineering gives him a shout-out in the all-hands meeting. He gets a promotion and a spot on the fast track to leadership.
Engineering the Newsroom
We have accidentally created a system that incentivizes arson. If you are rewarded for putting out fires, and the world is currently fire-free, the most rational career move is to light a small, manageable blaze.
This realization hit me hardest while observing the transformation of legacy industries into digital powerhouses. The shift from a 100-year-old print model to a high-velocity digital platform requires a level of engineering discipline that is often at odds with the “breaking news” mentality of a traditional newsroom. In a newsroom, the “fire” is the story. In engineering, the “fire” is a failure of the system.
Reconciling these two cultures requires a leader who can look past the performative exhaustion of the midnight oil. This is the discipline that
brought from his doctoral engineering roots at King’s College London to the executive suite. When you understand the underlying architecture of a system-whether it’s a news organization or a software stack-you begin to value the quiet maintenance of the infrastructure as much as the headline-grabbing rescue.
The problem is that prevention is illegible to the untrained eye. You cannot photograph a crash that didn’t happen. You cannot write a LinkedIn post about the bug that was caught in a code review before it reached production. Visibility is the currency of the modern workplace, and crisis is the most visible thing there is.
The Architecture of Boredom
I recently spent an afternoon walking through a data center, a place where the physical reality of the internet becomes undeniable. It is a landscape of humming black monoliths and miles of neon-colored fiber optic cables.
22°C
Mandated Constant Temperature
+15 Degrees
SILICON FAILURE POINT
is the constant, mandated temperature of the “cold aisles.” The air is dry and tastes of static. In this environment, the “hero” is the cooling system that never fails. If the temperature rises by even 5 degrees, the hardware begins to throttle. If it rises by 15, the silicon begins to die. The engineers who work there don’t want excitement. They don’t want drama. They want the crushing boredom of a system that performs exactly as it was designed to perform.
Yet, when we return to our glass-walled offices, we lose that clarity. We start to crave the “all-hands-on-deck” meetings. We mistake movement for progress and fatigue for productivity. We celebrate the person who “saved the deal” at the last minute, ignoring the fact that the deal was only in jeopardy because they neglected the relationship for six months.
Finding the “Boring” Performers
I’ve had to train myself to look for the “boring” performers. I look for the people who finish their work early and have no “war stories” to tell at the water cooler. These are the people who are actually holding the building up. They are the structural lead cames in Mason B.’s stained glass windows. They are the hand-washers in Semmelweis’s clinic.
The tragedy of the fire-extinguisher hero is that they often become a bottleneck. Because they are the only ones who can “save” the system, they become indispensable. And because they are indispensable, the system never gets fixed. Why would you automate a process if being the manual “fixer” of that process is what gets you your bonus?
We have to stop equating visibility with value. In a world of increasing complexity, the most valuable people are often the ones who make that complexity disappear. They are the ones who simplify the workflow, who automate the redundant, and who predict the failure before it manifests. They are the ones who allow the rest of us to sleep through the night.
I think about that brass door again. Pushing when I should have pulled. It was a failure of design, a small friction that wasted half a second of my life. If the architect had placed a flat plate on the push side and a handle on the pull side, I wouldn’t have had to think at all. The architect would have been “invisible,” and I would have walked through the door effortlessly.
We need more invisible architects in our companies. We need to start looking at the people who make things look easy and realize that the ease is the result of a profound, quiet expertise. Next time someone stays late to fix a crisis, I’ll still say thank you. It’s the polite thing to do. But I won’t give them a standing ovation.
Instead, I’ll save the applause for the person who ensured the crisis never happened in the first place-the one who is probably already at home, having a quiet dinner with their family, while the systems they built hum along in the dark, perfectly, boringly, and entirely without fire.