Feature Prioritisation Matrix
By Spencer Garcia · Published · Updated
A ranking you can defend when someone's pet feature comes fourteenth.
Tags: Product, Planning, Data
Prompt template
## Prioritising the backlog - The list: [textarea: Every candidate, and who asked for it] - Evidence behind each: [textarea: Requests, support volume, revenue at stake, data] - Rough effort: [textarea: Sizing if you have it, even t-shirt sizes] - What the business is trying to achieve this quarter: [textarea: Strategic goals] - Capacity: [textarea: Team size and time] - Already committed: [textarea: Promises you cannot break] Score each on reach, impact, confidence and effort, and show the working so people argue with the inputs rather than the ranking. Be explicit where confidence is low. The loudest requests usually score worst here and that is the useful part. Separate out anything cheap enough to just do. Then tell me what to commit to, what needs investigating first, and what to decline, with a reason I can actually say out loud to the person who asked.