Four people agree something in a meeting. Two years later, one has retired, one has moved to Boise, and the remaining two recall it differently and both sincerely.
Nothing was concealed and nobody was careless. The decision simply had no existence outside the memories of the people present, and memory is not a storage medium. It is a reconstruction, and it reconstructs toward whatever happened afterward.
What the written record actually does
Three things, and only the first is the one people think of.
It fixes the content. What was decided, by whom, on what date, subject to what conditions. This is the obvious function and the least interesting.
It preserves the reasoning. Considerably more valuable and almost always omitted. A successor who knows what was decided can implement it. A successor who knows why can tell whether the reason still holds, and can therefore change it responsibly rather than either preserving something obsolete or discarding something load-bearing.
It forces the thinking. Writing a decision down reveals whether it was actually made. Ambiguity that survives a conversation comfortably does not survive a sentence that has to specify who, what, and by when. A leader who cannot draft the paragraph usually discovers that three people left the room holding three versions.
The unwritten arrangement
Every organization of any age contains practices nobody can explain. The invoicing runs on a fourteen-day cycle rather than thirty. One supplier is used for a category where a cheaper one exists. A particular committee has a member from outside the organization.
Each of these was a reasonable decision responding to a real situation. The situation is documented nowhere and the person who knew it has gone.
What follows is one of two errors, and organizations alternate between them. Either the practice is preserved indefinitely because nobody dares change what they do not understand, long after the reason expired. Or a new leader removes it as an inefficiency and discovers, some months later, that it was solving something.
Both are caused by the same missing sentence, written at the time, costing perhaps a minute.
What to write and what not to
A leader who writes everything produces a record nobody reads, which is functionally the same as no record.
Write down anything a successor would need in order to act competently, anything that would look inexplicable to somebody arriving fresh, any decision that will bind the organization beyond the current year, and anything where the reasoning is not obvious from the outcome.
Do not write down routine operational calls, anything already covered by an existing document, or reasoning that is genuinely self-evident. The test is whether an intelligent stranger, looking at the situation in five years, would be able to work out why. If yes, no note is required.
Written for the wrong reader
A specific failure deserves naming because it is common and it destroys the value of the record entirely.
Documents written primarily to protect the author read differently from documents written to inform. They emphasise process compliance over reasoning, they attribute decisions carefully, and they include qualifications whose function is to preserve deniability rather than to convey uncertainty.
Such a record contains almost no usable information. A successor reading it learns that the correct steps were followed and nothing about why anything was done. Organizations where this style predominates have file rooms full of paper and no institutional memory whatsoever.
The distinction is whether a document would change if you knew for certain nobody would ever question the decision. If it would become shorter and more informative, the current version is defensive.
Nothing is private
Anyone serving a public body in Idaho operates under public records obligations, and the practical consequence is not what most people assume.
The assumption is that this counsels writing less. It does not. It counsels writing the same thing you would write anyway, in a form you would be content to see quoted, and treating no channel as informal. Text messages about public business are public business. So is email routed through a personal account.
The leaders who get into difficulty here are rarely the ones who documented too much. They are the ones who maintained a candid informal channel alongside a sanitised formal one, on the assumption that the first was private.
The same discipline is worth adopting in private organizations, where the audience is not a records request but a lawsuit, an acquirer’s due diligence, or a board four years from now.
Where it has to live
A record that cannot be found is not a record, and this is where most attempts at institutional memory actually fail.
Reasoning buried in an email thread is gone the moment that mailbox is closed. The useful version sits somewhere a successor will encounter it without knowing to search: attached to the contract, in the file for the practice it explains, in the minutes rather than in correspondence about the minutes.
The entries that follow deal with the forms this takes in practice: putting the conclusion first, the discipline of a single page, writing that survives the room, and what board packets and reports owe the people who have to govern from them.
Edited by Patrick J. Wolf, PhD