Main idea

"If I add this, what do I remove?" is the only question that makes an arbitration effective at the moment it is taken. Without it, adding costs nothing and happens without discussion; development time, product attention, design availability, data analysis capacity and support load are all treated as extensible, which none of them is.

Removal has many reasons, and all of them are perfectly sayable: the world has changed, the business has changed, the product strategy has changed, product knowledge has advanced, the topic is no longer relevant, it is too weak, it is off-roadmap, it never matured. What protects the team isn't preserving old ideas, it's its capacity to act on the right ones.

Why it matters

This turns prioritization into a symmetrical gesture. A queue from which nothing has ever been removed has never been prioritized, even if it has been sorted a hundred times — the order changed, the load didn't.

It also gives the right moment to ask the question: at intake, not during a quarterly review. Removing under the pressure of a stock already built up is a political exercise; removing at the moment of adding is a simple exchange.

Nuances and limits

The exchange assumes comparability between what comes in and what goes out. That is easy between two topics of the same kind, harder between a defect, a regulatory requirement and a strategic bet.

And the rule only applies to what commits capacity. A note, a signal, a traced decision consume nothing and don't have to be exchanged.

Open questions

• Who should carry the removal when the incoming item comes from management and the outgoing one from a customer?