Product Prioritisation Requires Displacement

A game can move to the top of the roadmap while the UA allocation, product capacity, and older commitments remain almost exactly where they were.

Removing an existing commitment is usually a harder decision than adding another priority.

There may also be good reasons to hold back on scale. Early cohorts can look encouraging while retention and payback are still too immature to trust. The team can keep UA within a limited range and use that time to work on the main product constraint.

That still consumes budget, product time, and management attention. If nothing else moves, the new priority is added to work the team was already carrying.

Before the review ends, somebody needs to decide what will receive less attention.

Otherwise, the team leaves with one more strategic product and exactly the same capacity.