Killing Outdated Content

Organizations accumulate documentation the way houses accumulate things: incrementally, without curation, until the useful items are buried under the irrelevant ones. A playbook library that contains fifty documents, thirty of which are outdated, is not a documentation asset — it is a navigation problem. The person who searches for the current credit request process and finds three versions of it, dated 2021, 2023, and 2025, has not been helped by the organization's documentation investment. They have been given a triage problem dressed as a resource.

1. Deprecate rather than delete When a playbook is superseded, mark it clearly as deprecated — change the status in the header to DEPRECATED, add a banner at the top that links to the current version, and move it to an archive location. Do not delete it. Deleted documents cannot be consulted for historical reference, cannot be used in audits, and cannot help the organization understand how a process evolved. Deprecated documents are findable but clearly labeled as superseded.
2. Conduct an annual documentation audit Once a year, audit the full playbook library. For each document: Is it still in use? Is it still accurate? Does it have an active owner? If a document is not in use, not accurate, and has no active owner, it should be deprecated. The audit prevents the accumulation of documentation debt — the growing gap between the organization's documented processes and its actual processes.
3. Create a deprecation protocol Deprecation is not a decision one person makes unilaterally about a document that others may rely on. The deprecation protocol should require: notifying known users of the document, confirming that a current version exists or that the process is truly obsolete, updating any cross-references in other documents that link to the deprecated one, and archiving the deprecated version with a clear label. Deprecation is a process, not a button.