Which formats are people using to share the product roadmap with customers / teammates / investors?
Nick Russell
8 replies
Replies
Pavel Kukhnavets@pavel_kukhnavets
Hygger
It depends on particular tool you use and its features.
For our projects, we use GanttPRO https://ganttpro.com/ - a Gantt chart maker that allows for exporting roadmaps in a couple of clicks. If you choose this PM platform, you can easily share your roadmap data with stakeholders using Excel, PDF, PNG, or XML formats.
Share
@pavel_kukhnavets Thanks for sharing this Pavel! A Gantt chart will always be the first choice for a strictly time-bound roadmap. I'll be sure to check out GanttPRO 🙂
Notaku
I use a simple Kanban board with an "in progress", "under review" and "planned" columns.
If i already know a feature will come next month i will also add a tag like "November" so people know when it will come out
For this roadmap website i used Notaku, it uses a Notion database as CMS and is fully customizable (custom domain, logo, footer, font, background, etc)
Notaku also let you embed the roadmap as a widget in your website (visit notaku.so for an example)
Hmmmm... it's such a tough one because it depends how granular you need/want to go. I guess this would differ depending on the intended audience. But my preferences are...
- Kanban for internal (e.g. Trello or Jira), who can 'open' and find more details about certain items
- Gantt style for engineers (e.g. Asana, Monday), as it show dependencies (e.g. when one feature takes longer than expected, it shows how the whole roadmap is effected)
- A simple slide for investors - keeping things super high level, and at an epic (do they need to know all the details?!)
@dan_robins totally! it's about sharing the simplest picture you can get away with to each audience. It can be hard though because you have to do ALL the work, so it can be tempting to share all of it to everyone - "hey, look at this beautiful ticket sub structure, and naming convention!", but most people don't - and shouldn't - care.