Hey Jock, I would love to pick your brain about roadmaps.
If you were to inherit a portfolio of ninety legacy products, some of which hadn’t been updated in years, what would you decide to do with them? And how would you prioritise which ones to work on? This article explains how.
Last time I published an article explaining why I thought roadmaps were a little like DVD box sets. DonorDrive product manager Kasey Marcum (@kaseymarcum) asked in the comments:
“Always enjoy your posts, Jock! I really love the high level idea of this. What does this actually look like in the wild?”
Imagine your roadmap and sprints being as engaging as a hit movie – just think how much easier they’d be to “sell” to your stakeholders and customers! Let’s see how you can do this.
Over the last few weeks I’ve mostly been investigating the variety of tools available to help product managers at different stages of their product’s lifecycle. For me, the emphasis has been on speed and ease of use because my project is short-lived and I want to show some results.
We’re product managers. We’re in charge of the future direction of our products. But when we start thinking about the requirements for a new product version, I bet we all make the same mistake when deciding what goes in.