Main idea

Flatly refusing everything that is not a priority would be brutal and wrong: many discarded topics are good, and will become important if the market shifts, if a big customer signs, if a regulatory constraint appears, if a technical dependency disappears, if a technological leap makes possible what was not. Keeping them on display without commitment is therefore a legitimate move.

It holds on one condition only: that the card write down what would reopen the topic. Why it stays visible, why it is not a priority, and above all what trigger would bring it back up — a concentration of requests around a few integrations, the signing of an account in the segment, proof of usage on a narrow scope.

Without that trigger, the column of possibilities becomes an open-ended waiting list: everyone reads a soft promise into it, nobody knows when to rediscuss it, and the topic comes back on the table at every meeting where someone thinks of it again.

Why it matters

It separates two objects that look very much alike on screen: an investigated possibility and a refusal nobody dared write down. The difference is not the length of the wait, it is the existence of a named event that ends the wait.

It also gives a reason to limit that column without removing it: every topic kept visible costs a trigger to write and to watch.

Nuances and limits

A trigger can be written and never observed, because nobody is in charge of watching for it. Writing is not enough; someone has to cross incoming signals against those conditions.

And not all triggers are observable at the same cost: "concentration of requests" can be measured, "technological leap" can only be recognized after the fact.

Open questions

• Who should own the watching of triggers, between the Product Manager who wrote them and the support team that sees the signals go by?