2 min read

Roadmaps are important. Respect them!

Roadmaps bring a cross-functional perspective to the fore. We make deliberate choices about a product’s development and document them as a roadmap, and therefore, its importance cannot be underestimated.
💡
For more articles on Scrum, Agile, Product Management, try this link.

A map shows us the way to our destination, along with the obstacles we will encounter on the way but not without alternative routes to get to where we want to go.

Product Roadmaps do the same for us Product Managers.

Road mapping is a crucial exercise and needs to consider ...

... how, and if, items being added in the roadmap support strategic objectives

If a parent company claims to prioritize security over every other non-functional feature, then it is incumbent upon the product team to ensure security is made the central intent in all backlog items.

... the emotion and sense of utility we want our customers to feel

Outcomes are more important than outputs. If we added a wizard to create a form, we want the user to feel at ease that they can use their intuition and successfully design, develop and deploy the form.

We can achieve these outcomes through User Stories and UX.

... how the emotion and sense of utility will be measured

Let me bore you with wisdom you already have: what you don't measure is what you don't know.

Talk to the stakeholders asking to create a new backlog item WHY they feel something is an important addition, WHAT the experience will be and HOW can it be measured?

In situations where the WHAT has multiple answers, consider A/B testing. Its time consuming but I always think it is a CAPITAL INVESTMENT towards a better product experience.

... the opportunity cost associated with the backlog/roadmap item

If only we could have everything we wanted, but we don't and therefore, we have to be SURE about what backlog items can be de-prioritized (or even removed) because we want that new shiny feature (that we believe will be lapped up with glee with our users).

... product release strategy

Product Roadmaps are not ONLY supposed to be about the technical work underway (features, enhancements and defect fixes). I learnt this lesson the hard way. Product Roadmaps must consider the 'cradle-to-deployment' plan for each release and, by necessity, should collaborate with marketing, sales and operations as and when needed. We can create the most mind-blowing feature in the world but if our users are unaware of its existence, is it truly mind-blowing?


I write to remember, and if, in the process, I can help someone learn about Containers, Orchestration (Docker Compose, Kubernetes), GitOps, DevSecOps, VR/AR, Architecture, and Data Management, that is just icing on the cake.