The screen glare was brutal, a chemical burn behind the eyes at 11:54 PM. I was sitting where David sat in the scenario-that terrible, cold rush when the scope of the disaster clarifies. Not a slow leak, but a catastrophic implosion built into the fourth column of the Excel sheet. $474 million in projected revenue was actually $4.74 million. An error of 99% that had somehow passed through three different senior reviews and was scheduled to hit the client’s inbox in under 6 hours.
I fixed it. The keystrokes were frantic, the formulas screaming defiance, but I wrestled the beast into submission. The next morning, the praise rolled in, warm and thick like cheap syrup. “Great catch,” “David saved us,” “Heroic effort.”
I smiled, accepted the admiration, and then spent the rest of the day feeling utterly hollowed out. I hate the phrase “Good Catch.” I despise it. I detest the culture that deems it a high compliment.
1. The Seduction of Necessity
The truth is, I thrive on it sometimes. That adrenaline spike-that validation that you are, in fact, the essential gear in a broken machine-is addictive. I’m the one who insists we shouldn’t need last-minute heroes, yet when I get the call at 3 AM because the deployment failed, I answer instantly, fueled by that sick, gratifying feeling of being necessary.
This feeling is seductive, powerful, and utterly corrosive to any attempt at true resilience.
The Concealed Flaws
Just last week, I caught myself doing something profoundly stupid, an echo of a mistake I should have learned from years ago, concerning a boundary I thought was securely cemented. It was an oversight born of distraction, a momentary lapse that could have been disastrous if I hadn’t realized the potential fallout just before sending the message.
The self-criticism was intense. Why do we keep making the same predictable errors? It’s often easier to admit a monumental mistake in public-a spreadsheet error-than to admit the quiet, habitual failures of attention that precede it. We try to patch the public image while the private system remains flawed.
The Visibility Dichotomy
The Visible Fix (Heroics)
The Invisible System (Prevention)
The underlying frustration is this: The Good Catch is the visible, dramatic work. The fixing. But the vital work-the architectural work, the training, the redundancy, the sanity checks that prevent the mistake from reaching that point-is invisible, boring, and, crucially, unrewarded.
The Unsexy Standard: Oscar A. and Parallel Checks
If I fix an error that would have cost the company $474 million, I get a bonus and public praise. If I spend three months implementing a system of double-blind verification and automated reconciliation that ensures that error can never happen, nothing happens. Life proceeds normally. No crisis was averted, because no crisis was allowed to brew. The silence of prevention is deafeningly boring, yet it represents true success.
This brings me to Oscar A., an elevator inspector I met some time ago while we were discussing high-reliability organizations (HROs). Oscar’s job is profoundly unsexy. He doesn’t celebrate “Good Catches.” If Oscar finds a safety mechanism failing on the 54th floor, he doesn’t wait for a high-speed catastrophe to fix it; he shuts it down.
Oscar explained that in his world, a “Good Catch” is fundamentally an admission of system failure. If the only thing separating a thousand people from a plummeting cable is the sharp eye of Inspector A during a routine check, the entire design process, manufacturing sequence, and maintenance schedule are broken. The system should have stopped the elevator long before Oscar arrived.
“I’m supposed to verify the integrity,” he told me, rubbing grease from his knuckles. “I’m not supposed to be the last firewall.” He spoke about the mean time between failures (MTBF). They didn’t aim for a high MTBF; they aimed for a system where critical components had parallel, independent checks designed in four distinct layers. Four layers. He emphasized that number. It wasn’t about heroic effort; it was about boring, predictable redundancy.
2. The Architecture of Improbability
Think about the incentives. When David fixes the $474 million error, he is rewarded for being a brilliant firefighter. His incentive is to stand ready for the next fire, because that’s where the visibility, the praise, and the career mobility are found. Nobody wants to be the person who spends their entire career building perfect fire alarms that never go off.
Why? Because human beings crave narrative. We love the savior story. Prevention is non-fiction; it’s a dry, technical manual written by someone nobody knows.
Shifting the Incentive: Rewarding Invisibility
The risk of the “Good Catch” culture is that it elevates firefighting to a core competency. It means the most senior people spend their time auditing the frantic work of others instead of designing bulletproof infrastructure.
3. The 4:1 Rule: Consequence for Visibility
Visibility Track (Hero Recognition)
1 Recognition Event
System Accountability Track (Post-Mortem)
400% Investigation Time
The effect was instant. People stopped broadcasting their heroic catches. Why? Because being the hero now meant triggering an arduous, uncomfortable inquest into why the process failed. The incentive shifted from visibility (Hero) to accountability (System Owner).
If you want to see an example of where absolute structural, functional, and aesthetic precision meet relentless quality control, consider the dedication applied to highly specialized collectibles. It reminds me of the obsession with intricate, delicate works that require perfect execution upfront, where a single structural flaw destroys the value. Items like the beautifully detailed, hand-painted boxes, requiring absolute attention to detail in their construction and firing process. They are celebrated not for being fixed, but for being flawless from inception. Limoges Box Boutique represents this principle perfectly. This focus on initial, non-negotiable quality is something organizations should emulate, demanding systemic strength rather than relying on individual talent to patch up organizational weakness.
The True Financial Burden
This reliance on reactive heroics also has a profound cost in human capital. The burnout rate for those designated ‘catchers’ is astronomical. They are the only ones who understand the broken system enough to fix it, so they are the only ones called. They are rewarded with recognition that feels wonderful in the moment but guarantees their continued enslavement to dysfunction.
We happily pay $10,000 in bonuses to the person who caught the error, because it saved us $474 million. But we refuse to fund the $50,000 project to automate the data feed reconciliation that would prevent the error from ever manifesting, because that’s seen as an expense that produces ‘nothing’ (i.e., no spectacular save).
What we need to value is the invisible worker. The person who writes the clean documentation. The architect who designs the system to be fault-tolerant, not just fault-detecting. That person is often overlooked, underpaid, and dismissed as “back office.” But that person is the one securing the foundation.
4. Pillars of Resilience
Clean Docs
No tribal knowledge
Redundancy
Parallel checks designed
Self-Correct
Auto-reconciliation
The Quiet Dividend
The most critical task we face in building genuinely high-quality organizations isn’t teaching people how to spot errors; it’s designing environments where errors are statistically improbable, structurally contained, and instantly self-correcting. We must stop celebrating the symptoms of failure.
Show me the organization where the most visible person is the one who designs the quiet, boring processes, and I will show you an organization that will last.
True expertise is found not in the ability to fix what is spectacularly broken, but in the dull, relentless focus required to ensure nothing breaks in the first place. That’s the work that pays $4,004 in dividends every single year. The silence is the sound of success. Everything else is just drama masking institutional decay.
The Necessary Pivot
So, the next time someone offers you praise for a “Good Catch,” accept it politely, but immediately pivot. Ask, in front of the whole team: “I’m glad we avoided disaster, but I need to understand exactly what mechanism failed upstream that required a human safety net in the first place.”
Do not reward the firefighter. Reward the person who built the fireproof wall. That’s the only way we stop rewarding failure.