PM Roadmap Template
(2026 Edition)
4 roadmap formats (with best-use guidance), 7 sections every roadmap needs, and 6 mistakes that turn roadmaps into neglected spreadsheets.
Practice Roadmap Questions Daily — Free →4 Roadmap Formats
1. Now / Next / Later
Group initiatives by certainty, not date. 'Now' is committed. 'Next' is directional. 'Later' is strategic.
🎯 Best for: Externally shared roadmaps. Stakeholders who want direction without false precision.
2. Outcome Roadmap
Organise by outcome (metric to move), not feature. Each outcome has candidate initiatives under it.
🎯 Best for: Teams that want flexibility on how to hit goals. Leadership that cares about results, not specific features.
3. Quarterly Theme Roadmap
Each quarter has 1–2 themes. Every initiative ladders up to a theme.
🎯 Best for: Companies with clear quarterly rhythms. Helps maintain focus across quarters.
4. Timeline / Gantt Roadmap
Classic feature-by-date view. Useful for execution tracking within a quarter.
🎯 Best for: Internal engineering coordination. Bad for external stakeholders — creates false precision.
7 Sections Every Roadmap Needs
1. Vision
One paragraph: what we're building toward over 12–24 months.
2. Strategic Pillars
2–4 themes that organise all work. Helps with focus.
3. Now (Committed)
Next 1–3 months. Real dates. Engineering signed off.
4. Next (Directional)
3–6 months out. Priorities clear, dates approximate.
5. Later (Exploratory)
6+ months. Strategic direction, specifics TBD.
6. What We're NOT Doing
Explicit non-priorities. Prevents 'is X on the roadmap?' from every stakeholder.
7. Metric We're Moving
For each pillar/theme: what's the outcome metric we're trying to shift?
6 Roadmap Mistakes
Roadmap as a list of features — no outcomes tied to any of them
Hard dates 9 months out — creates commitments you can't keep
No 'not doing' section — scope creep is inevitable
Same roadmap for engineering AND executives — different audiences need different formats
Updating only quarterly — falls out of date within weeks
Trying to show everything — dense roadmaps don't communicate
FAQ
What roadmap format is best?
Now / Next / Later is the safest default for externally shared roadmaps. Outcome Roadmap is best for internal PM teams. Gantt-style timeline is fine for engineering execution but terrible for stakeholder communication — the specificity creates expectations that don't match reality. Pick based on audience.
How often should PMs update the roadmap?
Monthly minimum for the 'Now' section; quarterly for Next and Later. If the roadmap is stale for 2+ months, it stops being consulted. The best PM teams treat the roadmap as a living artefact — updated by the PM, visible to everyone, and referenced in weekly updates.
How do PMs handle stakeholders who want their ask 'on the roadmap'?
Show them the trade-off. Don't just add items to the list. 'To fit your ask in the Now column, we'd defer X. Does that swap make sense?' Frameworks like Now / Next / Later make it easier to park things in 'Later' without killing them outright. Stakeholders usually just want to feel heard — parking is often acceptable.
Practice PM Roadmap Thinking Daily
Scenarios on prioritisation, trade-offs, and stakeholder pushback.
Start Free Trial →