Roadmap
ROHD-map
A strategic plan that outlines upcoming product features, priorities, and timelines to align the team and communicate direction.
A roadmap is the plan for what your product team will build and roughly when they will build it. It communicates priorities to the team, leadership, and sometimes customers.
The best roadmaps organize by outcomes, not features. Instead of 'Build Slack integration in Q2,' a good roadmap says 'Reduce time to first value for new users' and lists the Slack integration as one initiative that serves that outcome. This gives the team flexibility to find the best solution while keeping everyone aligned on what matters.
Roadmaps are not promises. They are plans, and plans change. A roadmap that never changes means the team is not learning. The key is to be transparent about what is committed (next 2-4 weeks), what is planned (next quarter), and what is exploratory (beyond that).
Examples
A PM presents the quarterly roadmap.
The roadmap has three sections: Now (in progress), Next (planned for this quarter), and Later (under consideration). The 'Now' section is specific. The 'Later' section is themes, not features.
A customer asks about a feature on the roadmap.
The sales rep says: 'That is on our roadmap for Q3, but I cannot commit to a specific date. I can share that it is a priority and introduce you to the PM who owns it so you can influence the direction.'
A roadmap changes after customer feedback.
Three enterprise prospects independently request the same integration. The PM moves it from 'Later' to 'Next.' The roadmap adapts to market signal, not just internal opinion.
In practice
Read more on the blog
Frequently asked questions
Should you share your roadmap publicly?
It depends on your audience and competitive landscape. Sharing a high-level roadmap builds trust with customers and prospects. But sharing specific dates creates expectations that may not be met. Most companies share themes and priorities, not dates.
How far ahead should a roadmap plan?
Current quarter in detail, next quarter in themes, beyond that in strategic direction only. Planning specific features more than one quarter out is usually a waste because priorities change as you learn more.
Related terms
A document that defines what a product or feature should do, who it serves, and how success will be measured.
A goal-setting framework that pairs ambitious objectives with measurable key results to track progress.
A meeting where the team selects which work to complete in the upcoming sprint and plans how to accomplish it.
A structured method for deciding which features or initiatives to work on first based on impact, effort, and strategic alignment.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.