Main idea

As long as the number of places is open, adding a topic requires no justification: it only has to be interesting, and it almost always is. The discussion then bears on the topic's intrinsic quality, where nobody has any reason to object.

A finite number of places changes the question being asked. It stops being "does this topic deserve to exist?" and becomes "this topic rather than which one?". You have to say which problem it serves, which business objective it supports, which risk it reduces, what value it brings — and above all what you are turning down by giving it that place.

The constraint does not produce a better analysis of each topic. It produces a comparison, which is the only operation a prioritization needs and the only one a list with no edge makes impossible.

Why it matters

It explains why prioritization debates spin in place in organizations that have set no limit: people argue about merit, and merit settles nothing. The limit is what forces the move from merit to opportunity cost.

It also indicates where to put the design effort in a prioritization setup: on the number of places, not on the criteria. Criteria without scarcity rank nothing.

Nuances and limits

Comparison assumes a commensurability that does not always exist. Ranking a customer defect, a regulatory requirement and a strategic bet demands a judgment the limit forces you to deliver, but does not equip you to make.

And an arbitrary limit can backfire: if the number of places matches no real capacity, the justification it produces is an exercise in style.

Open questions

• Which form of limit holds up best under pressure: a number of places, a capacity envelope, or a maximum time in the tier?