Prioritise a Product Roadmap
Product & Design · 2–3 days · Intermediate
The job
Turn a backlog of ideas into a sequenced roadmap grounded in user needs and business goals.
What the sponsor gets
Each canvas and map from this playbook — OKR Canvas, Jobs-To-Be-Done Canvas, Prioritisation Matrix, Assumption Map — exports as a PDF, or as PowerPoint on Pro, straight from the session, and the whole run exports as one PowerPoint for the sponsor. Nothing is redrawn.
The method
Gather inputs from all sources
Collect feature requests, user research findings, support ticket themes, sales feedback, technical debt items, and strategic initiatives into a single backlog. Deduplicate and group related items.
Tip: Include technical debt and infrastructure work in the backlog — if it is not visible alongside feature work, it will never get prioritised.
Align on strategic objectives
Create or review the product OKRs for the planning horizon. Every roadmap item should connect to at least one objective — if it does not, challenge whether it belongs on the roadmap at all.
Tip: If the team has more than 3 objectives, the roadmap will be scattered — fewer objectives means sharper prioritisation.
Ground priorities in user needs
Review or create JTBD canvases for the top user segments. Use these to evaluate each backlog item against actual user needs rather than internal assumptions or the loudest stakeholder.
Tip: When two items score equally, pick the one that serves the job your best customers are hiring you for — retention beats acquisition.
Score and rank the backlog
Plot all candidate items on an impact-vs-effort matrix. Include the full cross-functional team — engineering, design, product, and commercial — so the effort estimates are realistic and the impact assessments are not purely technical.
Tip: Give each stakeholder 5 votes to distribute across the high-impact quadrant — it forces genuine trade-offs instead of "everything is P1".
Flag the riskiest bets
For the top-priority items, map the key assumptions about user adoption, technical feasibility, and commercial impact. Items with high-importance, low-certainty assumptions need validation before committing a full build.
Tip: Sequence risky items early in the roadmap — discovering a fatal assumption in Q4 wastes three quarters of build effort.
Build and communicate the roadmap
Sequence the prioritised items into a time-based roadmap with clear themes per quarter. Share it with the organisation, explaining what is in, what is out, and why. Include the criteria you used so stakeholders understand the logic.
Tip: Present the roadmap as "now, next, later" rather than a Gantt chart — it communicates priority without creating false precision about delivery dates.
The canvases and maps
- OKR Canvas
- One objective, three key results and the initiatives beneath them, so ambition and measurement sit on the same page and no initiative floats free of a result.
- Jobs-To-Be-Done Canvas
- Functional, emotional and social jobs sit apart from pain points and desired outcomes, so the team describes the progress people want rather than the features it plans.
- Prioritisation Matrix
- Impact against effort in four quadrants — quick wins, major projects, fill-ins and avoid — so the team trades off instead of calling everything a priority.
- Assumption Map
- Assumptions plotted by importance and certainty, so the leaps of faith that need testing first stand apart from the safe bets.
What it doesn't do
It doesn't run the room for you or decide for the client. The steps, canvases and duration are a starting point you adapt; the judgement stays yours.