The client’s question was small: “How should we organize our files so the AI can use them?”
The honest answer was uncomfortable: the question is too small.
The company, a Swiss firm of fewer than twenty people, excellent at what it does, did not have a filing problem. It had a memory problem.
Knowledge with an address
The company knew a lot. But the knowledge had an address: two heads.
How decisions get made here. What works with which client. Why a proposal sounds this way and not another. Which mistakes are never repeated. None of it was written anywhere. All of it was in use every day.
The test came uninvited: one of the two spent two weeks on vacation. Two proposals sat waiting. A client question stayed open because nobody was sure what this client had already been promised. The team wasn’t weak. The knowledge was on vacation.
The documents? They existed. Folders, neatly labeled, years of projects. But documents are not knowledge. Documents are what remains when you leave out the how.
And the AI the company had brought in sounded like everywhere else: correct, generic, replaceable. Every answer needed rework. Not because the model was weak. Because it didn’t know the company.
What got built
Not a tool. A layer.
I documented the company the way companies are rarely documented. Not the processes first. The self-understanding first: how decisions are made here, how this company speaks, what must never happen, what quality means. Then the expertise, organized by use, not by folders.
Then the part that matters: the layer is alive. Work leaves traces. The machine suggests what belongs in the memory. A human decides. The memory stays current without anyone maintaining it.
A wiki stores and ages. A memory develops.
What changed
New people no longer ask the hallway. They ask the house: how do we handle payment terms? What did we promise this client? The answer comes in the company’s tone, with its logic, with its limits.
Proposals, summaries, client texts: first drafts that need a review, not a rebuild. And the thousandth answer still sounds like the house, not slowly like the internet again.
And the two heads? They still work there. But the company no longer rests on them. The next vacation is just a vacation.
Who the memory is really for
The part that surprises most people: the memory is not built for the AI. It is built for the company. The AI is just the first to use it.
Models come and go. A memory stays. Switch the model, and the memory moves with you.
The client asked for a folder structure. What he got is a company that can explain itself.
Knowledge that lives in people leaves with them. Knowledge that lives in the company stays.
Patrick Thole, Disruption Dynamics, Zürich
disruption-dynamics.ch