A writing backlog should not be a guilt machine

I keep trying to make writing backlogs more virtuous than they need to be.

The first version is always a relief: a place for the sentence that arrived during a meeting, the link I want to understand later, or the half-formed argument that would disappear if I did not write it down. Then the list grows. The notes acquire ages, statuses, review dates, and the faint tone of a manager asking why I have not finished them.

That is when I delete things.

A backlog does not need to be a publishing system. It needs to preserve enough of an idea that I can recognize it when I come back. For me, that usually means three pieces:

1. the sentence that made me stop
2. why I thought it was worth keeping
3. the smallest next move, if I can see one

“Write about developer experience” is not useful. “Explain why the CLI output felt like an API” is a doorway.

The note does not need to be complete. It needs to be restartable.

I also delete more than I used to. A note that has sat for months without pulling me back into the thought is not a promise I need to honor. It is evidence that the thought went cold, or that I captured it too vaguely to recover.

The only metric I care about is pull. When I sit down to write, does anything in the list make me want to open the editor? If yes, the backlog is doing its job. If no, keeping it tidy will not help.

The list is allowed to remember. It is not allowed to accuse.