Main idea

The argument that puts everything into the backlog is always the same: "at least everything is visible". A queue of five hundred lines is nonetheless opaque. Nobody can tell any more what is strategic from what is old, what comes from an important customer from what is a hunch dropped in one evening, what has already been rediscussed three times from what has never been looked at. Everything is visible, so nothing is legible any more.

What an outside observer — an executive, a salesperson, a customer — is really after is not the list: it is the answers to a few questions. Why this topic is on the roadmap and that one is not. Why this defect is being fixed now. Why this request stays a signal and does not become work. None of those answers can be read off an inventory.

An immature idea that stays out of the backlog is therefore not a hidden idea. It is an idea that has no decision to expose yet.

Why it matters

It strips exhaustiveness of the moral credit it grants itself. Dropping a topic into the collective tool feels like an act of loyalty to the team; it is often the opposite — you transfer to everyone the burden of sorting what you did not want to settle yourself.

It also changes what has to be kept alongside the backlog: not less information, but distinct spaces — a product memory, a signal base, thinking notes, decisions, refusals. Transparency plays out in those spaces, not in the length of the queue.

Nuances and limits

Exhaustiveness keeps its value in a constrained setting — audit, contractual commitment, regulatory obligation — where you have to prove that an item was recorded. The need is then for evidence, not for transparency.

And making decisions legible costs more than dropping everything in: they have to be written.

Open questions

• Where do you lodge the answer to "why not this topic" so that a salesperson finds it alone, without reopening the debate?