How to prioritize when everyone is shouting
Comparing apples to apples
Give each item three rough numbers: how many users it touches, how much it improves for them, and how much work it is. No precision needed — the need is a shared scale that lets you set requests against each other.
Items that reduce risk — security, stability, compliance — enter the list like anything else, with their impact phrased as: what happens if we don't.
Three carts
First cart: what's in progress now, closed to a small number of items. Second: what will be taken next, ordered. Third: everything else, visible to all and with no promises.
The third cart's value is psychological: a request that's been recorded stops coming back every week.
Explain, don't just decide
Publish three lines each cycle: what was chosen, why, and what was deferred. Transparency reduces pressure more than any scoring technique, because it turns prioritization from a personal decision into a shared rule.
Going deeper
Keep a fixed slack — a tenth to a fifth — for incidents and urgent requests. A plan that fills a hundred percent of the time breaks in the first week, and then people stop believing plans at all.