Over the last few months, I’ve been looking at new methods and software to manage our platform roadmap. This initiative was somewhat triggered by the Toronto ProductCamp in July, where there was a significant focus on roadmapping.
While the evaluation of roadmapping tools goes on, I have trialled one roadmap format within my organization – the Goal Oriented (GO) product roadmap.
|Evaluation measure(s) of success||…||…||…||…|
As you can see above, the GO roadmap layout is a simple, no-frills table listing upcoming releases. No fancy GANTT charts or tags on a board. It does however list all the significant attributes of a release that everyone in an organization should be aware of – including development, sales, marketing, professional services and support.
The GO roadmap author notes that this roadmap is goal oriented (thus the name “GO” roadmap). Each major release will have a key feature sometimes known as the golden nugget of a release. This ties into the release goal – what is the objective or purpose of this release? And an evaluation of success is also provided – how do we know whether we met our goal? Evaluation measures may be that sales of module x increases 10% or user adoption of solution y increases 20%.
I’m not using the GO roadmap format to actually manage and maintain my roadmap (hence the search for tools) – it’s simply an effective format to present the roadmap to internal staff, enabling all everyone to be on the same page and work to some common goals throughout the organization. It provides answers to key questions in a release:
- When is it available? (Release Date)
- What’s in it? (Key Features)
- Why are we doing it? (Goal)
- How do we know whether we succeeded? (Evaluation measure of success)?
The GO Product Roadmap was developed by Roman Pichler. You can find more information about the roadmap format here.