Theme-based roadmap template — editable, free
A theme-based roadmap groups by the area you are investing in, so the headings outlive the items underneath them. Swapping one item for another changes nothing a stakeholder has to re-learn, which is why this shape survives longer between updates than any other.
| View | Groups by | Visible fields |
|---|---|---|
Themes | Theme | Name, status, owner |
Leadership | Theme | Name, theme, quarter — owner and status hidden |
In flight | Status | Name, theme, owner, dates |
All items | Nothing — one flat list | Name, theme, status, owner, dates, notes |
What counts as a theme?
An area you keep investing in, which outlives the work inside it. Activation is a theme. Rebuilding the onboarding flow is an item. The test is whether the name still reads sensibly in a year with a different list underneath it — if it doesn’t, it’s an item with ambitions.
That durability is the whole argument for the format. A quarterly plan is rewritten every quarter. Four themes survive several planning cycles, so the work underneath can turn over completely while the story a director hears stays the same. It’s also the roadmap that reads best cold, which is most of what a roadmap for new team members is trying to buy: four headings explain the shape of a product faster than forty items do.
What is in this template?
Nine items across four themes — activation, retention, platform and reporting — with owners, quarters and one milestone, so the timeline views have something real to draw. Four views are saved, and they differ exactly as the field table above sets out.
Open the leadership view first. It’s the same nine items grouped by theme, showing the quarter and hiding owner and status. Nothing was copied to produce it: change an item on the theme board and the leadership timeline is already current.
When is a theme the wrong unit?
When the reader needs order. A theme board states what you’re investing in and says nothing about what comes first, so anyone who wants sequence will ask, and the answer is a format built on order instead.
It’s also wrong when the themes turn out to be the team names, which is the failure worth checking for before you present. The item test in what to include in a product roadmap applies one level up: a theme has to survive somebody asking what it’s for. If yours don’t, the answer is usually not a better list of themes — it’s a swimlane roadmap template, which puts the teams in lanes where they belong and leaves the themes free to be themes.
Dates stay in the file here, drawn as quarters rather than weeks. If you would rather drop them altogether, roadmap without dates sets out what has to replace them. Any view exports at 3840 × 2160, which fills a 16:9 slide.
Common mistakes
Naming the themes after the teams. If the themes are Platform, Mobile and Growth because those are the squads, the roadmap is an org chart and the strategy is still unstated.
Running a theme per item. Four or five themes with several items each is a set of bets; twelve themes with one item each is a list with headings.
Never retiring a theme. A theme that has carried no new work for three quarters is either finished or was never a priority, and leaving it on the board hides which.
Expecting a theme to answer when. Grouping by theme says nothing about order, so anyone who needs sequence will ask anyway and you will answer it somewhere else.
Questions
How many themes should a roadmap have?
Four or five. Fewer and a theme is the whole product; more than about six and nobody can hold them in mind, which defeats the reason for grouping at all.
What is the difference between a theme and an epic?
An epic finishes. A theme is an area you keep investing in, so it outlives the items under it and is still there next year with a different list beneath it.
Can a theme-based roadmap carry dates?
The items here carry start and end dates drawn as quarters. The theme board ignores them and the timelines use them, which is why one set of items feeds both.
Do I have to keep the themes in the template?
No. Rename them in the theme field and every view follows, because the grouping refers to the field rather than to the labels you started with.
Related
- Roadmap for executivesFour fields to show, two to hide, and why each call goes the way it does.
- Roadmap without datesSequence and horizon instead of dates, which commitments keep theirs, and why the first bucket fails.
- Now Next Later roadmap templateSequence instead of dates, with a board, two timelines and a table already saved.
Last updated