Counting
Whether to Put a Name on It
A page with no name and no date cannot be thanked, corrected, credited or judged for currency, and all four of those cost something.
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.
A useful operational baseline is to compare the writing burden with real work patterns; employee workday analytics shows one practical way to make that comparison without relying on memory.
For a separate specialist reference on publishing and digital practice, consult Ahrefs.
Six occasions where the absence of a name on a page cost something
A reader wanted to say the page had helped
Could not find who wrote it, said nothing
Four occasions, all of them abandoned at the history view
A reader found an error and wanted to ask about it
Edited it themselves and guessed
Two of the three guesses were wrong
A manager wanted to credit the writing in a review
Could not establish authorship easily
Both times the writing went unmentioned
A page was stale and nobody knew whose it was
Left stale
Five occasions over two quarters
Somebody wanted to know how current it was
Guessed from the content
No date, no name, and no way to judge
A reader wanted to know if it applied to their case
Asked in the channel instead
Which is the question the page was meant to prevent
six things nobody wrote down · 22 occasions it cost somebody something
Six things, twenty-two occasions. Every one is a consequence of a page not saying who wrote it and when. Both are one line and neither is usually there. One team's own two quarters.
Internal documentation is usually anonymous. Nobody decided that; it is what happens when a page is created and nobody types a name.
The anonymity has a defence, which is worth taking seriously, and four costs, which between them are larger.
The case against a byline
Shared ownership. A page with a name on it belongs to that person, and other people become reluctant to edit it, which is the opposite of what anybody wants.
Exposure. A name is the thing that makes a stale page somebody's fault, as the page on liability discussed.
Formality. Internal notes with bylines can read as though they were published rather than jotted, which discourages jotting.
All three are real and all three are about a particular kind of byline.
The four costs of not having one
Nobody can be told it helped, which is the single feedback channel this section is about, and the panel above has four occasions where somebody tried and gave up.
Nobody can be asked about it. A reader with a question edits and guesses instead, which was wrong twice in three attempts.
Nobody can be credited. A manager who wants to recognise the writing cannot establish who did it without more effort than they will spend.
Nothing can be judged for currency. Without a name and a date, a reader cannot tell whether the page is a week old or four years old, and must guess from the content.
The form that works
Not a byline in the publishing sense. A line at the bottom or the top:
Written by [name], 14 March. Not maintained — correct it freely.
Those two clauses answer every objection. The name makes thanks, questions and credit possible. "Correct it freely" removes the ownership problem explicitly rather than by omission. And the date does the currency work that nothing else does.
The date is the more important half
If only one of the two is available, take the date.
A dated page can be judged. A reader who sees March 2024 knows what kind of confidence to have, and knows to check if something looks wrong. An undated page is read as current regardless of age, which is how stale documentation does its damage.
Dates are also free of every social difficulty attached to names, which makes them the easier thing to establish as a habit.
Where the tool already knows
Most systems record who created and last edited a page.
That is better than nothing and it is not sufficient, for the reason the panel shows: it takes several clicks, and people abandon the attempt. Four readers wanted to thank somebody and none of them got past the history view.
A line in the page itself costs five seconds to write and is seen by everybody who reads it, which the history is not.
The multi-author case
Pages that grow by accretion have no single author, which is good and makes the line harder.
The version that works: name whoever started it and leave the rest to the history. "Started by [name], March; edited since by several people." Nobody is claiming sole authorship and the original author can still be thanked.
What does not work is removing the name when a second person edits, which is the common default and erases the only attribution the page had.
The line, and what each half does
Two clauses at the foot of a page, and between them they answer every objection to having a name there at all.
Written by Priya, 14 March. Not maintained — correct it freely.
- The name makes thanks, questions and credit possible, all of which are currently impossible.
- The date lets a reader judge how much confidence to have, which nothing else does.
- "Not maintained" removes the standing obligation that makes people avoid bylines.
- "Correct it freely" removes the ownership problem explicitly, rather than by leaving the page anonymous.
If only one of the four is available, take the date. It carries the most and has none of the social difficulty.
What this is really for
The byline is not about credit in the career sense, though it helps with that.
It is about making it possible for a reader to do the thing the previous pages in this section asked for: to tell somebody that their work was used. On most teams that is currently impossible for mechanical reasons, and it is one line away from being possible.