Main idea

A backlog's entry rule bears neither on the maturity of the idea, nor on its value, nor on its origin: it bears on the number of people the topic mobilizes. As long as a Product Manager is digging alone, there is nothing to put in a shared tool. As soon as it takes a feasibility study with a developer, an exploration of product data with a data analyst, an interface design with the design team, or a meeting between support, product and engineering, the backlog becomes useful.

Before that threshold, the topic exists elsewhere, and that elsewhere does not need to be standardized — Obsidian, Apple Notes, Trello, a notebook. That space serves to absorb the storm of ideas: you collect there, connect there, let things rest there, delete there. Many ideas never deserve to be seen by anyone else, and that is the normal working of such a space, not its failure.

Why it matters

It gives an entry criterion you can settle alone, with no committee and no maturity checklist: who do I need? A three-line idea dropped in "so as not to forget" fails that test, whatever its quality — it mobilizes nobody yet.

It also legitimizes the heterogeneity of personal tools. Wanting to standardize the upstream amounts to imposing the cost of a collective tool on work that is not yet collective.

Nuances and limits

The threshold is sometimes crossed the other way: a topic enters the backlog, turns out to be poorly understood, and has to go back to the personal space. The rule says nothing about that return, which is frowned upon because it looks like a retreat.

And some organizations require a trace in the tool from the first mention, for traceability reasons. The entry rule then becomes a rule of status rather than a rule of presence.

Open questions

• Who arbitrates the threshold when the Product Manager still believes they are digging alone while the topic already commits engineering?