Ask yourself a specific question: what is the oldest policy or procedure that currently governs your operation?
Not oldest in the sense of "vintage" or "foundational." Oldest in the sense of: has not been reviewed against current conditions since it was written.
Most operators, when they try to answer honestly, discover they cannot. The documentation exists. The review date does not. Or the review date does exist — Q3 annually — but what actually happened in Q3 was that someone glanced at it, found nothing obviously broken, and signed it off. That is not a review. That is a visual confirmation that the document is still there.
The problem with knowledge that waits is that it does not announce its own obsolescence. A policy written for a team of fifteen, now applied to a team of sixty, does not flag the discrepancy. A supplier procedure written when you had twelve vendors, now governing a network of three hundred, does not note that certain clauses no longer apply. A risk framework designed for your original product portfolio does not indicate that your portfolio has since tripled in complexity.
The document simply waits. Patient. Speaking in present tense. Treated as authoritative because it has not been challenged, which is not the same as being verified.
The practical discipline here is not especially complicated. It requires treating documentation as a claim with a date, made under specific conditions — and building the obligation to check those conditions into the governance of the archive, not just the initial act of writing.
What conditions gave this document its meaning? Do those conditions still obtain? If not, has the document been updated to reflect what has changed — or is it being applied to a situation it was never designed for?
Different knowledge ages at different rates. Technical specifications become obsolete when the technology changes. Market intelligence has a half-life tied to the volatility of the sector. Strategic principles can stay directionally valid for a decade. Foundational values, if genuinely foundational, can endure far longer.
The organisation that applies the same review cycle to all of these — or that applies no review cycle at all and calls it governance — is not managing knowledge. It is warehousing it.
Speed of retrieval is not the same as quality of intelligence. The ability to find the document in three seconds does not tell you whether finding it was a good idea.
The discipline is not building a bigger archive. It is knowing which parts of the archive are still speaking truthfully about the world they claim to describe — and having the institutional structure to find out when they are not.