Skip to contentRoadmapStar

6-month roadmap template — editable, free

A six-month roadmap is two quarters, which is long enough that the second half is not really committed yet. This template says so on the page: every item carries committed, intended or exploring, and the leadership view colours by that instead of by area. Eleven items, four saved views.

The views this template ships with, and what each one shows
ViewGroups byVisible fields

Six months (timeline)

Area

Name, Commitment, Owner, Start, End

Leadership (timeline)

Area

Name, Commitment, Start, End

By commitment (board)

Commitment

Name, Area, Owner, End

All items (table)

Nothing — one flat list

Name, Area, Commitment, Status, Owner, End

Jul 2026
1234567
891011121314
15161718192021
22232425262728
2930311234
567891011
Core product
Rewrite the editor
Integrations
Slack integration
Enterprise
SAML single sign-on
Quality
Cut the flaky tests
The six months view of this template, exactly as the image export draws it.
Open this templateFree · No account · Runs in your browser

What breaks at six months?

Certainty, and it breaks about halfway through. Most six-month roadmaps are drawn as though month six is as agreed as month one, which is false on the day it’s published and obviously false by February. The reader either notices and discounts the whole page, or doesn’t notice and plans against fiction.

So this template carries that distinction as a field. Every item is committed, intended or exploring, and the leadership view colours by that instead of by area — because for the audience reading across two quarters, how sure you’re is more useful than which team owns it.

What is in this template?

Eleven items across four areas, with the commitment field doing the work. Two items are exploring and one of them carries a note saying nobody has agreed to it yet, which is the sentence most roadmaps leave to be discovered.

The enterprise single-sign-on item is committed and contracted, and that’s the model for the exception: a date that already exists outside the company keeps its precision and gets marked as a milestone, because removing it doesn’t remove the obligation.

Four views are saved. The board groups by commitment, not by area, which turns the whole document into one question — how much of this have we actually agreed to — and it’s usually the view worth opening in a planning session.

What replaces certainty you don’t have?

Confidence, stated rather than implied. Roadmap without dates makes the fuller argument: sequence, horizon and confidence do the work a date was doing, and publishing confidence does more for trust than another round of estimation.

This is also the horizon that gets forwarded most, because it’s the one other functions plan their own work against. Roadmap for stakeholders is about the reader you never meet — the third person the picture reaches, with no framing and no way to ask a question — and a commitment field is most of what that reader needs to read the page correctly.

For a window that rolls forward instead of ending, a 12-month roadmap template re-cuts from today each month. For a version organised by the measure rather than the area, an outcome-based roadmap template puts the number on top.

Open this templateFree · No account · Runs in your browser

Common mistakes

  • Drawing all six months at the same weight. Everything on one bar height reads as equally agreed, and the first exploring item to fall takes the committed ones with it.

  • Marking everything committed because the word looks better. The field is only useful if something in it isn’t, and a page where every item is committed is a page nobody believes twice.

  • Leaving exploring items off the page. They’re the ones that surprise people in month four, and a surprise costs more than an early caveat ever does.

  • Re-planning the whole six months every quarter. The first quarter earned its dates; redrawing it alongside the second throws away the only part you had evidence for.

Questions

What is the difference between intended and exploring?

Intended means it’s going to happen and nobody has agreed when. Exploring means it might not happen at all. If you can’t put an item in one of the two, it’s exploring.

Is six months too long for a roadmap?

It’s the longest horizon most teams can support with anything specific, which is why it’s common. The fix isn’t a shorter roadmap; it’s being explicit that the second half is less certain than the first.

How do contractual dates fit in?

They stay exact and stay committed, and it’s worth marking them as milestones. Removing a date you’re already held to doesn’t remove the obligation, and somebody in the room can produce the contract.

Last updated