THE HEROICS TRAP: WHY WE CELEBRATE THE WRONG PEOPLE
In most manufacturing plants, there's a person everyone calls first.
You know the one. She's been there eight years. She knows which valve gets stuck on cold mornings. She can hear a bearing going bad from across the production floor. When the line goes down at 2 AM and the on-call tech can't diagnose the problem, someone calls her — even on her day off, even after hours, even during a vacation she never quite got to take. She always answers.
Her name, in the book I'm working on, is Sarah.
Sarah is excellent. The kind of person who carries institutional knowledge that no training program could replicate, who has accumulated thousands of hours of pattern recognition that makes her faster and more accurate than any system. She is, by any measure, an exceptional contributor.
She is also her organization's most significant reliability risk.
Not because of anything she's done wrong. Because of everything she's absorbed that should have been designed differently.
The Mechanism
High performers hide broken systems. This is not a metaphor. It's a mechanism.
When one person's capability compensates for a gap in the system — when Sarah's diagnostic knowledge fills the documentation gap, when her availability compensates for the planning gap, when her memory compensates for the tribal knowledge gap — the organization never sees the gap. Results are good. Uptime is strong. The quarterly metrics look fine.
From leadership's perspective, everything is working.
From Sarah's perspective, she is the reason everything is working.
She stays late. She answers the phone. She double-checks the work that shouldn't need double-checking. She catches mistakes before they become failures. She remembers the rules nobody wrote down. And because she does all of this, the organization never has to face the consequences of not having done it properly.
This is how broken systems stay broken.
Why We Celebrate It
The heroics trap persists because heroics feel good. Not just for the hero — for everyone watching.
When Sarah gets the line back up at 2 AM, there's relief, gratitude, and a genuine sense that things worked out. She gets recognized. Leadership says thanks. The post-mortem focuses on the fix, not on why the problem occurred in the first place.
Meanwhile, the organizational gaps that created the emergency are still there. The documentation still isn't written. The planning process still doesn't surface developing faults before they become failures. The knowledge still lives in one person's head.
And the next time something breaks, everyone calls Sarah.
The organizations that break out of this cycle do one uncomfortable thing: they separate the acknowledgment of Sarah's effort from the question the situation should be raising. "Thank you, Sarah" — that part is real and deserved. "And here's what this incident tells us about the system" — that part is the one most organizations skip.
Because asking the structural question feels, in the moment of the save, like ingratitude. It feels like criticizing the firefighter instead of celebrating the rescue.
It isn't. But it feels like it.
The Organizational Cost
The heroics trap has three costs that rarely get calculated:
The human cost. Sarah is performing at a rate the organization has never designed a sustainable version of. She's carrying cognitive load that belongs in a process, not a person. The burnout statistics in high-performer populations are not accidents. They're the predictable outcome of organizations that mistake individual capability for systemic resilience.
The resilience cost. The operation is not as reliable as it appears. It is as reliable as one person's availability. When Sarah takes vacation, takes sick leave, or ultimately leaves, the gap she's been filling becomes suddenly, visibly apparent. What looked like a strong organization reveals itself as a strong person holding a fragile one together.
The learning cost. As long as Sarah is there to solve the problem, the organization doesn't have to figure out how to solve it properly. The workaround is the answer. The hero is the system. And the system, left to depend on the hero, never improves.
What to Do Instead
This is not an argument against Sarah. It's an argument for building around Sarah before she leaves.
The question isn't "how do we protect this person" — although that matters. The question is "what would we need to build for this person to take a two-week vacation without anyone calling her?"
That question is clarifying. It forces the organization to name the specific gaps that Sarah fills: undocumented procedures, undesigned training paths, incomplete condition-based monitoring, overreliance on one person's pattern recognition. And it creates a roadmap for addressing them.
The goal isn't to make Sarah unnecessary. It's to make the operation sustainable — so that Sarah's contribution is augmentative rather than foundational, building on a solid system rather than compensating for an absent one.
High performers deserve to operate in organizations that don't extract everything they have and then ask for more.
And organizations deserve to know what they're actually relying on.
Heroics are not a sign of a strong culture.
They're a sign of a system that hasn't been designed yet.