Most organisations treat documentation as an administrative burden.
Something that happens after the real work is done. A task that someone else should probably be doing. A box to tick before the project can close or the meeting can end.
This is not just an attitude problem. It is a category error with compounding consequences.
The move from living memory to external memory — from carrying the count in the skull to pressing it into clay — was never an administrative act. It was an architectural one. The moment the accountant in Uruk made his first mark, he was designing the information infrastructure of an institution. He was determining what would be knowable. He was deciding which obligations would survive his absence, and which would dissolve with him.
Every document created in an organisation today is making the same decision.
What will be knowable? What will persist when the person who knows it leaves? What will be checkable, challengeable, compared against a later record?
Organisations that treat documentation as overhead answer these questions badly — not through malice but through inattention. They produce records that are technically maintained but practically inaccessible. Archives that accumulate faster than they are read. Systems that function as consciences: available in principle, consulted only in crisis, otherwise ignored.
The test is simple enough. If a key person left the organisation tomorrow, what would remain? Not the files — the understanding. The reasoning behind the decisions that are filed. The context that makes the record interpretable rather than merely retrievable.
If the answer is "not much", the documentation is serving the calendar rather than the institution.
This is not a software problem. It is a seriousness problem.
The accountant in Uruk understood — through operational necessity, not management theory — that the mark he pressed was doing something more than recording a count. It was transferring cognitive load to a surface that could hold it beyond any individual.
His successors built trade routes, cities, and civilisations on the discipline of tending that surface.
Most modern organisations build an archive that nobody navigates and call it knowledge management.
The gap between those two outcomes is not technology. It is the decision about whether the record matters.