Writing the Minimum That Actually Helps

The aim is not a manual. It is enough for a competent person to pick something up without the person who normally does it.

The principles in “Writing the Minimum That Actually Helps” become easier to maintain when ownership and time spent are visible. Teams evaluating automatic time tracking 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 four things

What this is for. One sentence. The purpose, not the steps, because purpose survives changes in procedure.

Where things are. The system, the folder, the login, the physical location. This is the single most useful category and the shortest to write.

What is unusual. Exceptions, quirks, the client who is different, the step people get wrong.

Who to ask. Internally and externally: the supplier contact, the person at the client, the accountant.

Four short paragraphs covers most activities in a small organisation.

What to leave out

Detailed step-by-step instructions for anything a competent person can work out from the interface.

Screenshots, which age badly and take longest to produce.

Anything the system already documents.

Background and rationale beyond one sentence.

Length is the enemy here: a long document does not get written, and once written does not get read or updated.

The format

Plain text or a simple document, in a place with a sensible name.

Headings matching the four things above, so somebody can scan.

Dated, so a reader can judge how much to trust it.

And named after the activity rather than the person, which matters more than it sounds and has its own note.

Writing it fast

Twenty minutes per activity, dictated if that is easier.

Do the ones from your dependence map, worst first.

Three or four a week gets a small organisation through its critical list in a couple of months without anything resembling a project.

The test of a good note

Give it to somebody who does not do the activity and ask them to attempt it.

Where they get stuck is what is missing.

Where they did not need it, you wrote too much.

Fifteen minutes, and it improves the note more than any amount of revision by the author.

The living version

The note is a starting point that gets added to when somebody hits something unexpected.

Which means it needs to be somewhere editable by whoever hits the problem, not locked to its author.

A note that only one person can update recreates the dependence it was meant to remove.

For the things that cannot be written

Some activities are judgement rather than procedure, and a note will not transfer them.

Write what can be written — where things are, who to ask — and accept that the rest needs pairing.

Do not let the unwritable part prevent the writable part, which is a common way nothing gets written at all.

What to check

Do your notes say what things are for, or only how to do them?

Is the "where things are" section there?

Has anybody tried to use one without help?

And can somebody other than the author edit it?

The point

Four short paragraphs covers most activities: what this is for, where things are, what is unusual, and who to ask.

Length is the enemy here.

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.