Design roadmap template — editable, free
Design work finishes months before the thing it shaped ships, so a roadmap that only carries ship dates makes most of it invisible. This template groups ten items by design stage — research, exploration, specification, build support — across four surfaces, with a handover marked as a milestone.
| View | Groups by | Visible fields |
|---|---|---|
By stage (board) | Design stage | Name, Surface, Owner, End |
Leadership (timeline) | Surface | Name, Surface, Start, End |
Research pipeline (timeline) | Design stage | Name, Design stage, Start, End, Build support hidden |
All items (table) | Nothing — one flat list | Name, Surface, Design stage, Status, Owner, End |
Why does design work go missing from a roadmap?
Because a roadmap built on ship dates only records the last stage of it. The research that decided what to build happened two quarters earlier, the exploration that ruled out three approaches has no release attached, and neither appears anywhere. The result is a team whose most valuable months are invisible and whose work looks like it starts when the engineering does.
Grouping by stage fixes it without inventing anything. Research, exploration, specification and build support are the four things a design team is ever doing, and each one has a different relationship to time.
What is in this template?
Ten items across four surfaces, with the design stage as the primary grouping and exact dates underneath. The onboarding sequence runs the whole way through — research, then exploration, then specification — so the dependency between stages is visible, not assumed.
The handover to engineering is a milestone rather than the end of a bar. That date is the one other people plan against, and a bar that merely stops doesn’t announce itself.
The third view is the research pipeline: everything except build support, which is what to look at when somebody asks what is coming, not what is being finished.
Who reads a design roadmap?
Engineering, to know when a specification lands. Leadership, to see that the quarter ahead has been thought about. And anybody new, which is the audience this format serves best without trying — roadmap for new team members explains why notes and owner earn their place on a view built for somebody reconstructing two years of decisions.
The question of which fields survive contact with each of those readers is the same one every roadmap faces, and what to include in a product roadmap gives the one test that settles it.
For a fixed window with phases rather than stages, a 90-day roadmap template has the same shape at a different scale. For the calendar that depends on these handovers, a marketing roadmap template marks which of its dates can move. And for the cyclical version of planning by stage, an HR roadmap template separates what repeats every year from what doesn’t.
Common mistakes
Showing only the items that ship. Research and exploration are most of the work and none of the ship dates, so a roadmap built on releases makes a design team look idle in exactly the months it’s busiest.
Putting the handover at the end of a bar instead of on it. A handover is a date somebody else is planning around, and a bar that merely stops doesn’t tell them when.
Running exploration without a research item in front of it. Three directions for a problem nobody has characterised is three ways of being wrong.
Leaving build support off. It’s real work, it lands after the specification is done, and a roadmap without it produces a quarter that looks free and isn’t.
Questions
Why group by stage instead of by project?
Because the stage is what makes the work legible to everyone else. A stakeholder seeing four items in research understands there’s nothing to review yet; the same four items under a project name read as four things that are late.
Should design items appear on the product roadmap too?
The outcome should, once. Duplicating the design work onto the product roadmap gives you two documents holding the same status, and the design one is the one that stops being updated.
How far ahead can design plan?
Research and exploration, one to two quarters. Specification, only as far as the exploration it depends on. Anything drawn beyond that’s a placeholder, and marking it as one is more useful than drawing it confidently.
Related
- 90-day roadmap templateThirty, sixty and ninety day phases with a confidence field, for a window that starts whenever you start.
- Roadmap for new team membersOwner and notes are the payload here, shipped work stays on, and the dates come off.
- What to include in a product roadmapOne test for every item, plus the three things that belong on no roadmap outside the squad.
Last updated