WHAT IS A ROADMAP?
- Vision and direction of product offering over time
- Plan for executing the company strategy
- Stakeholder alignment
- Options and scenario planning
- Lifecycle of product (including EOL)
Often a pictorial timeline that shows what products are being released:
WHAT ABOUT TECHNOLOGY?
More and more products rely on some sort of technology. While new technologies are great (and have often propelled a company to be a leader), they can be risky, particularly in the early stages while the technology is developing and all the problems with it have been ironed out.
So as well as mapping out your product roadmap, consider the technology and performance requirements of your product.
We see the common traps:
- Committing to a product release date when depending on technology that isn’t proven
- Delivering the product to market with technology that isn’t reliable enough
- Your existing technology gets overtaken by new technologies that perform better and/or cheaper and by the time you realise it, it’s too late. Remember Blackberry, Nokia, Kodak, etc
BUT CAN’T WE FIX IT WITH SOFTWARE?
Many products include some sort of software and often problems (even hardware problems) can be fixed with a software update. Or we can release a feature when it is ready.
Back a few years ago you might get a new version of software once a year. But these days we seem to get software updates all the time and it has become the “new normal”
But relying on software to compensate for hardware problems can only go so far – remember the Samsung Galaxy Note 7?
The other thing you need to factor into your roadmap are the many external factors and trends that can impact the success of a product / company
- Customer buying habits
- New business models
- Technology trends
- Regulatory requirements
There are a few models out there that you can use to help identify other influences – here’s a couple:
HOW TO MAKE SENSE OF ALL THIS?
Here’s a few tips to make your roadmapping exercise more successful
- Make it visible so everyone can see it in the company
- This gets a bit tricky when there is sensitive information that you don’t want to be known outside of the company
- Include a good range of people in your company in the process
- Not only are you getting their perspectives and ideas, but it’s a great way of getting their buy-in to the resulting roadmap / plan
- Write it down
- The thing that often gets lost/forgotten is the work done leading up to the finalisation of the roadmap, eg: research, information gathered, results of discussions, trade-off decisions, etc.
- Capture it so that it can be leveraged (and so we can remember our reasoning for a decision)
- Update it
- As soon as it is approved and filed, it becomes out of date
- Things are always changing and the company needs the ability to adapt based on new information/learnings
- And so you need to update your roadmap as things change. And it’s a really good way of evaluating the impact that the change may have, taking into account the work done on the roadmap previously
HOW WE CAN HELP
What companies find is it’s useful to have someone external who is able to facilitate the roadmapping session that it doesn’t have any of the internal baggage, eg: politics, etc
We can provide a different perspective and can talk about other industries we have worked in and the strategies they used a both from a technical/product perspective, but also different business models.
More often than not, we won’t have the deep technical or domain knowledge of people in the company. But that’s actually a good thing – we can ask the stupid questions and challenge assumptions.
What an engagement would look like are a series of workshop’s where we would progressively develop a visual representation of the roadmap as well capture all the background information. They key point it will be in the form of something that can be easily and regularly updated as things change – could be a flipchart with post-it notes or something in an electronic format.
If you would like to discuss roadmapping, feel free to give us a call: