Providing a Product Roadmap to Customers
When we provide quarterly projections of functionality to customers, it sets their expectations. Internally, there is no way to get a committed delivery date until we are at least half-way through our development cycle. How can we lead the market, conveying a roadmap to our clients without setting expectations?
Firstly, I would suggest that a quarterly revision of your roadmap is too short a revision cycle and very unnecessary. A roadmap is an articulation of a plan, your vision and strategy not a commitment on delivery to the market. I hope your strategy and vision doesn't require a quarterly update, or we may have bigger problems than the roadmap!
We recommend that your external roadmap (the one shared with externally facing audiences) communicate in broad strokes not fine detail. You need to meet the market's legitimate need to understand your vision and plans for the future. Communicate what you can with confidence. Provide a timeline of the projects that have been approved, the markets you have targeted, initiatives for personas, goals, and use scenarios, and even technologies and platforms that you have committed to. I would never suggest you provide a list of features on a roadmap, but rather capabilities or problems that will be addressed in your releases.
If you want to learn more about the roadmapping process and Product Roadmaps in general, I suggest you attend our Roadmapping, Requirements That Work and Practical Product Management seminars, which lay out a different view of product planning for a market-driven enterprise that is "tuned in" to your customers and prospects.
Answered by Rich Nutinsky


