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.
What nobody wrote down here, and what it cost
How the staging database is rebuilt
Asked of the same person seven times
Four minutes each, plus the interruption
Which client agreed to the export
Reconstructed from mailbox searches
Twice by people not on the thread
two things nobody wrote down · 10 occasions it cost somebody something
Two things, ten occasions, and nobody billed any of it to anybody.
What the Forty Minutes Came Out Of
Writing does not take time from a reserve; it takes it from something specific that was already planned, and naming that thing is most of the cost conversation.
The Liability You Take On by Publishing
Publishing a page creates an open-ended obligation to keep it true, and people who have been blamed for a stale document price that obligation correctly.
Being Wrong in Writing, Where It Stays
A mistake in conversation disappears. A mistake in writing persists under your name, and that difference stops more pages than any shortage of time.
What It Costs to Be the Answer
Answering the same question repeatedly costs far more than the minutes, because the interruption destroys more than it consumes.
What Not Writing Costs, and Who Is Billed
The cost of an absent document is real, large and distributed across people who never connect what they paid to what was missing.
Count the Asks Before Deciding What to Write
A documentation backlog built from what gets asked is short, surprising and correct. One built from intuition is long, tidy and mostly unread.
Writing While Doing It, Not Afterwards
Writing something down while doing it costs a fraction of writing it afterwards, because afterwards you have to reconstruct what you already had.
The Second Draft Nobody Budgets For
A page is never finished when it is published. The revisions are cheap, they are where the quality is, and nobody plans for them.