3 Things That Helped Me Manage My Roadmap As A New Product Manager
So you just started as a product manager at a new company and you’re already juggling sitting in on user interviews, speaking with numerous stakeholders and analysing product performance data to understand the ins-and-outs of your product area. One of the biggest tasks on your plate will be to build out your feature/problem area’s roadmap.
My goal with this article is to articulate my learnings from starting a new product role, taking over an existing roadmap and learning to build and grow it — all the nitty-gritty that roadmap guides and templates don’t focus on.
Purpose of a roadmap
The purpose of a roadmap is to communicate the strategy of your team.
It is not primarily intended for planning out your product timeline, your time or your team’s resources. Thinking of it this way can lead to an inflexible roadmap that makes it tougher to deliver features of value that meet user or business needs.
1 — Take it all in
In the first few weeks of your job, take your time to absorb all the information that is on the roadmap and think about why it is laid out the way it is.
Ask your colleagues lots of questions to understand how decision-making works at your…
