The Map from Memory
Capture knowledge before it disappears
3 min read
Imagine someone hands you a map drawn entirely from memory. The big landmarks are there. The general direction is right. But the side streets are missing, the distances are off, and there's a critical turn that the person who drew it forgot to include because they've made it so many times they don't even think about it anymore.
That's what most company documentation looks like.
The knowledge exists inside the organization. Someone knows how to onboard a new client. Someone knows why the billing workflow has that extra step. Someone knows the workaround for the system limitation that has been there since year one. But it lives in their head, not in a document, and certainly not in a format that anyone else could follow without calling that person first.
The First Way Companies Lose Institutional Knowledge
This is the first way companies lose institutional knowledge: it never gets written down in the first place. Not because people are unwilling, but because the person who knows something so well has a hard time seeing what's worth documenting. The steps that feel obvious to them are the exact steps that are invisible to everyone else. It's the curse of expertise. The more fluent you are in a process, the more likely you are to skip over the parts that someone new would need most.
The Second Way: It Fades
The second way companies lose it is slower and quieter. It fades.
After a project wraps or a quarter closes, teams remember two categories of things clearly: the high-level outcomes and the moments that caused real pain. The big wins, the big misses, the thing that blew up at the worst possible time. Those stick. But everything in between, the small adjustments, the timing that mattered, the vendor who was unexpectedly difficult, the workaround that saved a week, all of that starts to blur almost immediately. And the longer you wait to capture it, the less there is to capture.
This is why retrospectives that happen three weeks after a project ends produce vague takeaways that no one acts on. The details that would have made the next project meaningfully better are already gone. Not because they weren't important, but because human memory prioritizes extremes and drops the middle. And the middle is where most of the useful operational knowledge lives.
The combination of these two problems creates a compounding gap. Knowledge that should have been documented wasn't, and knowledge that was fresh enough to capture accurately faded before anyone wrote it down. Over time, the map gets less and less reliable. New team members can't follow it. Experienced team members fill in the gaps from memory, which means the same undocumented knowledge stays undocumented and the cycle continues.
Building Capture Into How Work Happens
The fix isn't a massive documentation initiative or a retroactive knowledge dump. Those tend to produce a burst of effort that no one maintains. The fix is building capture into the way work already happens. Document processes while they're being done, not after. Run short retrospectives while the details are still sharp, not weeks later. And when someone asks a question that requires tribal knowledge to answer, treat that question as a signal that something needs to be written down.
It doesn't have to be perfect. A rough map drawn in real time is more useful than a polished one drawn from memory six months later.
Key Takeaway
The best time to draw a map is while you're still on the road. Institutional knowledge disappears in two directions at once: the expertise that never gets documented because it feels obvious, and the details that fade before anyone captures them. Build documentation into how work happens, not after it's done, and the map stays accurate enough to actually follow.
If your team's knowledge lives in people's heads instead of in systems, and you're not sure how to start getting it out, I'd welcome a conversation.