I’m asked questions about product management from time to time. Here’s one I’ve answered recently:
I would love to pick your brain about roadmaps.
To give more clarity to my team (which is working on two mandates/sub-projects), I would like to empower them with a roadmap/timeline of the project. We already have one, on Confluence that I’ve printed next to our whiteboard. But it’s not “ours”.
Any recommendation in terms of shape/content? Should it be extremely detailed or high level? More generally, how to craft the best roadmap/product timeline for my team?
And for its creation? Any convenient tool or Excel template for this?
If you were to inherit a portfolio of ninety legacy products, some of which hadn’t been updated in years, with varying numbers of users relying on them, what would you decide to do with them? And how would you prioritise which ones to work on?
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.
I’m writing about one hundred things I’ve learned about being a product manager.
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.