A roadmap that includes everything includes nothing.
That's the most common mistake with GTM roadmaps: they're exhaustive instead of focused. 47 tasks for Q3. 12 parallel initiatives. No clear sequence. No underlying principle for deciding what comes first.
The result is predictable: everything gets started, little gets finished, and nothing gets delivered at the quality it requires.
What a GTM roadmap is, and what it isn't
A GTM roadmap isn't an operational plan for every task. It's a strategic tool that answers three questions:
- What are we doing, and when? — ordered by priority, not by availability
- Why are we doing it in this order? — based on explicit prioritization criteria
- What are we deliberately not doing (right now)? — the most honest statement a good roadmap makes
MoSCoW: the universal prioritization framework
MoSCoW only works if the "Won't Have" category actually gets used. Many roadmaps include only Must, Should, and Could, which means everything somehow ends up being important.
The Won't-Have list is proof that real prioritization has taken place.
Prioritization criteria: what actually matters?
Customer centricity: how many customers does this matter to?
One of the most common prioritization problems is allowing a few vocal customers to shape the roadmap more than the many quiet ones.
Good prioritization asks: how many customers or prospects does this affect?
Frequency is the most important criterion for customer centricity.
Revenue potential: what does it deliver?
How much revenue does this initiative enable or protect? Does it open new markets? Reduce churn? Improve win rates?
Revenue potential is quantifiable, and it should be quantified.
Market potential and timing
Is there a window of opportunity? Is a competitor close to establishing itself in the segment? Is a regulatory window opening?
Market potential × time sensitivity is a key criterion that is often underestimated.
Effort and resources: the counterweight
What's the impact relative to the effort required?
A commonly used framework is the impact/effort matrix:
- High impact + low effort = quick wins (priority 1)
- High impact + high effort = strategic projects (priority 2)
- Low impact = deprioritize
Time horizon: 3 phases (Now: 0–90 days, Next: 90–180 days, Later: 6–18 months)
Per initiative: priority (MoSCoW) + criterion + owner + success metric
Governance: quarterly review — what was delivered, what has changed, what needs to be adjusted?
Stakeholder version: executive roadmap (outcomes) vs. team roadmap (activities) — these are not the same document
What does a GTM roadmap that actually gets used look like?
A roadmap that gets used has a few defining characteristics:
- It fits on one page: if you need more than one page, you have a project plan, not a roadmap.
- It shows clear dependencies: what needs to be finished before the next thing can begin?
- It's reviewed and adjusted every quarter: no roadmap survives contact with the market unchanged. That's not a flaw, it's by design.
- It has an explicit owner: who is responsible for maintaining the roadmap and making prioritization decisions?
A roadmap that never changes isn't a living management tool. It's a document nobody reads.
The roadmap isn't the goal.
The goal is to prioritize the right things at the right time. The roadmap is the tool that makes that possible, when it's built well and regularly maintained.