PM Roadmap Prioritization
(2026 Edition)
5 input signals and 5 rules for prioritising with rigour.
Build Prioritisation PM Skills — Free →5 Input Signals
Strategy — does this advance the bet we're making?
Customer pain — how painful, how widespread, how willing to pay/stay
Revenue impact — direct or leading indicator
Effort and risk — not just engineering weeks; opportunity cost
Strategic optionality — does this open or close future moves?
5 Rules
Every yes is three nos — make the nos explicit
Kill publicly — stopping work is honest, not weakness
Segment by horizon — Horizon 1 (quarter), H2 (year), H3 (speculative)
Rebalance monthly — reality changes faster than quarterly reviews
Don't let loud stakeholders set priorities — they're one voice, not the mandate
FAQ
How does a PM say no to exec requests?
Not with 'no' — with 'yes, and here's what won't happen as a result.' Show the tradeoff: if we build X, we don't build Y. Let the exec choose. Most requests die when their true cost is visible. The few that survive deserve to be on the roadmap.