Product Roadmap Deck
Specifications
- Slides
- 10 slides
- Aspect ratio
- 16:9 (Widescreen)
- File format
- PowerPoint (.pptx)
- Font
- Calibri
- Version
- 1.0
- Editing
- Fully editable
- Primary color
-
#6D28D9
Style
About this template
Ten slides for explaining the next quarters
A deck for telling executives or investors what you will build over the next two or three quarters and why in that order. Apart from the cover and the closing slide, all eight slides go to prioritisation criteria, this quarter, this half versus next half, key metrics and trend analysis – so unlike an IR deck where the roadmap sits last, this file is a roadmap from start to finish. There is no room here for product or market introduction; put another deck in front of it.
There is no timeline graphic
No gantt bars or quarter arrows exist. Body slides are title, one summary line, three bullets. So the time axis is built one of two ways: use the dividers as quarter names and the body bullets as that quarter’s three items, or use the four bars on slide 9 as four quarters. The trend slide already ships configured that way.
Five agenda lines and the slides behind them
- Change the cover label (PROJECT MANAGEMENT) and the title for your audience, along with the “2026. presenter name / affiliation” line and the template blurb.
- The agenda holds five items – prioritisation criteria, this quarter, this half and next half, key metrics, trend analysis – and every line has a slide. Only the first two get a divider-and-body pair (3-4 and 5-6); the other three are carried by the comparison slide 7, the metric cards on slide 8 and the bars on slide 9.
- If you need one slide per quarter, duplicate a divider-plus-body pair like 3-4 and add an agenda line. The dividers are numbered only 01 and 02, so 03 onward must be typed in by hand.
- There is no separate slot for engineering capacity or review cadence, but the cards on slide 8 already hold 14 engineers and a two-week sprint, so that slide absorbs them.
Three things per quarter slide
Each quarter body takes one thing you will ship, the problem it solves, and the test for done. The defaults on slide 6 show the form: payment module replacement in March / mobile app 2.0 beta / 400ms search response. The first two are dated deliverables and the last is the criterion.
- For example, Q3 2026 – automatic retry for failed payments / manual handling costs six hours a week / done when manual cases fall 90%.
- For example, Q4 2026 – team-level permissions / accounts above 100 seats churn over credential sharing / done when the top ten contracts adopt it.
- Keep slide 4 as is. Stating the yardstick first – 30 or more customer requests takes priority, ordering by expected revenue contribution, 20% of each quarter reserved for technical debt – heads off arguments about the ordering.
The half-year comparison, the cards and the quarter bars
Slide 7 puts the first half (launch) – mobile app general availability, three more payment methods, finer admin permissions – opposite the second half (expansion) – a public API, three additional languages, fraud detection. It folds quarterly plans into halves, so make sure the items from slide 6 reappear in the left column and the two slides tell one story. The cards on slide 8 read 12 items per quarter, 14 engineers, two-week sprints, five days of release validation – all measures of whether the roadmap is achievable. Promise far more than twelve items and the card becomes the counter-argument. The bars on slide 9 are 11 completed in Q1, then 14, 16 and 13 planned, so only the first bar is an actual and the other three are plans. The labels already distinguish completed from planned; do not delete that, or past results and future promises blur into one chart.
Where roadmap talks leak
- Five items per quarter in three bullet slots; the type shrinks and the priority disappears.
- Dates with no definition of done, so the next quarterly review cannot judge what was achieved.
- Letting the three planned bars sum to 43 while the card says twelve items per quarter. A mismatch draws the “which one is real” question first.
A place for the undecided
The information that leaks most often in a roadmap talk is what has not been decided. Duplicate a body slide before the closing slide 10 and list three items under review with the date each will be settled; questions then land on that slide. Since the closing line reads “we ship in the order we promised”, a slide separating what has not been promised is especially useful.