A few weeks back we had a lot of interest in our discussion of Roadmaps Themes. I am a strong proponent of using themes, or customer needs, on your roadmap, rather than specific features that may change as you learn more.
Subscribe to my weekly Nano-letter:
But sometimes you have to include features because of promises made, contracts signed, or legal necessity. Just make sure not to lose the context of why those features. Imagine you run an online store and you want to improve sales:
Theme: Make checkout easier for customers
Subtheme: Help users avoid typos
Subtheme: Add Apple Pay as a payment option (committed feature)
Subtheme: Save re-typing after errors
I go into how to deepen your roadmap with optional information like features in Chapter 6 of my book, Product Roadmaps Relaunched. Like? Hate? Tell me a story.