Brenda is clicking her pen with a rhythmic, almost surgical precision, counting down the last 107 minutes of her shift before she disappears into the blue horizon of a three-week Alaskan cruise. Her desk is currently the most popular destination in the office, a temporary pilgrimage site for desperate middle managers and panicked juniors. They aren’t there to wish her a bon voyage. They are there because Brenda is the only person on the payroll who understands the legacy billing architecture-a sprawling, Frankensteinian mess of COBOL and hope that processes 47 percent of our monthly revenue. If that system hiccups while she is watching glaciers melt, the company doesn’t just slow down; it ceases to function as a liquid entity. We are watching a single point of failure put on a sun hat and pack a suitcase.

The Stinging Realization

Watching this panic unfold reminds me of the time I spent at a crowded terminal, where I caught someone’s eye and waved back with frantic enthusiasm, only to realize they were waving at their spouse standing directly behind me. That stinging, hot-cheeked realization that you have misread the room-or your own importance-is exactly what companies feel when their ‘indispensable’ employee finally leaves. We mistake the hoarder for a hero. We think the person who ‘knows everything’ is an asset, when in reality, they are a structural crack in the foundation that we’ve decided to cover up with a nice rug. This isn’t just Brenda’s fault; it’s a management culture that prioritizes the immediate comfort of having a ‘fixer’ over the long-term health of a transparent system.

Sky H., a typeface designer I know who obsesses over the minutiae of kerning and the structural integrity of a lowercase ‘g’, once told me that the most beautiful font is useless if the master file is locked in a dead man’s drawer. Sky spends 37 hours a week documenting the ‘why’ behind the curves, ensuring that if they were to vanish tomorrow, the work could continue. Sky understands something that Brenda’s bosses don’t: true expertise isn’t about being the only one with the keys; it’s about building a door that everyone knows how to open. In the world of high-stakes design, Sky is a rarity. Most people in technical or creative roles find a dark, quiet corner of the workflow, build a nest of proprietary knowledge, and wait for the organization to become dependent on them. It’s a survival mechanism, a way to ensure that in the next round of layoffs, your name is written in permanent ink because nobody else knows how to run the 7-year-old script that generates the end-of-quarter reports.

The hoarder’s throne is built on the silence of their peers.

– The Cost of Secrecy

When we look at the cost of this silence, the numbers are staggering. We aren’t just losing time; we are losing the ability to evolve. If it takes 27 steps to authorize a simple refund because only Brenda knows the override code, that’s 27 opportunities for a mistake to happen. It’s 27 moments where the company is choosing to be fragile. We reward this. We give Brenda a ‘Reliability Award’ and a $777 bonus, never stopping to ask why the reliability of a multi-million dollar firm is resting on the shoulders of a single human being who is prone to the flu, better job offers, or, in this case, a boat in the middle of the Pacific. We have romanticized the ‘wizard’ who saves the day, forgetting that if the system worked correctly, we wouldn’t need a wizard at all.

Building the Cage

I’ve been that person. I once held onto a specific client relationship like it was a holy relic, refusing to share the contact logs or the specific nuances of their temperament. I thought I was making myself un-fireable. In reality, I was just making myself exhausted. I couldn’t take a day off without 17 missed calls. I couldn’t move to a different department because I was ‘too valuable’ where I was. I had built a cage out of my own secrets and called it job security. It’s a miserable way to exist, constantly looking over your shoulder to see if someone has finally figured out your ‘method’ and rendered your gatekeeping obsolete.

This is where we have to look at the tools and the philosophies we surround ourselves with. A truly reliable system-whether it’s a software stack, a manufacturing process, or a piece of safety equipment-doesn’t rely on a secret handshake. It relies on being fundamentally sound and predictably accessible. When you look at high-performance gear, like the products from Revolver Hunting Holsters, the value isn’t in some hidden trick that only one person can perform. It’s in the deliberate, transparent engineering that ensures the tool works every single time, for anyone who needs it. Resilience is about removing the mystery. It’s about ensuring that the ‘how’ is so well-integrated into the design that the ‘who’ becomes secondary to the mission.

Sky H. recently finished a project where they had to hand over 57 different weights of a custom sans-serif. Instead of just sending the files, Sky included a 97-page manual detailing every design decision, every alternate character, and every potential pitfall for future editors. That is the behavior of a professional who values the work more than their own ego. It takes a certain level of confidence to make yourself replaceable. It requires you to believe that your value lies in your ability to create and innovate, not in your ability to sit on a pile of information like a dragon guarding a hoard of useless gold coins.

But the hoarders aren’t the only ones at fault. Managers often allow this to happen because documentation is boring. It’s not ‘billable’ in the way that fixing a crisis is billable. It’s much easier to let Brenda handle it than it is to force Brenda to spend 47 hours writing down everything she does. We prioritize the fire-extinguisher over the fire-proofing. We wait until the smoke is billowing out of the server room to realize that we don’t know where the keys are. It’s a failure of imagination, a refusal to believe that the ‘indispensable’ person could ever actually be gone.

❝

Documentation is an act of love for your future self.

– Knowledge Transfer

Killing the Cult of the Hero

If we want to build something that lasts, we have to kill the cult of the hero. We have to stop celebrating the person who stays until 11:07 PM to fix a problem they are the only ones capable of fixing. Instead, we should be asking: ‘Why was this a problem only you could fix?’ and ‘How do we make sure it never happens again?’ We need to incentivize the sharing of knowledge as much as we incentivize the acquisition of it. Imagine a world where Brenda’s performance review was based on how many other people she taught to run the legacy billing system. Suddenly, the cruise isn’t a source of panic; it’s a non-event. The system keeps humming along at 97 percent efficiency, and Brenda gets to actually enjoy her vacation without her phone vibrating in her pocket every time a batch file fails to load.

I think back to that moment at the airport, waving at a stranger. The embarrassment came from the realization that I was projecting a connection that wasn’t there. Companies do the same with their key employees. They project a sense of stability onto a person who is ultimately just a person. We are all just people. We are all 777 miles away from a total change in perspective. When we build systems that require a specific human to be present at all times, we aren’t being savvy; we are being reckless. We are gambling with the future of everyone else in the building for the sake of avoiding a few uncomfortable conversations about process and transparency.

Sky H. once said that the ultimate test of a design is whether it survives the designer. If your company cannot survive a three-week absence of its top performer, you don’t have a company; you have a hostage situation. It takes 397 days, on average, for a company to fully recover from the loss of a ‘knowledge hoarder’ who leaves without a transition plan. That’s over a year of stumbling, of relearning lessons that should have been written down, of apologizing to clients for ‘unforeseen technical difficulties’ that were entirely foreseeable the moment we let one person become the sole guardian of the truth.

As Brenda finally closes her laptop and walks toward the elevator, the tension in the room is palpable. Someone mentions that there are 77 pending tickets that might need her attention. She just smiles, waves-a real wave this time, directed at everyone-and the doors slide shut. The silence that follows is the sound of an organization realizing it has no idea how to walk on its own two feet. It’s a cold, sharp realization, but maybe it’s the one we need. Maybe this time, when she comes back, we’ll stop treating her like a goddess and start treating her like a teammate. Because a goddess is someone you pray to when things go wrong, but a teammate is someone who makes sure things go right even when they aren’t there to be found.

We have to stop building monuments to the indispensable and start building systems that can survive the reality of being human. We need the resilience of a well-made tool, the clarity of a well-designed font, and the courage to admit that no one person should ever be the only thing standing between us and the void. It’s a long road to transparency, maybe 807 miles long, but it’s the only one that doesn’t end in a shipwreck.

We have to stop building monuments to the indispensable and start building systems that can survive the reality of being human. We need the resilience of a well-made tool, the clarity of a well-designed font, and the courage to admit that no one person should ever be the only thing standing between us and the void. It’s a long road to transparency, maybe 807 miles long, but it’s the only one that doesn’t end in a shipwreck.