Roadmap template
Build a Now / Next / Later roadmap without false precision
Use three decision horizons to communicate current focus, likely follow-on work, and important options while keeping goals, rationale, and uncertainty visible.
Quick answer
What is a Now / Next / Later roadmap?
A Now / Next / Later roadmap organizes product priorities into three relative horizons. Now is the active focus, Next contains likely follow-on work, and Later contains important options that need more evidence, capacity, or strategic confidence.
Copy the structure
The practical Now / Next / Later template
Keep the number of Now items intentionally small. If everything is in Now, the roadmap no longer communicates priority. Use themes or outcomes at the roadmap level and keep detailed tasks in the delivery backlog.
| Horizon | Use it for | Include |
|---|---|---|
| Now | The few themes receiving active focus | Outcome, owner, rationale, supporting inputs, immediate constraint |
| Next | Likely follow-on priorities that need more readiness | Expected outcome, open assumption, dependency, evidence needed |
| Later | Important options without a near-term commitment | Problem or opportunity, strategic link, reason for waiting, review trigger |
Five steps
How to build the roadmap
- 1
1. Define the planning goal
Write the outcome or strategic direction that should guide this version of the roadmap.
- 2
2. Gather decision-relevant inputs
Collect customer problems, business needs, ideas, evidence, dependencies, and capacity constraints.
- 3
3. Create outcome-oriented themes
Group related inputs and name each theme by the problem or outcome, not only by a proposed feature.
- 4
4. Assign a horizon
Use relative priority, confidence, urgency, and readiness to choose Now, Next, or Later.
- 5
5. Add rationale and review triggers
State why the item belongs there and what new evidence, dependency, or constraint would cause a change.
Example
A startup activation roadmap
| Horizon | Theme | Rationale |
|---|---|---|
| Now | Help new users reach first value | Activation is the current goal, onboarding friction is repeated, and the team has capacity to address it. |
| Next | Improve team sharing | Sharing supports retention, but the team needs to validate where collaboration currently breaks down. |
| Later | Expand reporting options | The opportunity is relevant, but usage volume and customer evidence are not strong enough yet. |
Quality checks
Avoid the common template mistakes
- Do not use Now as a list of every task already in progress.
- Do not put precise delivery promises into Next or Later without enough certainty.
- Do not name every theme after a feature if the underlying outcome matters more.
- Do not move items between horizons without recording the reason.
- Do not let Later become a permanent archive of unreviewed ideas.
- Do not publish one roadmap view to every audience if they need different levels of detail.
Maintenance
Review the roadmap on a decision cadence
Review the roadmap whenever strategy, customer evidence, capacity, or dependencies change materially. A regular monthly or quarterly review can work, but important new evidence should not wait for an arbitrary date.
During the review, ask whether Now is still the best use of capacity, whether Next has gained enough evidence to advance, and whether Later items still deserve attention. Record the reason for meaningful changes.
Editorial sources
Goalward reviewed these primary sources on July 17, 2026. The guide above is original analysis and is not a copy of source material.
- Atlassian: Agile roadmaps
Roadmap context, adaptability, and Now / Next / Later guidance.
- ProdPad: Product roadmap software
Outcome-focused Now / Next / Later roadmapping approach.
Common questions
Questions about now / next / later roadmaps
Does Now / Next / Later mean this month, next month, and later?
Not necessarily. The horizons communicate relative priority and confidence. A team can define approximate time ranges, but it should avoid implying certainty it does not have.
How many items should be in Now?
There is no universal number, but Now should remain small enough to represent real focus. Capacity and the size of each theme should determine the limit.
Is a Now / Next / Later roadmap the same as a backlog?
No. The roadmap communicates direction and priority at a higher level. The backlog contains delivery-ready work and implementation detail.