Keeping It Current Without a Programme

Written knowledge decays. In a small organisation nobody has time to run a review schedule, so the maintenance has to be attached to work that happens anyway.

The principles in “Keeping It Current Without a Programme” become easier to maintain when ownership and time spent are visible. Teams evaluating the full article 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 Ready.gov business preparedness guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The three habits

Update when you use it. If you follow a note and something has changed, fix the note before you move on. Two minutes, at the moment you know exactly what is wrong.

Update when you explain. If somebody asks and the note did not cover it, add the answer.

Update at handover. Whenever a task moves between people, the note gets read by a fresh pair of eyes, which is the best review it will ever get.

All three are attached to existing work, which is why they survive.

The date line

Every note carries the date it was last touched.

A reader seeing "last updated eleven months ago" treats it differently from one updated last week, which is the information they need.

And a stale date is the prompt that triggers a look, without anybody running a schedule.

The annual delete

Once a year, go through and remove what is obsolete.

Deleting is the maintenance that nobody does and that matters most: a folder containing wrong material stops being trusted, and an untrusted folder is unused.

An hour, and it is more valuable than a month of writing.

What to do about drift you cannot fix

Sometimes a note is clearly out of date and nobody knows what the current answer is.

Mark it rather than leaving it: "this may be out of date, check with X".

A flagged note is honest and still useful. An unflagged wrong note is a trap.

Who maintains what

Whoever does the activity, not a designated documentation owner.

Ownership by a single person recreates the dependence the documentation was meant to remove, and that person becomes a bottleneck for corrections.

In a small organisation the answer is that everybody can edit anything.

The signal that it is working

Somebody who was not the author edits a note.

That is the moment it stops being one person's document and becomes the organisation's.

If that has never happened, the notes are still personal property regardless of where they are stored.

What not to introduce

Review cycles with owners and dates, which are a corporate mechanism that will not survive a busy quarter.

Approval before editing, which stops corrections.

And version control beyond what your tool does automatically, which adds friction for a benefit small organisations do not need.

What to check

Do your notes show when they were last updated?

Has anybody other than the author ever edited one?

When did you last delete something?

And is there anything in the folder you know to be wrong?

The point

Attach maintenance to work that happens anyway: update when you use it, update when you explain it, update at handover.

Review schedules do not survive a busy quarter.

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.