The Process Doc Nobody Opened
A 43-page ops manual drew 31 views in a year, 23 of them the author's. The doc nobody opens was scoped for the writer, not the person doing the task.
A customer success manual went live at 43 pages, 11 contributors, and six months of writing meetings. A year later, Notion's analytics showed 31 page views. 23 of those were the author checking his own work. The other 8 were new hires during onboarding week, none of whom came back to the doc after day five.
This is the ordinary way internal documentation dies. The doc is comprehensive, organized for the writer, hosted in a place that makes sense only if you already know it exists, and shaped for the rare full read instead of the common task lookup. The CSM trying to refund a duplicate charge does not open a 43-page manual. She messages the senior CSM. He answers in Slack. The answer never makes it back into the manual. The manual decays while the real knowledge keeps living in threads and in heads. It is the same failure mode as a runbook that lives in one person's head, only with more pages to make it look solved.
What works is unsentimental and less impressive: short docs, task-shaped, sitting in the path the worker is already on. How to refund a duplicate charge as a four-paragraph note, pinned in the #customer-success channel where the question gets asked. It gets used because it is one click from the question. It stays current because the channel where it lives is the channel where the next question surfaces.
Most teams write the wrong shape because the wrong shape reads as maturity. The 43-page manual looks like an operation that has its act together. Five pinned notes in a Slack channel look like a team that never bothered to write anything down. The first photographs better in a board deck. The second is the one people open. It is the same reason a Slack channel quietly becomes the real wiki while the sanctioned docs go untouched.
The check takes ten minutes. Pull the analytics on the docs hub and sort by view count. If more than half the docs have fewer than ten views in the last quarter, the documentation is a graveyard and the team is operating on something else. Find the something else — the threads, the pinned messages, the one Slack DM everyone forwards. Write the docs in that format, in that place. The artifact that gets opened is worth more than the artifact that looks complete.