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?
Product managers often struggle to keep on top of their product roadmap. I recently gave this talk at Landing Festival Berlin to explain where people often get lost and show you how to make your product roadmaps more meaningful, user-centric and measurable.
I gave a talk recently about how I’ve been using data and analytics to guide my decisions in product management. I’ve edited the transcript a little and split it into bite-size parts for your entertainment. This final bit tells the secret behind meaningful product roadmaps. The previous bit was about the benefits of open and transparent data.
Curating the product roadmap is one of the most typical responsibilities of a product manager. But have you ever thought about why you bother with them in the first place and how you could make them more effective?
I’m writing about one hundred things I’ve learned as a product manager.
Product managers hate saying ‘no’. It’s not in our nature to disappoint people. We want everyone to be happy with our products. We’d much rather say a nice, cooperative ‘yes’ that makes everyone happy and leaves us feeling warm and fuzzy.