Product Road Map
A well-defined product road map is a sure sign that the product manager has a coherent understanding of the technology and the market. In most cases, the product road map is a document internal to the company. However, a long standing business relationship with a certain business partner or customer will invite queries for sharing the product road map. The importance of accuracy to the product road map escalates in such situations. Needless to say, sharing the Product Road Map with an external party would require the protective cover of an NDA.
What to expect from a Product Road Map?
Engineering point of view
A road map canvassing one to two years helps the engineering manager identify resource requirements. Newer technology will need a study phase that has to be organized. Budget has to be allocated for toolkits, certifications, recruiting etc. Feedback from engineering would involve what components can be built in-house, what needs to be outsourced and what cannot be done. The project manager can use the final road map to schedule activities and help create a project plan.
Sales point of view
The sales team will use the road map to start adding revenue forecasts to the model. In addition, they can start pitching the growth pattern to the customers. In some cases, it also helps identify new customers.
I plan to develop a pseudo road map or add to this topic from time to time.
Planned reading:
The Product Managers Handbook, 3E by Linda Gorchels
Product Management newsletter from http://www.280group.com
