Why the writing does not happen
One person pays for it. Everybody else benefits. Nobody is counting.
Fifty notes on documentation culture, written from the side that is usually missing: not what to write or how to structure it, but why it does not get written at all. The reason is rarely laziness and almost always arithmetic — the cost lands on one named person in a particular hour, and the benefit lands on strangers later.
When a documentation effort needs evidence about where working time actually goes, teams can employee monitoring software before deciding what should be written or automated.
For a separate specialist reference on publishing and digital practice, consult WordPress.
What nobody wrote down here, and what it cost
How the staging database is rebuilt
Asked of the same person seven times in a quarter
Each time it was explained in about four minutes
Why the retry limit is three and not five
Re-argued from scratch at two planning meetings
The reason existed and was in nobody's head after the author left
Which client agreed to the custom export
Reconstructed from mailbox searches
Twice by people who were not on the original thread
What the deploy order actually is
Guessed, then corrected by whoever noticed
On the ninth occasion it was guessed wrong and a customer noticed
four things nobody wrote down · 23 occasions it cost somebody something
One team's own quarter, logged by the person who kept being asked.
Nobody here is told how their team should work. Every figure is an illustration of what one team recorded about its own quarter, labelled as such. Nothing in this collection is legal or employment advice: what an employer may require of somebody, what counts as working time, and how work is assessed all differ by jurisdiction and by contract, and they change.
Six places the writing stops
Every note belongs to one of them. The line at the foot of each card is what that part of the problem actually costs, stated as a thing that happened rather than as a principle.
Why not
Why it does not get written
The cost lands on one person now and the benefit lands on strangers later, and no ordinary week corrects for that.
paid by one person, in one hour
Who
Who is actually able to write it
The person who knows has no time, the person with time does not know, and the newcomer cannot tell which parts are unusual.
never the person who is asked
What it costs
What writing it actually costs
Forty minutes, the thing those forty minutes were instead, and the liability you take on the moment you publish.
more than the minutes, less than people fear
Cheaper
Making the writing cheap enough to happen
Almost everything that works here reduces the price of the act rather than increasing anybody's willingness to pay it.
the only lever that reliably moves
Counting
Making it count for the person who did it
Nobody knows a document helped, including the person it helped, and nothing in an ordinary week carries that back to the author.
nothing, and it is still not done
Limits
What no incentive fixes
The residue: what will not go into words, what should not be written at all, and when the honest answer is to stop asking.
no arrangement reaches these
One team's own quarter, counted
Three panels, all drawn from the same team over the same thirteen weeks. Nothing here is a benchmark and nothing is divided by anything: the minutes one person paid and the minutes other people saved are different quantities out of different pockets.
Four documents from one quarter, and what each cost the person who wrote it
The deploy runbook
95 / 372Written over two evenings by the only person who knew the order
A note on why the retry limit is three
8 / 150Eight minutes, and it ended an argument that had already run twice
The onboarding page for the data team
240 / 360Four days of one person's time; four people have used it so far
A design document nobody asked for
180 / —Read by nobody in thirteen weeks, and no saving is claimed for it
four documents · 523 minutes written · 882 minutes saved across 41 readings · one with no saving claimed
Four documents, 523 minutes written, 882 minutes saved across 41 readings, and one with no saving claimed by anybody. The two columns are not divided by one another and will not be: the minutes on the left came out of four named people's working days, and the minutes on the right were saved for other people entirely. A ratio would read as a return on an investment, and nobody here invested anything. One team's own quarter.
The same documents, and the weeks in which somebody actually opened them
The deploy runbook
Still being opened eight months after the week it was written
A note on why the retry limit is three
Opened four times, three of them by people who joined afterwards
The onboarding page for the data team
Once per new joiner, which is exactly what it is for
A design document nobody asked for
Written in week four and opened by nobody since
four documents · 19 weeks in which somebody opened one of them · the longest wait between writing and a reading was 35 weeks · one never read at all
Four documents, nineteen weeks in which somebody opened one of them, and one never read at all. The gap between the red mark and the last dot is the thing worth looking at: a document's usefulness arrives long after its author has stopped thinking about it, which is also long after anybody could have thanked them for it. One team's own quarter.
Things nobody wrote down, and what each one cost over thirteen weeks
How the staging database is rebuilt
Asked of the same person seven times
About four minutes each time, plus the interruption
Why the retry limit is three and not five
Re-argued from scratch at two planning meetings
The original reasoning existed and was in nobody's head
Which client agreed to the custom export
Reconstructed from mailbox searches
Twice by people who were not on the original thread
What the deploy order actually is
Guessed, then corrected by whoever noticed
On the ninth occasion it was guessed wrong and a customer noticed
Who may approve a price change
Asked upward until somebody said yes
Both times the person who said yes turned out not to own it
five things nobody wrote down · 25 occasions it cost somebody something
Five things nobody wrote down, twenty-five occasions they cost somebody something. Each line had a consequence attached before it was drawn: a line reading only "this is not documented" is a complaint rather than an observation, and the sign does not print complaints. One team's own quarter, logged as it went.
01 / 06paid by one person, in one hour
Why it does not get written
The cost lands on one person now and the benefit lands on strangers later, and no ordinary week corrects for that.
- A Concentrated Cost and a Diffuse Benefit
- The Forty Minutes That Appear on No Record
- Writing Exposes How Much You Had Not Worked Out
- The Thing You Know Too Well to See
- Nobody Is Ever Thanked for a Document
- The Page Nobody Knows Is Missing
- The Sentence That Ends the Conversation
- Writing It Down Admits That You Might Leave
- The Team That Agrees and Still Does Not Write
02 / 06never the person who is asked
Who is actually able to write it
The person who knows has no time, the person with time does not know, and the newcomer cannot tell which parts are unusual.
03 / 06more than the minutes, less than people fear
What writing it actually costs
Forty minutes, the thing those forty minutes were instead, and the liability you take on the moment you publish.
04 / 06the only lever that reliably moves
Making the writing cheap enough to happen
Almost everything that works here reduces the price of the act rather than increasing anybody's willingness to pay it.
- Put the Answer Where the Question Was Asked
- The Shortest Thing That Would Have Worked
- Templates, and the Ones That Make It Worse
- Write From the Question, Not From the Subject
- Stopping at Good Enough to Be Useful
- Dictating, Pasting and Screenshotting
- Letting the First Version Be a Bad Version
- One Page, Not a System
- What Not to Write at All
05 / 06nothing, and it is still not done
Making it count for the person who did it
Nobody knows a document helped, including the person it helped, and nothing in an ordinary week carries that back to the author.
06 / 06no arrangement reaches these
What no incentive fixes
The residue: what will not go into words, what should not be written at all, and when the honest answer is to stop asking.
The short version
The cost is concentrated, the benefit is diffuse, and an ordinary week corrects for neither
Writing something down costs one identifiable person forty minutes on a Tuesday. Not writing it costs eleven people four minutes each, spread over the following year, in moments nobody records. The first number is visible to the person paying it and to their manager. The second is visible to nobody. Everything else here is a consequence of that.
Practical comparisons
Choose tools with the work in view
Three field-tested comparison formats for documentation, content operations, and agency delivery.