Why not
The Sentence That Ends the Conversation
The sentence is said sincerely, agreed by everybody, and produces nothing, because agreement is cheaper than writing and feels like the same thing.
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.
Documentation is easier to defend when the team can connect it to measurable time saved; this guide provides an operational reference for that conversation.
A useful independent point of reference for this part of the process is Buffer.
Six occasions on one team where somebody said the thing should be written down, and what happened next
After an incident where the deploy order was wrong
Agreed in the review, nobody named
Nothing written; the same thing happened eleven weeks later
In a planning meeting, about the pricing logic
Added to a backlog as a ticket
Still in the backlog at the end of the quarter
In chat, after the fourth identical question
Agreed by three people
One of them wrote four lines that afternoon, which ended it
In a retrospective, as an action for the team
Owned by everybody
Raised again at the next two retrospectives
After somebody announced they were leaving
Agreed urgently
A handover document was written and was mostly a list of links
In a one-to-one, about the on-call rota
Agreed and assigned to a named person
Written the following week, because somebody was named
six things nobody wrote down · 10 occasions it cost somebody something
Six occasions, ten repetitions. The two that produced something had one thing in common and it was not urgency: somebody was named, or somebody simply did it there and then. One team's own quarter, reconstructed from meeting notes.
"We should document this" is one of the most agreeable sentences available in a working conversation. Everybody nods. The topic closes.
It is also, measured by what follows, one of the least productive, and the reason is not that anybody was insincere.
What the sentence actually does
It resolves the discomfort in the room.
Something has just gone wrong, or somebody has just asked a question for the fourth time, and there is a brief moment where the team is confronted with a gap. The sentence closes that moment. It converts an uncomfortable present fact into a comfortable future intention, and everybody can move on.
That is a genuine function and it is why the sentence is so popular. What it does not do is cause anything to be written, because nothing about saying it changes the cost of the writing or who will bear it.
Agreement is the cheap part
Everybody agreeing that documentation matters costs nothing. It takes four seconds, it makes everybody look sensible, and it is true.
The expensive part — one person, forty minutes, on a day with other claims on it — is untouched by the agreement, and nothing in the conversation allocated it.
This is why teams can agree about this sincerely and repeatedly for years without the behaviour changing. The agreement is not a step towards the writing. It is a substitute for it, and it is a good enough substitute to be self-sustaining.
The two things that actually produce a page
The panel above has six occasions and two outcomes, and the two share a structure.
Somebody did it immediately. Four lines, that afternoon, while the question was still live. No ticket, no plan, no agreement — just somebody typing for six minutes.
Or somebody was named. Not "the team", not "we", not a ticket owned by the backlog. A person, with a name, who knew it was theirs.
Everything else in the table produced a repetition.
Why the ticket does not work
Putting it in the backlog feels like the responsible move and is usually where documentation goes to die.
A documentation ticket competes against work with visible outcomes and loses every time it is prioritised, because the comparison is between a change somebody is waiting for and a page nobody has asked for. That comparison has one answer and it will have the same answer next fortnight.
The ticket also launders the agreement into a record, which makes the team feel the matter is handled. A thing in a backlog is harder to raise again than a thing that was never written down, because raising it now sounds like nagging about an existing ticket.
The replacement sentence
Two forms, and either beats the original.
"I'll write that down now" — said by whoever has just explained it, and done in the next ten minutes, at four lines.
"Can you write that down? Four lines is fine." — said to a named person, with the size stated, which is the part that makes it answerable.
Saying the size matters more than it looks. "Document this" implies an unbounded task; "four lines" is a request somebody can agree to and complete, and completing it is what makes the next request plausible.
Naming somebody is uncomfortable
The reason teams say "we" is that naming a person in a meeting feels like assigning work in public, and people are reluctant to do it, particularly to peers.
That discomfort is the entire mechanism. "We" is chosen precisely because it avoids the moment where one person has to accept a cost in front of everybody, and avoiding that moment is why nothing happens.
It is worth saying plainly in the room: a documentation action owned by everybody is owned by nobody, and we have now agreed this four times.
Three sentences that work better
The replacement is not a process. It is a different sentence, said in the same moment, by whoever is in the room.
- "I'll write that down now." — said by the person who just explained it, and done in the next ten minutes.
- "Can you write four lines on that by Friday?" — a name, a size and a date.
- "That's the fourth time this has come up; I'm putting it in the runbook." — said while doing it.
All three are slightly less comfortable than the original, because each one attaches the cost to somebody. That discomfort is not a side-effect of the method; it is the method, and avoiding it is why the original sentence has been said four times already.
What to do with the agreement that already exists
Most teams reading this have a standing agreement that they should write more, several years old, with nothing attached.
The useful move is not another agreement. It is to take the three things people actually ask about, name one person for each, state a length, and give a date. Three names, three lengths, three dates, in one message.
That is less satisfying than a plan and considerably more likely to produce pages.