In this articleContents
  1. 1. Institutional amnesia is expensive and invisible
  2. 2. Why documents do not solve it
  3. 3. What a working memory actually holds
  4. 4. Who fills it in? Mostly, the work does
  5. 5. Three properties that make memory useful
  6. 6. What changes in practice
  7. 7. Where the memory lives
  8. 8. The point

Your Marketing Team Should Not Have to Start From Zero Every Time

Most marketing organisations know far more than they can use. The problem is not how much they remember. It is that what they know rarely reaches the work that needs it.

24 September 2026 · 6 min read

1. Institutional amnesia is expensive and invisible

Marketing teams rarely lose information in one dramatic moment. They lose it a little at a time.

A new campaign starts with a new brief that repeats questions answered last year. A strategy deck is rebuilt because the previous one cannot be found, or can be found but nobody knows whether it is still valid. Someone who led the last launch moves on, and the reasons behind a dozen choices leave with them. A test that failed two years ago is proposed again, with the same confidence as the first time.

None of this shows up in a report. It shows up as time, as repeated debates, and as decisions made more slowly — or more boldly — than the company's own history would justify. And it is not a one-off cost. It is paid again at every planning cycle, in every market, by every team that has to rediscover what another team already knew. In an organisation spread across countries and functions, that is the real brake on decision velocity: not how fast people think, but how long it takes them to find out what has already been decided.

2. Why documents do not solve it

Most teams already have plenty of documents. The trouble is what documents hold.

  • Files store outputs, not decisions. A deck shows the chosen message. It rarely records the alternatives, the reasons, or who signed off.
  • Search finds text, not state. You can find the brief that mentions a target audience. You cannot tell from it whether that audience was approved, merely proposed, or replaced three months later.
  • Evidence ages silently. A market figure quoted in a plan was true when it was written. The document does not know that it is now eighteen months old.

A drive full of files is a record that something happened. It is not a memory the work can use.

3. What a working memory actually holds

A memory that helps the next piece of work keeps a different kind of material:

  • Decisions, with their rationale, their owner and the date they were taken.
  • Evidence, with its source and its age, so it can be checked and so its freshness is visible.
  • Assumptions, written down, and marked as tested or still untested.
  • Constraints: brand rules, budget boundaries, commitments that limit what can be done.
  • Outcomes, and how the team interpreted them.
  • Validated learning: what the team now knows because an outcome supports it.
Company Memory: past decisions, evidence, constraints, outcomes and validated learning flow into the current piece of work — a brief, a plan, a review or a decision.COMPANY MEMORYPast decisionssource · stateEvidencesource · stateConstraintssource · stateOutcomessource · stateValidated learningsource · stateCURRENT WORKBrief · plan · review · decisionstarts from what the company already knowsUse relevant context · preserve provenance · keep ownership human
Past decisions, evidence, constraints, outcomes and validated learning flow into the current piece of work.COMPANY MEMORYPast decisionssource · stateEvidencesource · stateConstraintssource · stateOutcomessource · stateValidated learningsource · stateCURRENT WORKBrief · plan · review· decisionstarts from what the company knowsUse relevant context · preserve provenance ·keep ownership human
The relevant past comes to the work, with its source and its state.

4. Who fills it in? Mostly, the work does

The first objection any experienced leader raises is the right one: who is going to enter all of this? If the answer is "your team, in a new tool, after the meeting", the memory will be out of date within a month.

So the memory is not built by transcription. Existing documents, the CRM and analytics are read where they live, not copied. And most of what matters is captured as a by-product of the work itself: when a recommendation is reviewed and a decision is taken, what was decided, by whom and on which evidence is recorded at that moment, not reconstructed later. The team's job is to review and correct, not to type.

5. Three properties that make memory useful

Provenance. Every item says where it came from, so anyone can check it instead of trusting it.

State. Every item says what it is: decided, proposed, superseded, still open. The difference between "we agreed this" and "someone suggested this" is often the whole argument.

Relevance. The memory does not wait to be searched. When a new initiative starts, the parts of the past that bear on it come to it: the earlier decision on the same audience, the test in an adjacent market, the brand constraint that applies.

6. What changes in practice

An illustrative example, not a customer story.

A team is asked to plan an entry into a new market. Without a working memory, the first week goes to archaeology: finding who ran the last expansion, what the audience definition was, whether a pricing test was ever done, which brand rules were bent last time and why.

With a working memory, the plan starts from what is already known. The earlier audience decision is there, with its rationale and the evidence behind it — and with a note that one of its assumptions was never tested. The result of a similar test in an adjacent market is there, together with how it was interpreted at the time. The brand constraint that applies is visible before anyone writes a line of copy. The team still has to decide. It just decides from the company's history rather than from a blank page.

7. Where the memory lives

Company Memory is not a new place to copy everything into. Your documents, your CRM and your analytics stay where they are and stay authoritative. Olymuse reads what it needs where it lives and keeps what those systems do not: the decisions, their reasons and the learning that connects them.

And because a memory can be wrong, it stays open to review. Items carry their sources. Anything can be questioned, corrected or retired. The memory is there to inform the team's judgment, not to replace it.

8. The point

A marketing team should get better at its own work over time, not reintroduce itself to its own history every quarter. That starts with keeping what the company already knows close to the work that needs it.

Your team should not have to start from zero. Most of the time, it does not need to.

Frequently asked

Isn't this just a better knowledge base?

No. A knowledge base answers "where is the file?". A working memory answers "what should this piece of work remember?" — decisions, their status, the evidence behind them and what was learned.

What stops the memory from filling up with outdated or wrong information?

Provenance and state. Every item carries its source and its date, and is marked as decided, proposed or superseded. Only what an outcome supports is treated as learning.

Do we have to migrate our documents?

No. Your systems remain the source of record. The memory reads what it needs where it lives.


This is the third of three launch articles. Read the first: Start Anywhere. Align Everything. · Olymuse is in founder-assisted private alpha. Apply for the Private Alpha →

Applications are open for the founder-assisted private alpha.

A marketing operating layer above the stack you already run. You stay the decision-maker.

Apply for private alpha