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 note on where knowledge actually sits, and why it leaks.

Every company keeps two maps of what it knows. There is the written one — the documents, the playbooks, the tidy diagrams — and there is the real one, which is held in people's heads and surfaced only when someone asks the right question of the right person at the right time. The gap between those two maps is where most operational pain lives.

Knowledge is a flow, not a store

The mistake is to treat knowledge as inventory: write it down once, file it, done. But what a company knows is constantly going out of date, and the parts that matter most are exactly the parts too tacit or too political to write down. The wiki captures the settled questions. The unsettled ones stay in conversation.

So memory leaks at the edges — when someone leaves, when a team reorganises, when the one person who understood the billing logic takes a month off. The work is not to write more documents. It is to make the real map legible without forcing everything through the bottleneck of someone remembering to update a page.