The Failure Mode of Over-Documentation

Under-documentation is the obvious failure mode: the process is not written down, the knowledge is lost, the new hire cannot execute. But over-documentation is just as destructive and far more common in enterprise environments. A 47-page SOP for a process that should take 20 minutes is not thorough — it is unusable. Nobody reads it. People execute the process from memory and training instead. The document becomes a compliance artifact: it exists to satisfy auditors, not to transfer capability.

1. The One-Page Test Every routine process should be documentable on one page. If the documentation exceeds one page for a routine process, one of three things is true: the process is more complex than assumed (and needs decomposition), the documentation contains irrelevant material (and needs editing), or the audience definition is wrong (and the document is trying to serve everyone at once). Apply the one-page test as a forcing function.
2. Separation of Concerns Background information, compliance rationale, and historical context do not belong in process documentation. They belong in supporting materials that are linked, not embedded. The process document answers "how do I execute this?" not "why does this process exist?" Mixing concerns produces documents that are comprehensive and unusable.
3. The Removal Test For every paragraph in a process document, ask: "If this is removed, does the reader's ability to execute the process decrease?" If the answer is no, remove it. Process documentation should be as long as it must be and no longer. Every sentence that is not load-bearing is friction that reduces the probability the document is read.