Urgency is not a priority signal
In most growth-stage B2B companies, everything genuinely is urgent to someone. The largest customer's request is urgent commercially. The reliability work is urgent technically. The board's strategic bet is urgent politically. Treating urgency as the ranking signal means the roadmap belongs to whoever escalated most recently.
Urgency is a sequencing input. Value and cost decide whether something belongs on the list at all.
The four scoring axes
- Impact. Which metric it moves and by roughly how much, for which segment. A stated range beats a confident single number.
- Effort. Engineering and design cost including the work nobody counts: migration, support, documentation, and enablement.
- Dependency. What must be true first. High-dependency items look cheap and land late; this axis is where most roadmaps lie to themselves.
- Reversibility. How cheaply it can be undone. Highly reversible bets deserve less debate and faster decisions; irreversible ones deserve more scrutiny than their size suggests.
Score on a simple scale, keep the scoring session under an hour, and record the score beside the item so the reasoning survives the meeting.
The forcing rule
A scoring model without a forcing rule just documents an overloaded roadmap. The rule is one line: nothing enters without something leaving or a date moving, and the trade-off is named out loud in the operating review.
This is the mechanism that changes behaviour. Once requesters know that their addition means naming what it displaces, the volume of low-conviction requests drops sharply without a single difficult conversation.
When the score and the politics disagree
Sometimes you will ship the lower-scoring item — to save a renewal, to honour a commitment, to keep a partnership alive. That's legitimate. What is not legitimate is pretending the score said so.
Override in public, in one sentence: this scored third, we're doing it first because of the renewal, and here's what moves as a result. The system keeps its credibility precisely because the exceptions are visible and rare. Silent overrides are what teach a team that prioritization is theatre.