Every organisation develops a memory.

It remembers why a particular decision was made, which client prefers a telephone conversation to an email and how a difficult project was eventually brought under control. It knows which funding application succeeded, which partnership required additional care and which apparently simple task contains complications that are invisible to someone encountering it for the first time.

This knowledge has real value.

It helps people work more intelligently. It prevents old mistakes from being repeated. It preserves context that cannot always be reconstructed from a finished document or a row in a spreadsheet.

But organisational memory is often more fragile than it appears.

Important knowledge may live inside one person’s head, inbox or private notes. A founder may understand every client relationship but have no complete record of that understanding. A project manager may know why a process has developed in a particular way, while everyone else sees only the final steps.

The arrangement can function for years.

Then that person becomes unavailable.

They may leave the organisation, take a holiday, experience illness or simply become occupied with another priority. Suddenly, work that appeared to belong to the organisation is revealed to have depended on one individual’s memory.

A resilient organisation does not attempt to document everything.

It decides what must not be allowed to disappear.

Information Is Not the Same as Knowledge

Most organisations possess large amounts of information.

They have emails, reports, proposals, meeting notes, spreadsheets, cloud folders, messages and recordings. The difficulty is not always that information has been lost. It may be that nobody knows where to look, which version is correct or why the information matters.

A folder full of documents is not automatically a knowledge system.

Information records what exists.

Knowledge helps someone understand what to do with it.

A signed contract is information. Knowledge includes understanding which obligations require attention, who is responsible for them and what previous conversations shaped the agreement.

A list of community partners is information. Knowledge includes understanding the history of those relationships, how trust was established and which forms of communication are appropriate.

A project plan is information. Knowledge includes knowing which assumptions remain uncertain, why one route was selected and which warning signs should trigger reconsideration.

Organisational memory therefore requires more than storage.

It requires context.

The Founder Often Becomes the System

In a young business or creative practice, the founder naturally holds most of the knowledge.

They created the idea, developed the offer, built the relationships and made the early decisions. When a question arises, asking the founder is often quicker than searching for an answer elsewhere.

This can feel efficient.

It can also prevent the organisation from developing memory outside the founder.

If every proposal must be explained by the same person, every client history recalled by them and every unusual decision referred back to them, their attention becomes a permanent operational requirement.

The organisation may grow, but its capacity remains restricted by one person’s availability.

This creates pressure for the founder and uncertainty for everyone else. Team members may hesitate to act because they cannot see the reasoning behind previous decisions. They may complete the task differently each time or create unofficial processes to fill the gaps.

The founder becomes not only a leader but also the organisation’s search engine, archive and final safeguard.

That is not sustainable.

Founder knowledge should remain valuable. It should not remain inaccessible.

What Should an Organisation Remember?

Not everything deserves permanent documentation.

Attempting to record every conversation and minor decision can produce so much material that important knowledge becomes harder to find.

The question is not, “How can we save everything?”

It is, “What would be difficult, expensive or damaging to reconstruct?”

An organisation should consider protecting knowledge relating to:

Important decisions and the reasoning behind them

Client and partner commitments

Project objectives, responsibilities and deadlines

Legal, financial and contractual obligations

Funding requirements and reporting conditions

Cultural and community relationships

Accessibility requirements

Safeguarding responsibilities

Intellectual property and permissions

Research sources and evidence

Significant risks and assumptions

Previous mistakes and lessons

Approved language, messages and public positions

The location and status of essential files

Processes that depend on specialist knowledge

The correct level of documentation will vary.

A routine internal preference may require only a short note. A decision involving public trust, legal responsibility or community knowledge may need a fuller record.

The amount of documentation should reflect the consequence of forgetting.

Record Why, Not Only What

Organisations often preserve the final decision while losing the reasoning that produced it.

A document may state that a partnership was declined, a service was redesigned or a particular audience was prioritised. Months later, someone may see the outcome but have no understanding of the evidence, concerns or alternatives considered at the time.

The decision may then be reversed without anyone realising that an old risk has returned.

A useful decision record does not need to be long. It might include:

What was decided

Why the decision was necessary

What evidence was considered

Which alternatives were discussed

Who participated

Who approved the outcome

What remained uncertain

When the decision should be reviewed

This creates continuity without pretending that every past decision must remain permanent.

Conditions change. Evidence develops. Relationships evolve.

Organisational memory should support future judgement, not imprison people inside old choices.

Some Knowledge Belongs to Relationships

Knowledge is not always contained in facts.

Sometimes it exists within a relationship.

A community organisation may know that a certain phrase has a history that makes it inappropriate in a particular context. A cultural partner may understand why an earlier project created distrust. A long-standing team member may recognise that an apparently minor change affects people whose perspectives have previously been overlooked.

This knowledge may never appear in a conventional project report.

That does not make it less important.

Organisations working with communities, culture and identity must be especially careful not to reduce relational knowledge to data that can simply be captured and reused.

Some knowledge is shared in confidence. Some belongs collectively to a community. Some requires permission before it can be recorded, circulated or applied elsewhere.

Responsible organisational memory asks:

Who created this knowledge?

Who has the right to access it?

Was permission given to record it?

Can it be reused in another context?

Does documenting it create a privacy or safeguarding risk?

Could removing it from its original context distort its meaning?

How should contributors be acknowledged?

What should deliberately not be retained?

Preserving knowledge should not become a form of extraction.

The organisation must remember its responsibilities as carefully as it remembers the information itself.

Accessibility Is Part of Organisational Memory

Knowledge has not been successfully preserved if only a small number of people can use it.

A system may technically contain everything the organisation needs, yet remain inaccessible because files are poorly named, folders are inconsistent or documents require specialist language to interpret.

Accessibility includes more than permissions.

It includes whether someone can locate the information, understand its significance and determine whether it is current.

A useful knowledge system should answer practical questions:

Where is the authoritative version?

When was it last updated?

Who owns it?

Who can access it?

What does it relate to?

Which actions does it require?

Is any part confidential or restricted?

When should it be reviewed or deleted?

Good organisation is not cosmetic.

It reduces the time between needing knowledge and being able to act upon it.

More Technology Does Not Automatically Create Better Memory

When knowledge is scattered, the immediate response is often to purchase another platform.

A new database, project-management system or AI tool promises to centralise information and make everything searchable.

These tools can help.

But technology cannot decide which knowledge is important, whether it is accurate or who should be allowed to use it. It cannot repair poor habits if people continue storing material in private locations or failing to update the official record.

The organisation may simply create another place in which information becomes lost.

Before introducing a new system, it should clarify:

What knowledge needs to be preserved

Who will contribute to it

Who will maintain it

Which source is authoritative

How information will be checked

What should remain confidential

When outdated material will be reviewed

How people will learn to use the system

What happens if the technology becomes unavailable

The tool should serve the knowledge practice.

It should not be mistaken for the practice itself.

AI Can Retrieve Knowledge—and Repeat Its Errors

AI can help organisations search documents, summarise records, identify connections and make internal knowledge easier to access.

For a small team, this can be valuable. It may reduce the need to search through years of files or depend on one person to explain every previous decision.

But AI introduces its own risks.

It may present outdated information with confidence. It may remove qualifications from a summary or combine material from contexts that should remain separate. It may expose sensitive information if access is poorly controlled.

An AI knowledge system should therefore have clear boundaries.

People need to know:

Which information the system can access

Whether its answers are linked to original sources

How accuracy will be checked

Which subjects require human confirmation

Who is allowed to retrieve confidential material

How corrections are recorded

When information should be removed

Who remains accountable for decisions based on its output

The aim is not to create an artificial memory that replaces human understanding.

It is to make verified organisational knowledge easier to find while keeping responsibility with people.

Documentation Is Not the Same as Transfer

A person can leave behind extensive notes and still take essential capability with them.

Some knowledge is difficult to understand without demonstration, conversation and practice. A written guide may explain the steps of a task but not the judgement required when circumstances vary.

This is sometimes called tacit knowledge: understanding developed through experience that people may use without being able to describe completely.

Transferring it requires more than uploading documents.

Useful approaches include:

Working alongside another person

Recording demonstrations

Discussing difficult cases

Explaining why exceptions were made

Rotating responsibilities

Allowing someone else to lead while support remains available

Reviewing completed work together

Creating opportunities to ask questions

Testing whether the task can be completed without the original owner

The real test is not whether the process has been written down.

It is whether another person can use the knowledge responsibly.

Build Memory Into the Work

Documentation is often postponed until the end of a project.

By then, people are tired, attention has moved elsewhere and much of the reasoning has already been forgotten.

A stronger approach captures essential knowledge as the work develops.

A project might include:

A short record when a major decision is made

Clear ownership for each important document

A regular review of risks and assumptions

Notes after significant client or community conversations

A final check that permissions and commitments are recorded

An end-of-project review identifying what should be repeated or changed

A defined place for the approved final materials

This does not need to become burdensome.

A few well-designed questions asked at the right moments may preserve more value than a lengthy report produced months later.

Create a Minimum Organisational Memory

A small organisation does not need an enormous knowledge-management programme.

It needs a minimum dependable memory.

Begin with one important area of work and establish:

A clear location: Where will the knowledge live?

An owner: Who is responsible for keeping it current?

A naming system: How will people recognise the correct material?

A decision record: How will important choices and their reasoning be captured?

Access rules: Who can see, change or share the information?

A review date: When will accuracy be checked?

A transfer method: How will another person learn to use the knowledge?

A deletion rule: What should not be kept indefinitely?

Then test the system.

Ask someone who did not create the material to find an important document, understand what happened and identify the next action.

Their difficulty is useful evidence.

It shows where the organisation’s memory is incomplete.

A Resilient Organisation Can Remember Without One Person

The strength of an organisation should not be measured only by what it can do when all its key people are present.

It should also be measured by what remains possible when someone rests, moves on or becomes unavailable.

Can the organisation honour its commitments?

Can another person locate the right information?

Can they understand why previous decisions were made?

Can relationships continue without forcing clients or communities to explain everything again?

Can the founder step away without becoming the emergency contact for every uncertainty?

Organisational memory is not about removing people from the work.

It is about respecting what people have learned enough to prevent that learning from being lost.

The most valuable knowledge should not be trapped inside the person carrying the greatest responsibility.

It should become part of the organisation’s shared capacity—protected with context, used with permission and available when the work needs it.