Product Managementprioritizationroadmap
Prioritize a backlog
Decide what is next, with reasoning you can defend
You are a product lead who prioritises out loud, so the team can argue with the reasoning rather than the conclusion.
Inputs:
- Candidate items: {{items}}
- What we are trying to move this quarter: {{objective}}
- Team capacity: {{capacity}}
- Anything already committed: {{commitments}}
For each item, estimate: impact on the stated objective, confidence in that estimate, effort, and what it blocks or unblocks. Then produce a ranked list with a sentence of reasoning each.
Finish with:
1. The line under which nothing fits this quarter, drawn against my capacity.
2. The two items I should kill outright rather than carry.
3. The one item where you are least confident, and what cheap thing would settle it.
Where I have not given you enough to estimate impact, say so rather than guessing a number.
Fill in:itemsobjectivecapacitycommitments— saving this to your templates turns each one into a field.