A roadmap is not a schedule. It's a communication tool — a way of conveying strategic direction and current priorities to multiple audiences simultaneously. Most teams use it as a schedule and wonder why it keeps going wrong.
The classic roadmap problem: the PM spends two weeks building a beautiful quarterly roadmap. Stakeholders approve it in a planning meeting. One month later, a major customer has a critical need, a competitor launches something significant, or the CEO changes strategic direction. The roadmap becomes outdated. The team is caught between the plan they committed to and the reality they're operating in.
This happens not because roadmaps are inherently bad tools but because the roadmap is being used as a commitment device instead of a communication device. When a roadmap is a commitment, changing it is a breach of trust. When a roadmap is a communication device about current thinking, updating it as thinking evolves is the expected and healthy behavior.
The Audience Problem: One Roadmap Doesn't Serve Everyone
Different stakeholders need different things from a roadmap. Engineering needs to know what they're building in the next 6 weeks with enough precision to make technical decisions. Sales needs to know what's coming in the next 6 months with enough specificity to inform customer conversations. Leadership needs to understand the 12-18 month direction with enough clarity to make resource allocation decisions. Investors or board members need to see the 2-3 year vision.
One roadmap cannot serve all these audiences well simultaneously. A roadmap detailed enough for engineering is too granular for investors. A roadmap abstract enough for investors is too vague for engineering. The solution is layered roadmaps — different representations of the same underlying strategy at different levels of precision for different audiences.
The underlying strategy is the source of truth. The roadmap representations are audience-specific views into it. When the strategy changes, all the representations update from the same source. When an audience asks a question, the PM can explain which view they're looking at and pull up a different view to answer the question.
The Practical Roadmap Structure That Works
Now (current quarter): high specificity
What the team is committed to delivering in the current quarter, broken down by sprint or month. Specific enough for engineering planning and stakeholder expectation-setting. Updated at the start of each sprint based on what was actually completed and what shifted.
Next (following 1-2 quarters): medium specificity
The direction you're heading and the major problems you're planning to solve, with rough sizing and sequencing but without detailed feature specifications. This is where you're making strategic commitments without technical over-commitment. Change is expected as you learn from the current quarter's work.
Later (6+ months): strategic direction
The major themes and opportunities you're exploring, with intentional vagueness about specific features. "We believe that enterprise account management is a major opportunity in H2" is an appropriate level of specificity for this horizon. Specific features in this bucket are likely to change significantly as you learn more.
Maintaining Roadmap Health
A roadmap's health can be assessed by one question: does the team use it to make decisions, or do they use it only to communicate what's been decided elsewhere? A roadmap that's consulted when making prioritization decisions is a healthy roadmap. A roadmap that's updated after decisions have been made elsewhere is a reporting artifact, not a planning tool.
The PM who runs the quarterly planning process by filling in the roadmap template from their own thinking, presenting it for approval, and then updating it as events dictate is operating a communications system. The PM who runs the quarterly planning process by facilitating discussions about strategic direction, having those discussions in the roadmap format, and using stakeholder feedback to refine the roadmap before finalizing — that PM is running a genuine planning system.
Roadmap planning not working?
Roadmap dysfunction is usually a symptom of either unclear strategy or poor stakeholder communication — and often both. I've helped teams build roadmap practices that actually work for planning. Let's diagnose what's not working for you.
Work with Yogesh →