I used to be one of those people who, when someone mentioned the word roadmap, rolled her eyes. And this is because what I was asked to deliver was a list of features, with a delivery deadline attached to them.

But what if we could flip the conversation and utilize the roadmap as an alignment tool and make it the prototype of our strategy instead? An artifact to describe where you are heading, how you plan to do it, what success looks like, and who you need help from.

Where you have an evolving plan that outlines your direction, helps you with collaboration, and evolves with your learnings.

I discussed my evolving approach to roadmaps in the Talking Roadmaps podcast, where you can hear me talk about:

🙅🏼‍♀️ The biggest mistakes I have made and you should avoid. Spoiler: having a roadmap that looks like a fixed delivery plan for the future. Seriously, do not go there.

🤝  The role of the roadmap as a collaboration tool, emphasizing the importance of communication and buy-in.

✋🏻The fundamental elements of a roadmap: goals. As long as you have clear goals, you can do it even without a product strategy

💡 How to use learnings and insights as a fundamental tool for maintaining your roadmap. And the complexity of communicating confidence levels.

🛼 How we're shaking things up with a rolling 15-month roadmap. What's your take on this approach?

Curious? Listen to the entire conversation below, and let me know your thoughts