Company Brain and context

What is organisational memory? Definition and examples

Also: Institutional memory, tribal knowledge, decision log

In short

Organisational memory is what a company knows and keeps about itself: decisions, experience and reasons, independent of individual people. It sits in documents, systems and heads, and it fades when nobody looks after it.

Why it matters: Your company learns instead of repeating the same mistakes with every change in the team.

Why does Organisational memory matter for your company?

When an experienced person leaves, the company often loses more than a pair of hands. The reasons for earlier decisions, contacts and lessons from failed attempts leave too. The team makes the same decisions again, sometimes with the same mistakes.

A well-kept organisational memory records what was decided, why and what was learned. With AI agents it matters even more: they only work as well as the memory they read from.

Organisational memory in detail

Tribal knowledge

Tribal knowledge is knowledge that exists only in certain people's heads and is written down nowhere. It makes teams fast while everyone is around and slow as soon as someone is missing. AI agents cannot reach it at all.

Every company has people everyone asks: the ones who know why a customer has special terms, which system is fragile or who really decides. That knowledge is valuable but fragile. A holiday, an illness or a resignation is enough, and it is gone.

Decision log

A decision log records what a company decided, why and by whom. It also shows what no longer applies, so people and AI agents work from the current state.

Many decisions live only in meeting notes, emails or chat threads. After a few weeks nobody knows exactly what was agreed or why. The result is repeated debates and teams working from different states.

Example: The pricing debate that keeps coming back

The leadership team is discussing a freemium model for the third time. The two people who ran the first attempt have left. Nobody knows exactly why it was stopped back then.

With an organisational memory, leadership finds the earlier decision with its reasons and figures within minutes. It checks what has changed since and decides on that basis instead of from scratch.

3 common mistakes to avoid

  • Confusing memory with an archive

    An archive stores everything. A memory knows what still applies today and what is outdated.

  • Recording only outcomes

    Without the reasoning a decision can neither be defended nor sensibly changed. The “why” is the most valuable part.

  • Leaving it to one person

    If one person carries the memory, it is gone again at the next change. It needs fixed routines and clear owners.

Step by step

  1. 1

    Collect key decisions

    Start with the decisions of the last twelve months that still apply.

  2. 2

    Add the reasons

    Record for each decision why it was made and what was rejected.

  3. 3

    Link to the sources

    Point to the documents, tickets and meetings where it is carried out.

  4. 4

    Clean up regularly

    Mark what no longer applies instead of quietly leaving it there.

Bring one important decision.

In 30 minutes with Marc or Simon we show where your work drifts from the decision today.

Meet the Company Brain

Read on in the PM Lab

Articles that go deeper.

Related terms

Back to the glossary