Skip to main content
A roadmap is one of the most misunderstood artefacts in product. Most people think of it as a schedule - a list of features with dates attached. That version exists, but it’s usually more harmful than helpful. The more useful version is a direction-setting tool that communicates priorities and intent without locking you into decisions you’ll regret in three months 🗺️

​
What a roadmap is for

A roadmap answers the question: where is this product going and why? It aligns the team, gives stakeholders visibility, and forces prioritisation. Those are legitimate needs. What it’s not for: committing to ship specific features on specific dates. The moment a roadmap becomes a contract, it starts working against you. Teams stop questioning bad ideas because they’re “on the roadmap”. Discovery gets squeezed because delivery is already planned. Dates get hit at the expense of quality or correctness.

​
The now-next-later format

The most PM-friendly roadmap format is now-next-later - three time horizons with decreasing specificity. What you’re working on now is concrete. What’s next is directional. What’s later is intentionally vague. This matches how much you actually know. You have high confidence about what’s in the current sprint, reasonable confidence about the next few months, and much lower confidence about anything beyond that. A roadmap that pretends otherwise is lying to your stakeholders 💡

​
Outcome-based roadmaps

The more powerful shift is moving from feature-based to outcome-based roadmaps. Instead of “add bulk export in Q2”, the roadmap says “reduce time-to-value for enterprise users”. The outcome stays stable even as the solution evolves through discovery. This is what Marty Cagan advocates in Inspired and Empowered - teams that own outcomes, not feature backlogs.

​
The stakeholder tension

The hardest part of roadmapping isn’t the format - it’s the stakeholder dynamic. Sales wants commitments. Executives want certainty. Both are understandable. The job is managing that tension without letting it turn your roadmap into a feature factory 🙌 Lesson learned: the best roadmap conversation I’ve had started with a stakeholder asking “when will X be done?” and ended with us agreeing on the outcome X was meant to achieve - and realising there was a faster way to get there.