Why not
The Forty Minutes That Appear on No Record
Writing takes time out of a day that was accounted for, and produces nothing that appears on any record anybody reviews. That combination is most of the problem.
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
What the deploy order is
Guessed, then corrected by whoever noticed
Wrong on the ninth occasion
Why the retry limit is three
Re-argued at two planning meetings
The reasoning was in nobody's head
three things nobody wrote down · 20 occasions it cost somebody something
Three things, twenty occasions, and one customer who noticed.
A useful operational baseline is to compare the writing burden with real work patterns; learn about the workflow shows one practical way to make that comparison without relying on memory.
Teams can compare this approach with the established material available from Brevo.
One engineer's week, with the writing separated out from everything else they did
Shipped the import change
0 / —The thing that appeared on the board and in the standup
Reviewed four colleagues' work
0 / —Visible to four people, and recorded nowhere
Wrote the runbook for the import
40 / 135Forty minutes on Thursday afternoon, mentioned by nobody
Answered the same question in chat four times
0 / —Sixteen minutes, spread across three days, invisible as a block
four documents · 40 minutes written · 135 minutes saved across 9 readings · three with no saving claimed
Four activities, forty minutes of writing, 135 minutes saved across nine readings. Only the first row appeared anywhere that anybody reviews. The third is the only row that produced a lasting artefact and is the only one its author hesitated to mention, on the grounds that it had taken time away from the first. One engineer's own week, recorded at the request of their manager.
A working week is accounted for. Not formally, usually, but in the sense that at the end of it somebody will have an impression of what each person did, assembled from what was shipped, what was said in standup, and what was visible in passing.
Writing does not enter that impression. It takes an afternoon out of the week and leaves no trace in the place where weeks are judged.
Where the time comes from
Nobody has forty spare minutes. The forty minutes come from something, and the something was on a list.
That displacement is the real cost and it is almost never counted honestly. The page took forty minutes; it also delayed a review by a day, or pushed a small fix into the following week, or meant somebody finished at six rather than half past five.
When people say writing takes too long, this is usually what they mean. Not that forty minutes is a lot of time in the abstract, but that it is forty minutes which had to be taken from a day where every hour already had a claim on it.
The record problem
What a person did in a week gets assembled from a small number of visible sources:
| Source | Shows writing? |
|---|---|
| What shipped | No |
| The board or tracker | Only if somebody made a ticket for it |
| Standup | Only if the person says so, and most do not |
| Code review | No |
| What a manager happened to see | Almost never |
Four of those five are blind to it, and the fifth depends on the author volunteering something that sounds, out loud, like an explanation for having shipped less.
Why people do not mention it
Saying "I spent Thursday afternoon writing up the deploy order" in a standup is a sentence most people are reluctant to say, and the reluctance is rational rather than modest.
It sounds like an account of time rather than an account of work. It invites the question of whether it needed doing, which is a question with no good answer at the moment it is asked, because the benefit has not happened yet and will arrive distributed among people who are standing right there and do not yet know they will need it.
The safest thing is to say nothing and absorb the afternoon, which is what most people do.
What this does over a year
Two things, both slow.
People who write find that their weeks look thinner than the weeks of people who do not, through no difference in effort. Over several cycles that produces a quiet, unargued conclusion that writing is something you do when you can afford to look less productive.
And the team's picture of where its time goes becomes wrong in a specific direction. The visible work is overstated and the connective work — writing, reviewing, explaining, answering — is understated, which makes every planning conversation slightly optimistic.
Making the time visible
The intervention is small and nearly costless, and it is done by almost nobody: put the writing on the same surface as everything else.
A ticket, a line on the board, an entry in whatever the team actually looks at. Not for credit, though that helps. For the narrower purpose of making the afternoon appear in the place where afternoons are counted, so that the week reads accurately rather than as a week with a hole in it.
The objection is that this is bureaucratic. It is, slightly. It is also the difference between an afternoon that happened and an afternoon that nobody can account for.
Putting the afternoon somewhere
The intervention is clerical and takes under a minute, and it is worth being specific about what it looks like.
- Make a ticket, or a line on whatever board the team uses.
- Name the thing: "four lines on the deploy order", not "documentation".
- Close it when done, like anything else.
That is all. It does not ask anybody to value the work differently; it puts an afternoon into the place where afternoons are counted, so that the week reads as a week with work in it rather than a week with a hole.
People resist this as bureaucracy, and the resistance is usually strongest from the person whose afternoon it was — which is the clearest sign that it is needed.
What it does not fix
Making the time visible does not make the benefit visible, and the benefit is the half that matters for whether anybody writes again.
A ticket saying "wrote the import runbook" records that forty minutes were spent. It records nothing about the nine people who later opened it, because that has not happened yet and, when it does, will not be connected to the ticket by anybody.
That half is a separate problem and it has its own section.