Prioritisation Framework for Product Directors: template, structure and example

When to use it

Create it when you are accountable for a portfolio spanning several product teams and need one shared basis for investment choices. Use it to make cross-team trade-offs explicit, run prioritisation through named forums on a set cadence, and land recommended next steps so the framework is actually adopted. It sits in the Plan phase, ahead of the Product Prioritisation Matrix.

When not to use it

If you are prioritising within a single team's backlog rather than balancing investment across products, a team-level Prioritisation Framework fits better. If direction is still unvalidated, discovery and opportunity assessment come first; and if you only need to plot an agreed set of candidates, use the Product Prioritisation Matrix.

What you need before you start

• The portfolio strategy and the decisions and outcomes the framework must inform, plus its audience, boundaries and exclusions
• The initiatives or investments to be ranked across teams, with the sources of evidence for each
• Criteria covering value, reach, effort, risk and strategic fit, with proposed weights
• A scoring model and a stated way for scores to translate into a priority decision
• The decision forums, participants, inputs and cadence for prioritisation
• Named contributors from Product Managers, delivery leads, technology, finance, commercial, operations and executive sponsors

Recommended structure, section by section

1. Summary — The framework, the criteria it uses, and how it decides portfolio priorities.
2. Purpose and Scope — The purpose of the framework, the boundaries and exclusions of its scope, the audience it serves, and the decisions and outcomes it is meant to inform.
3. Prioritisation Criteria — The criteria used to evaluate and rank investments, including value, reach, effort, risk, and strategic fit.
4. Scoring Model — The scoring model and weights, how scores translate into a priority decision, and the biases and gaming risks to guard against.
5. Inputs and Evidence — The evidence and inputs required to score consistently, and the sources for each.
6. Decision Process and Forums — The decision forums, participants, inputs, and cadence for prioritisation.
7. Trade-off Principles — The principles for resolving trade-offs, protecting capacity, and balancing value against effort.
8. Worked Example — A worked example showing an item scored, a trade-off resolved, and the decision explained.
9. Cadence and Governance — The prioritisation cadence, review triggers, and governance checkpoints.
10. Recommended Next Steps — The adoption, enablement, or validation actions needed to operate the framework.
11. Ownership and Review — Who owns the framework, the governance forum and approvers, where the source evidence and audit trail live, the review cadence and decision rights, and the events that trigger a revisit.

What good looks like

A strong framework teaches the reader what matters, then helps them act. It is specific enough to guide portfolio decisions yet concise enough to be used, separating evidence from opinion so the reader can see how conclusions were reached. The test: a new reader can describe the framework's purpose, see the recommended next step, know who approved it, and identify what would trigger a revisit.

Quality checklist

• Criteria span value, reach, effort, risk and strategic fit, and it is clear how scores translate into a priority decision
• Evidence is separated from opinion, with sources given for each input
• Scoring biases and gaming risks are named and guarded against
• Decision forums, participants, inputs and cadence are defined, with review triggers and governance checkpoints
• Trade-off principles protect capacity and balance value against effort, with a worked example showing a decision explained
• Recommended next steps for adoption, enablement or validation are set out, and ownership, approvers and the audit trail are named
• Final sign-off sits with the Product Director, 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:

• Product Director 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