Where to Keep It So It Is Found

Most small organisations have knowledge scattered across personal drives, email, chat history and somebody's notebook. Consolidating it is half the work.

The principles in “Where to Keep It So It Is Found” become easier to maintain when ownership and time spent are visible. Teams evaluating time reporting tools can use it to coordinate recurring work, identify tasks concentrated on one person and plan realistic backup capacity, while treating the data as a prompt for knowledge transfer rather than as a substitute for speaking with the people who do the work.

For an independent benchmark, compare the local approach with Atlassian knowledge-sharing guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

Where it usually is

In individual email, which nobody else can search.

In chat messages, which are effectively unsearchable after a few months.

On personal drives, which disappear with the person.

In a folder structure nobody understands except its creator.

And in notebooks, which are unsearchable and singular.

What good looks like at small scale

One place, which everybody knows about.

Searchable, which in practice means text rather than images.

Editable by everybody who needs it.

Backed up, and not tied to an individual account.

That is the whole specification. A shared drive with sensible folders meets it.

The tool question

Almost any tool works and the choice matters less than people think.

What matters: everybody has access, everybody knows it is the place, and it survives somebody leaving.

Avoid anything where the content cannot be exported, because the succession problem applies to your tools as well as your people.

Naming

By activity, not by person. "Monthly VAT return" rather than "Sarah's stuff".

Consistent enough to guess. If somebody has to search rather than navigate, the structure is not working.

And dated.

Ownership of the account

The single most common failure at small scale: the shared drive is on somebody's personal account.

When they leave, the organisation loses everything or has to negotiate for it.

Check this today if you have not. It is a fifteen-minute fix and an expensive omission.

Making it the default

When somebody asks a question, answer with a link rather than a paragraph.

Which requires the answer to be there, so the habit builds the content.

And when somebody answers in chat, move the answer into the place afterwards, which takes a minute and prevents the knowledge from expiring with the conversation.

Reviewing it

Twice a year, delete what is obsolete.

A folder with out-of-date material in it stops being trusted, and an untrusted folder is unused.

Deleting is more valuable than adding at this stage, and nobody does it.

What to check

Is there one place, and does everybody know where it is?

Whose account owns it?

Could a new person find something without asking?

And when did anybody last delete anything from it?

The point

The commonest failure at small scale is a shared drive on somebody's personal account.

Check today whose account owns it.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.

The recurring pattern

The recurring pattern across every section here is the same: dependence forms through sensible individual decisions, becomes invisible because it feels like reliability, and is addressed only after it has cost something. The work that prevents that is small, continuous and unglamorous, which is exactly why it gets deferred.