Roadmaps are dynamic documents—they must be updated when new information is available. Learn how and when to update your roadmap for maximum success.
- Even though some of your stakeholders might wish otherwise, product roadmaps are dynamic documents. They have to be. They represent your organization's development plan at a particular point in time based on the best information available to you at that point in time. When you learn new information about your customers or the market, guess what? You'll need to update your roadmap. So how do you know when it's time to update your roadmap? When you've learned something new that makes the old roadmap no longer seem like the optimal course of action.
There are several types of new information that you might encounter. First, you might've learned information about your customers' needs and desires. For example, you might've tried out a new pricing model and found out that your customers won't accept it. Second, it could be information about your competitors. Say you've just read a major announcement from one of your competitors which makes them more of a threat than you thought. And third, you might've learned something new about the time or cost of product development. The projects that you prioritized on your roadmap might be taking much longer than anticipated to complete.
In all of these cases, you'll probably want to revise your roadmap. Sometimes, team members may approach you and ask for changes to the roadmap. In these cases, it's important that you try to understand the reason for the change. What's the new information that's been learned since the last roadmap update? In some cases, you might find that there really is something new. But in others, you may discover that one of your team members is still not aligned with the decisions made in the previous iteration and still trying to promote their point of view, in which case, you might want to alert your business leader.
The frequency of roadmap updates can vary widely between organizations. If the product you're working on is very immature, you're probably learning new information all the time, so your roadmap will probably change very frequently. If the product is much more mature, and your market is very stable, you might not need to revise your roadmap at all, that is, until everything's been released. Remember that the decision about whether and when to update the roadmap is your responsibility.
As the product leader, you're the guardian of the product roadmap.
This course shows how to build a product roadmap for your business—and gain critical stakeholder buy-in. See examples of what roadmaps might look like, and spend time learning the tools and techniques necessary to map the projects for your specific organization. Instructors Teg Grenager and Eldad Persky help you create strong, dynamic roadmaps that will ensure your team is working on the right projects at the right time.
- What is a product roadmap?
- Roadmaps in agile organizations
- Selecting stakeholders
- Researching customers
- Identifying milestones
- Estimating effort
- Maintaining the roadmap