Roadmaps are one of the best and most important tools for project/product teams. When done well, roadmaps provide tremendous value. When done poorly, I hear things like this from BAs and product owners:
- “Roadmaps are a joke around here.”
- “We don’t follow it anyway, what’s the point?”
- “Oh, you mean the ficticious roadmap?”
- “I can’t even understand this roadmap my leader gave me, this is a joke!”
- “I haven’t had time to collaborate with anyone on the roadmap, so I just put something together to meet a deadline. It won’t stick anyway!”
Roadmaps should be a useful guide for the team through the solution lifecycle. Like any artifact that provides value over time, roadmaps must be fluid and change throughout the year. If your roadmap is created and never looked at again, it’s time to take another look at how your roadmap is developed, maintained and used by the team.
When reviewing your roadmap, consider the following questions:
- Is your roadmap a living document that changes as needs and priorities change?
- Do items on your roadmap get reprioritized, resorted, deleted and added as the year goes on?
- Does the roadmap align with a larger strategy? Are changes to the roadmap aligned with a bigger purpose?
- Does everyone impacted by the roadmap understand the customer point of view and have a value mindset?
- Is your roadmap visible and transparent so the team can see it and discuss it often?
Want to know more about high-value roadmaps? I’m here to help, contact me to learn how to bring value to this important tool!