The Day Jamie Disappeared

Jamie could fix anything. Not in the mythical 10x way. She wasn’t writing elegant code or closing impossible deals. She simply knew things. Like: where the invoicing system kept its grudges, why Customer X got billed differently than everyone else, and which vendor payments could be delayed and which would trigger angry, escalating emails.

We called it “tribal knowledge,” but really it was Jamie knowledge. She’d been there since the early days when everything was duct tape and good intentions. Over five years, she’d absorbed every weird exception, every Band-Aid fix, every “just this once” decision that had hardened into permanent process.

Then she went to Bali for three weeks.

Day one: fine. Day three: a billing dispute we couldn’t untangle. Day seven: the monthly reconciliation that nobody else knew how to run. By day ten, we were archaeologists, digging through old Slack threads like ancient tablets, trying to decode decisions made in meetings we’d never attended.

The beautiful irony? Jamie had documented everything. Meticulously. But documentation and knowledge transfer are different animals. Her notes read like technical poetry — precise, but written as if everyone else could read her mind.

"Run monthly billing sweep but check for Edge Case 3 first."

What was Edge Case 3? None of us knew. Jamie did. Jamie was in Bali.

The Myth of Magical People

Here’s the seductive lie we tell ourselves: if we just hire good people and get out of their way, everything will sort itself out.

It sounds reasonable. It feels generous. It’s also completely backwards.

Work isn’t Tetris. You can’t just drop talented pieces into place and watch them click together perfectly. Even the “right” hire might be wrong for this team, this season, this particular collection of broken processes that somehow still generates revenue.

But we keep chasing unicorns. The engineer who can architect their way out of any technical debt. The salesperson who closes deals others couldn’t even get meetings for. The operations wizard who makes complexity disappear with a few keystrokes and some Excel magic.

I’ve seen companies restructure entire departments around one person’s edge-case brilliance. I’ve watched teams postpone critical decisions until their star player returned from vacation. I’ve been in meetings where the answer to “How do we handle this?” was genuinely “We ask Sarah.”

The problem isn’t that these people don’t exist or aren’t valuable. They absolutely are. The problem is what happens when they leave.

And they always leave.

The Quiet Collapse

High performers have bad months. They burn out. They take better jobs. They move cities, start families, go back to school. Sometimes they just need a break from being the person everyone asks.

When they go, the collapse isn’t dramatic. It creeps in, like a support beam quietly rotting behind drywall.

The weird billing case that only made sense if you knew the backstory, or the customer relationship held together by someone’s particular phone manner, or the monthly report that worked because one person remembered to check three different systems and reconcile the discrepancies by hand.

None of this feels urgent until it is: when you’re standing in the wreckage, realizing you didn’t have a system at all. You had a person doing system-shaped work, and now they’re gone.

I watched this happen to a startup that built their entire customer success function around one remarkable account manager. She could defuse any situation, translate between technical and business teams, and somehow make angry customers feel heard even when she couldn’t solve their actual problem.

When she gave notice, the founders panicked. They offered more: money, equity, flexible schedules. She took a role at a nonprofit because she wanted to work on something that mattered to her.

Within six months, three major accounts had churned. Not because the product was worse, but because nobody else knew how to navigate the invisible dynamics that kept those relationships stable. The knowledge had walked out the door.

What Actually Endures

Durable systems survive individual departure. They degrade slowly and visibly. Most importantly, they can be repaired without heroics.

Think about the financial model that still makes sense three CFOs later. The sales process that generates consistent results regardless of who’s running it. The onboarding sequence that turns confused new hires into productive team members without requiring a dedicated mentor.

These systems share a few traits. They are designed for handoffs, not heroes. They favor clear defaults over human judgment calls. They write down the weird stuff, especially the weird stuff. And they are tested by absence, not presence.

The best way to evaluate a system isn’t to watch it work when everyone’s around. It’s to see what happens when key people aren’t.

The Hidden Weight of Heroes

There’s a particular exhaustion that comes from being the person everyone asks. It starts slowly. You solve a problem here, untangle a mess there. You’re helpful. You’re competent. People notice.

Then it compounds. You become the default escalation point, the safe pair of hands, the one who just figures it out. The expectation settles in quietly: they’ll handle it. They always do.

I’ve been that person. It feels good at first. You’re valuable, needed, maybe a little indispensable.

Indispensability is a prison disguised as a promotion.

You can’t take real vacation because things break when you’re gone. You can’t delegate because nobody else knows the full context. You can’t even change roles easily because you’ve become the load-bearing wall in a structure that wasn’t designed to stand without you.

Meanwhile, the organization never develops the muscle memory to function independently. Why would they? You’re still there. You keep figuring it out.

The cruelest part is that this often happens to your best people. They have the competence to solve problems and the conscientiousness to follow through. So they become systems administrators for processes that should have been systematized long ago.

Building for Absence

Resilient systems aren’t magical. They aren’t even particularly elegant, but they are designed around a simple principle: they work when people can’t.

This means documenting not just what to do, but why. Not just the happy path. Weird edge cases too. Not just the final decision, but the context that led to it.

It means creating defaults that handle most situations automatically, so judgment only gets applied where it actually matters. It means regular testing, regular maintenance, regular questions about whether something still makes sense.

Most importantly, it means accepting that no individual person should be irreplaceable, no matter how talented they are.

The Slow Work of Tending

Systems decay by default. Left alone, they collect exceptions, workarounds, and cruft until they’re unrecognizable. The elegant process becomes a maze of special cases. The clean handoff becomes an oral tradition passed down through confused new hires.

Maintenance isn’t glamorous. It’s the slow, seasonal work of tending. Checking on things that look fine. Updating documentation that’s mostly correct. Simplifying processes that have grown cluttered with age.

It’s admitting that what worked when you were 10 people might not work when you’re 50. That the scrappy startup workaround has an expiration date. That good enough eventually stops being good enough.

The companies that do this well don’t celebrate heroics. They honor maintenance. They make tending normal, expected, part of how work gets done. They allocate time for it, measure it, reward it.

They understand that taking care of systems is a way of taking care of people. Because sustainable work happens in sustainable systems. And sustainable systems don’t require anyone working unsustainable hours to keep them going.

When the Star Player Leaves

Eventually, your most indispensable person becomes dispensable. Not because they’ve lost their touch, but because they’ve found a better opportunity, a different path, a life that doesn’t revolve around being the person everyone asks.

The unraveling is slow and quiet. The kind of quiet that breaks things. A process stops working, and a customer relationship goes cold. A report nobody knows how to build fades into memory.

In a resilient organization, this doesn’t become a crisis. It becomes a prompt to document what was undocumented, and systematize what was personalized. To spread knowledge that was stuck in one brain for too long.

The goal isn’t to make people replaceable. It’s to make knowledge transferable, processes learnable, and systems maintainable by people who are allowed to take time off.

What Stays

The best systems don't draw attention to themselves. They work. When someone new joins and says, "This makes sense," and mean it, that's the win.

Sarah built something that lasted longer than her tenure. Not because she was irreplaceable, but because she made herself unnecessary. The processes didn’t bear her name. The documentation didn’t need her translation.

When she left, the work continued. Not as a tribute, but as proof she did it right.

Six months later, no one talks about the Sarah era. They just do the work.

Which means she’s still there, in the best possible way: invisible, essential, durable.

Like this? Subscribe via email here.