--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: Institutional Memory slug: institutional-memory type: distributed knowledge system status: unstable version: 0.0.n released: unknown maintainer: whoever has been here the longest dependencies: - long-tenured employees - oral tradition - that one wiki nobody updates - informal lunch circuits - fear of asking obvious questions license: proprietary, non-transferable, expires on resignation tags: - organizations - knowledge - fragility - humans - legacy systems ---
The accumulated knowledge of how things actually work, as opposed to how the documentation says they work.
Institutional memory is not stored in any single place. It distributes itself across the nervous systems of people who have been present long enough to witness consequences. It propagates through gossip, hallway conversations, and the raised eyebrow of a senior employee when someone proposes something that was tried in 2014.
The storage mechanism is entirely biological. This is considered a known bug, not a design choice.
Key transmission vectors:
| Bug | Severity | Status |
|---|---|---|
| Stored entirely in humans | Critical | Won't fix |
| Non-transferable via email | High | Open |
| Corrupts during layoffs | Critical | Recurring |
| Inaccessible to new hires for 6 to 18 months | High | By design, apparently |
| Holders often unaware they hold it | Medium | Philosophical |
| Version conflicts when old-timers disagree | Medium | Unresolvable |
When the last person who knows why the legacy system does the thing it does leaves the company, institutional memory does not disappear cleanly. It becomes institutional mythology: a set of origin stories told with decreasing accuracy, usually invoked to justify not changing something.
Also: when an organization grows fast enough, institutional memory fails to scale. New employees outnumber carriers. The memory becomes minority knowledge. This is how a five-year-old company forgets what it learned in year two.
retention_strategy:
documentation: aspirational
exit_interviews: underused
knowledge_base: outdated
apprenticeship: deprecated_in_most_orgs
decay_rate: proportional_to_attrition
backup_frequency: never
restore_tested: false
Can you export it? People have tried. The result is usually a Confluence page with seventeen sections and no search tags.
What happens when it's gone? The organization re-learns the same lessons. This is sometimes called innovation.
Who owns it? Nobody. Which means it belongs to whoever is about to quit.
Is it documented anywhere? Yes. In the commit history that nobody checks and the Slack threads that expired six months ago.
Institutional memory is automatically deprecated when its last carrier accepts another offer. No migration path exists. Plan accordingly.