Road maps are an important part to strategy. It doesn’t matter if you are trying to figure the future of your company, your product, your team or your life – a road map is important to helping your keep track of your goals and the initatives and activities needed to achieve them.
The book Product Leadership: How Top Product Managers Launch Awesome Products and Build Successful Teams By Richard Banfield, Martin Eriksson, Nate Walkingshaw, outlines what is not a road map:
- It is not a release plan—leave out specific dates and timelines.
- It is not a list of features and/or components, nor should it include job stories, user stories, or “jobs to be done”; these are too granular for a road-map.
- It is not a commitment. It is a living guide that reacts to new information
- It is not one monolithic document. Given that we argue for small, autonomous, cross-functional teams focused on specific areas of the product there should be a road map per team.
- A successful road map is not a Gantt chart. Waterfall connections (dependencies) won’t work for this level of planning.
So why is it that so many guides and software packages (either desktop or online) make you create road maps that have timelines and/or look like gantt charts?
There had to be a better, simpler way – and there is.
This is why I created Munro Maps.