Counting
Telling the Author That It Helped
One sentence to the person who wrote a page is the only feedback that ever crosses the gap, it costs fifteen seconds, and almost nobody sends it.
What nobody wrote down here, and what it cost
That the runbook saved somebody a morning
Nobody told the author
Six occasions, none reported back
That a note ended an argument
The author never heard
Both times from people who joined later
two things nobody wrote down · 8 occasions it cost somebody something
Two things, eight occasions, and the author heard about none of them.
When a documentation effort needs evidence about where working time actually goes, teams can digital workforce management tools before deciding what should be written or automated.
Teams can compare this approach with the established material available from Semrush.
Six occasions on one team where a page saved somebody time, and whether the author was told
The deploy runbook saved a morning
Nobody told the author
The reader did not know who had written it and did not look
A note ended an argument in planning
Nobody told the author
The author was not in the meeting
An onboarding page answered a new joiner's question
Nobody told the author
Four joiners, four occasions, no mention
A four-line answer was found in a search
Nobody told the author
Seven occasions; the author still does not know the page is used
A runbook was used during an incident
The author was told once
The one occasion anybody reported anything, and it was in passing
A page was corrected by a reader
The author was told each time
Corrections get reported; usefulness does not
six things nobody wrote down · 18 occasions it cost somebody something
Six things, eighteen occasions, and the author heard about four of them. The last row is the finding: readers reliably tell an author when a page is wrong and almost never when it worked. One team's own quarter.
A page that saves you twenty minutes was written by somebody. Find out who, and send them one line saying so.
That is the entire content of this page. The rest is why it does not happen and why it matters more than it sounds.
Why it does not happen
Four reasons, none of them indifference.
The reader does not know who wrote it. Most pages carry no name and finding one requires looking at a history.
It does not occur to them. Being helped by a document does not feel like being helped by a person.
It feels disproportionate. Sending a message about a page you read seems like a lot of ceremony for a small thing.
And there is no moment. The reader has already moved on to the thing they were doing, which is the point of the page having worked.
What it is worth
Out of proportion to its cost, for three separate reasons.
It is the only information the author ever receives. As the previous page argued, silence is identical for a page that helped nine people and a page nobody opened, so a single message is the difference between knowing and not.
It is specific. "The deploy runbook saved me a morning on Tuesday" is evidence; general encouragement about documentation is not.
It is remembered. People who receive one of these remember it for a year, which is itself a measure of how rarely it arrives.
The corrections asymmetry
The last row of the panel is worth sitting with.
Readers reliably tell an author when a page is wrong. They almost never tell them when it worked. So the entire feedback an author receives, across a career, is corrections.
That is a strange diet. It would not be tolerated in code review and it is the normal condition of writing documentation.
What to say
One sentence. No structure.
Used your deploy runbook this morning — saved me working it out. Thanks.
Not a formal thank-you, not a nomination for anything, not a message in a channel about recognising documentation. One line, directly, when it happens.
If the page was wrong in a small way, say both: it helped, and this bit is out of date. The second is easier to hear attached to the first, and it is how corrections should arrive anyway.
Finding the author
The obstacle most often cited, and it is usually thirty seconds of work: a page history, a commit, a file header.
Where it genuinely cannot be determined, that is an argument for the byline question raised two pages further on, and in the meantime saying so in the channel where the page lives reaches them.
Why not to systematise it
The instinct, having read this, is to build something: a channel for documentation thanks, a monthly award, a field in a tool.
Those convert a signal into a ritual. A message sent because somebody was actually helped carries information; a message sent because it is Thursday and the channel exists carries none, and the author can tell the difference immediately.
The mechanism here is specifically that it is unprompted, which is not a thing that can be arranged.
Why the author never hears
Four separate obstacles, each sufficient on its own, which is why the message so rarely arrives.
- The page carries no name and finding one takes several clicks.
- Being helped by a document does not feel like being helped by a person.
- It seems disproportionate — a message about a page you read.
- There is no moment; the reader has already moved on, which is the page having worked.
Only the first is fixable by anything other than deliberate effort, and it is fixed by one line at the foot of a page. The other three require somebody to decide, once, that this is a thing they do.
What a manager can do with this
Not mandate it. Do it, visibly, several times.
The behaviour spreads by example in a way it does not by instruction, because it is slightly unusual and people need to see that it is normal here before they will do it.
It is also one of the few interventions in this collection that costs a manager nothing, requires no agreement from anybody, and can be started this afternoon.
What the message does for the author
Worth being specific about, because fifteen seconds spent on something vague is easy to skip and fifteen seconds spent on something that matters is not.
It tells them which of their pages worked, which is the only way anybody gets better at choosing what to write. It tells them the afternoon was not wasted, which is the thing they have been quietly unsure about. And it is evidence they can use when describing their own quarter, which nothing else provides.
People who receive one of these remember it for a year. That is not a statement about sentiment; it is a measurement of how rarely any feedback at all arrives.