Prioritisation Framework for Heads of Product: template, structure and example
A Prioritisation Framework is the Head of Product's ruleset for ranking initiatives, features and backlog candidates before capacity is committed. It sets the criteria and weighting, the scoring model, the trade-off principles and the governance, so a product team makes consistent, evidence-based choices when demand outstrips available time or funding.
Reviewed by Gensudo Team · Last reviewed 24 July 2026
When to use it
Create it when your product team faces more demand than it can fund and needs a repeatable, transparent way to decide what gets built. Use it to establish the criteria and scoring model, make trade-offs visible, and give executives confidence that the order of work traces back to evidence rather than to the loudest voice. It sits in the Plan phase, ahead of the Portfolio Prioritisation Matrix.
When not to use it
If you are not yet ranking anything and are still validating direction or the problem itself, discovery and opportunity assessment come first. If you simply need to plot an already-defined set of candidates, use the Portfolio Prioritisation Matrix rather than rebuilding the underlying framework.
What you need before you start
- The strategy or portfolio priorities the framework must serve, plus its audience, boundaries and exclusions
- The candidate initiatives, features or backlog items to be ranked
- Evidence for each input, with proven facts separated from assumptions and confidence levels noted
- A chosen scoring model (for example RICE or value-and-effort) and proposed weights
- Known capacity limits, dependencies and risks
- Named contributors from Product Directors, finance, technology, commercial, operations, customer insight and executive sponsors
Recommended structure, section by section
- Purpose and Scope — Why the framework exists and where it applies, including the audience, boundaries and exclusions, and the links to strategy or portfolio priorities.
- Prioritisation Criteria — The criteria used to evaluate and rank work, with the criteria and weighting, the evidence quality, the trade-offs, and the rejected options and why the selected path best supports the outcomes.
- Scoring Model — The scoring model (for example RICE or value-and-effort) and its weights, the evidence each input needs, and the scoring biases, gaming and portfolio-imbalance risks to guard against.
- Inputs and Evidence — The evidence and inputs required to score consistently, separating proven evidence from assumptions, with the confidence level, the validation gaps, and the next evidence required.
- Decision Process — How prioritisation decisions are made and by whom, with the recommended action and its rationale, the decision owner, the approval conditions, and the consequences of no decision.
- Trade-off Principles — The principles for resolving trade-offs, with the criteria and weighting, the evidence quality, the trade-offs, and the rejected options and why the selected path best supports the outcomes.
- Cadence and Governance — How and when prioritisation is run and reviewed, with the accountable owners and contributors, the forums and review rhythm, the decision rights, and the escalation path.
- Worked Example — A worked example showing a real initiative scored against the criteria, the effect of evidence quality on confidence, the resolution of a trade-off, and the explanation of the final priority decision to stakeholders.
- Success Measures and Decision Thresholds — The measurable outcomes, baselines, targets, guardrail metrics, reporting source and thresholds that determine whether to proceed, adjust, scale or stop.
- Ownership and Review — Who owns the framework and how it evolves, with the accountable owners and contributors, the forums and review rhythm, the decision rights, and the escalation path.
What good looks like
A strong framework teaches the reader what matters, then helps them act. It is specific enough to guide real decisions yet concise enough to be used, with assumptions stated, agreements shown and trade-offs made visible. The test: a new reader can describe the framework's purpose, see the recommended order of work, know who approved it, and identify what would trigger an update.
Quality checklist
- Scoring criteria and weights are explained, and the final order can be traced back to evidence
- Proven evidence is separated from assumptions, with confidence levels and validation gaps recorded
- Scoring biases, gaming and portfolio-imbalance risks are named and guarded against
- Trade-off principles are stated and a worked example shows one being resolved
- Success measures, baselines, targets, guardrails and thresholds for proceed, adjust, scale or stop are defined
- Evidence, risks, decisions and named owners are in place before sign-off is requested
- Final sign-off sits with the Head of Product, with senior leadership endorsement where funding, risk or strategic direction is affected
Who creates it, and when
In Gensudo this document is a governed template for:
- Head of Product in the Plan phase (as “Prioritisation Framework”)
Where it sits in the flow
Before this document: RICE Scoring Sheet for Product Managers · OKR Framework for Heads of Product · Opportunity Assessment for Product Managers
This unblocks: Product Roadmap for Product Managers
Frequently asked questions
How is this different from a Portfolio Prioritisation Matrix?
The framework defines the rules: the criteria, weighting, scoring model, trade-off principles and governance. The matrix applies those rules to plot a specific set of candidates. Build the framework first so the matrix that follows is consistent and defensible.
Which scoring model should the Head of Product use?
Any consistent model works, for example RICE or value-and-effort, provided you record its weights, state the evidence each input needs, and guard against scoring biases, gaming and portfolio imbalance. The model matters less than applying it transparently and being able to trace the final order back to evidence.
Who needs to sign it off?
The Head of Product coordinates input from Product Directors, finance, technology, commercial, operations, customer insight and executive sponsors. Final sign-off normally sits with the Head of Product, with senior leadership endorsement where funding, risk or strategic direction is affected.
When should the framework be revisited?
Set a cadence and review rhythm in the governance section, and name what would force an earlier revisit, such as a change in strategy, a shift in capacity, or new evidence that overturns an earlier score. A new reader should be able to identify what would make the document need updating.
Create this document in Gensudo
The governed template, role-specific guidance and AI drafting grounded in cited evidence.
Get started