What a company knows, and where it keeps forgetting it

Institutional memory does not live in the wiki. It lives in three people, two of whom are on holiday. A short note on where a company's knowledge actually sits, and why it keeps leaking out.

Every company keeps two maps of what it knows. There is the written one: the documents, the playbooks, the tidy architecture diagrams that look great in an onboarding deck. Then there is the real one, which lives in people's heads and only surfaces when somebody asks the right question of the right person at the right moment. Most operational pain lives in the gap between those two maps.

Knowledge is a flow, not a store

The standard mistake is to treat knowledge like inventory. Write it down once, file it under the correct heading, consider it handled. But what a company knows is going stale all the time, and the parts that matter most are usually the parts that are too tacit, too political, or too awkward to write down. The wiki ends up holding the settled questions. The unsettled ones, which are the expensive ones, stay in Slack threads and hallway conversations.

So memory leaks at the seams. Someone leaves. A team gets reshuffled. The one engineer who genuinely understood the billing logic takes a month off, and a routine change turns into an archaeology project. Writing more documents nobody reads will not close that gap. What helps is making the real map legible without forcing every useful thing through the bottleneck of one person remembering to update a page.