Green gradient background
Back to the blog

From experience

The best thing we did this year: writing down the company memory

The valuable part was not the summary. It was the contradictions it surfaced inside our own documents, which nobody had ever read side by side.

Company memoryInternal processAgents

Published

For years, the information about our own company sat exactly where it sits in most companies: quotes in email, prices in a spreadsheet with three versions, procedures in a few people's heads, decisions in chat threads. Nothing was missing. Nothing was in one place either.

1

Before

Information everywhere, across dozens of places

2

We gathered the documents

Into one folder, without sorting anything

3

We asked for the memory in writing

Clients, projects, who does what

4

Contradictions in our own documents

Different prices, dead procedures

5

Every agent starts here now

One set of pages, kept current

How it went, in the order it actually happened. Step four was the unexpected one.

What we did not expect

The summary written over the documents told us nothing new about what we do. What it showed was where we disagree with ourselves: the same service quoted differently in two quotes from the same month, a procedure nobody had followed in a year, two people listed as the owner of one client. None of that was visible while each document sat on its own.

What changed afterwards

  • Every new agent starts from the same pages, not from a prompt written from scratch.
  • When a price changes, it changes in one place and every automation sees it.
  • The “how do we do this” conversation has a written answer instead of three verbal ones.
We thought we were writing context for the AI. We were writing our procedures down for the first time.

Terms used here

Company memory
The short set of pages every automation starts from: clients, projects, roles, prices.
Single source
The rule that a fact is written in exactly one place. Without it, versions multiply on their own.

Where to start

  1. 1Gather everything about one process into a folder, without sorting it.
  2. 2Ask for a summary and read it looking for contradictions, not for bad phrasing.
  3. 3Resolve the contradictions in the real documents, then regenerate the summary.
Green gradient background

Recognise a process like this?

Tell us how you work today and we will tell you what automating the repetitive part would actually involve.

Let's talk
    What we changed: company memory | Clean Code Culture