This content was originally published more than five years ago and is archived here for preservation.
More up-to-date content is available on this blog.
I’m writing about one hundred things I’ve learned as a product manager.
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?
What is a product roadmap? #
A product roadmap is a way of describing the evolutionary path your product will take. Like any practical set of directions, a good route needs to have a clear destination, as well as the landmarks along the way that will help you to keep on track. You’ll also usually have a general idea of when you expect to reach each point. And if you encounter unforeseen obstacles or heavy traffic on the way, you should be able to re-route so that you can still reach your desired destination without too much delay.
A roadmap is a communication tool for coordinating different groups of people
For all but the most basic of products, your development (or engineering) team will need to know what’s coming up in the mid to long-term. The design decisions they’re taking now may depend on the direction in which your product’s heading. They might need to hire in people with specific skill sets if, for example, you were planning to introduce a new iPhone app later in the year. In much the same way, other teams within your organisation will need to plan ahead to prepare for a major product release.
Telling a good story #
You can think of your roadmap as the emerging story of your product
Like any good DVD box set like The Wire or Breaking Bad, a memorable story needs to have a strong narrative and character development. The broader narrative is divided up into more easily digested episodes, with one or more overarching story arcs that unfold over time. Each episode then has its own storyline with a typical three-act structure: a beginning, middle and end.
In much the same way, you can think of your roadmap as the emerging story of your product, with episodes as development sprints building towards the resolution of a major story arc with a series finale – or a major, themed product release. Within each episode – or sprint – you can extend the analogy further by thinking of epics as being the broader plot elements and the user stories providing the detailed dialogue. And as is usually the case in an individual episode, all the loose plot details are neatly tied up by the end, as should also be the case in a development sprint.
Your roadmap tells a story, so it needs to be coherent. Think about how you could make your product’s story more engaging and memorable.
I wrote a follow-up to this article talking more about roadmaps and product themes if you’re interested. It involves time machines.