What we mean by 'organizational memory'
A short definition, a longer explanation, and the working principles we use to build the product.
When we say 'organizational memory,' we mean the system that retains, structures, and serves the operational knowledge a company runs on — the how, the why, the who, and the when. Not the documents. The actual knowledge.
A useful organizational memory is voice-led at capture because nobody types out their tacit knowledge. It is graph-shaped at rest because the relationships matter more than the nodes. It is permission-aware at retrieval because a memory you cannot govern is a liability. And it is operational at the edges because a memory you cannot act on is just trivia.
Those four properties are how we evaluate every product decision we make. If a feature does not contribute to one of them, we delete it. If a feature contradicts one of them — for example, a workflow that requires writing a doc before capture — we redesign it. It is a constraint, and the constraint is the product.