Personaas

When your best people leave, your company forgets

There was cake in the breakroom the day Priya left. Nine years, a signed card, diligent handover notes. Everyone felt covered. Three months later, nobody could explain the clause she'd fought for.

There was cake in the breakroom the day Priya left. Nine years, a card everyone signed, a slightly teary speech. Her replacement had shadowed her for two weeks and taken diligent notes. Logins handed over, calendar invites reassigned, the runbook updated. Everyone felt covered.

Three months later a vendor dispute blew up over a clause buried in a renewal contract — an oddly specific clause that made no sense to anyone still in the building. Why was it there? Priya had fought for that clause in 2021, after a delivery failure that cost the company a quarter's worth of goodwill. She knew exactly why it mattered. She just never wrote it down, because to her it wasn't a fact to document. It was simply something she knew.

That's the part the handover never catches. And it's the part that actually runs your company.

The handover captures the "what." It misses the "why."

A good handover transfers tasks. Here's the report that goes out on Mondays, here's who approves expenses, here's the shared drive. All necessary, all transferable, all the stuff you can write on a checklist. What it can't transfer is judgment — the accumulated sense of why things are done the way they are, which shortcuts are safe and which ones bite, who to call when the official process stalls, what was already tried and quietly abandoned.

That knowledge is tacit. People don't know they know it until someone asks the exact right question, and by the time you're asking, the person who knew is gone.

None of this is in the handover doc

  • the reasoning behind decisions nobody wrote down
  • who to actually call when the thing breaks at 2am
  • the quiet workarounds that keep the process running
  • the context that makes the numbers mean something

None of that lives in the wiki. Be honest about the wiki — a good chunk of it is out of date, and the genuinely useful knowledge was never in there to begin with. It lives in Slack DMs, in the margins of old decks, in the head of the one person everyone quietly pings when something's on fire. Your org chart remembers roles. It has never once remembered reasons.

And it's getting worse, quietly

People change jobs faster than they used to. Teams are spread across cities and time zones, so the hallway conversations that used to spread know-how by osmosis mostly don't happen. More of the "how" now lives inside tools and one-off scripts that made perfect sense to the person who built them and are opaque to everyone else.

So every departure is a small brain-drain — rarely catastrophic on its own, easy to wave off. But they compound. Lose enough of them and you become a company that keeps relearning its own lessons, paying full price each time for knowledge it already had and let walk out the door.

A company that forgets what it learns isn't building expertise. It's renting it, one employee at a time.

You can't fix this by asking people to document more

The obvious reflex is a documentation mandate. Write it all down before you go. It never works, for two reasons. First, nobody has time — documentation is the thing that slips when the actual work is on fire, which is always. Second, and more fundamental, people can't document what they don't realise is valuable. The most important knowledge is invisible to the person holding it precisely because it's second nature.

Knowledge that has to be captured as a separate chore mostly doesn't get captured. It has to accrue as a byproduct of the work itself — quietly, while the work is already happening — or it won't happen at all.

What if the knowledge stayed with the company?

Here's the shift worth sitting with. Right now, in most organisations, institutional knowledge is stored in individuals. When they leave, the storage leaves with them. What if it accrued to the organisation instead — every decision, every resolved ticket, every workflow captured, structured, and reusable, so the know-how outlasts any one person's tenure?

That's the difference between a company that gets measurably smarter every year and one that resets a little with every resignation. It's also one of the specific things we built Personaas to do. A persona trained on how your organisation actually works turns everyday work into organisational knowledge as a side effect of doing the work — not a separate documentation project nobody has time for. So when the next Priya leaves, the reason that clause exists doesn't leave with her. It's still there, still answerable, still yours.

Here's a test worth running honestly. If your single most experienced person won the lottery and quit tomorrow, how much of what they know would you have to relearn the hard, expensive way? For most companies the answer is uncomfortable. It doesn't have to be — but only if you stop treating the knowledge in people's heads as something you'll get around to capturing later. Later is usually their last day.

More from the blog