How to make a simple product roadmap
A roadmap does not have to be big to be useful. This one covers about four months: eight initiatives in three areas, each with a status and a priority. It is one of the two plans every new Tidigar library starts with, and a good place to start your own. The same plan appears below as a timeline and as a board.
Timeline: what happens when
Each area has its own row and its own color.
Overlaps are normal: the design system and the help center run alongside the first product work. What matters is that each area has a clear next step and that the high-priority work is not squeezed into the last weeks.
Board: where each initiative stands
The same initiatives with areas as rows and status as columns.
One initiative is complete, three are in progress and four are planned. A roadmap that is mostly Planned at the start of a quarter is healthy; one that is mostly In progress halfway through has too much going on at once.
Make it yours
- Choose Open in Tidigar to get your own copy. It is free, needs no account and stays on your device.
- Rename the areas to your teams or products, and the initiatives to your own.
- Drag each initiative to its real dates, and update its status on the board as work moves.
- Add dependencies, milestones and saved views when the roadmap grows; the project plan shows how.
Frequently asked questions
What belongs on a product roadmap? The few initiatives that matter most for the next months, with a rough time and an owner. Tasks belong elsewhere.
How detailed should dates be? For a few months, weeks are enough. Move to months or quarters for longer horizons.
Why both a timeline and a board? The timeline answers "when", the board "how far along". Most roadmap meetings need both.