Now-Next-Later Roadmap
The Now-Next-Later Roadmap is an alternative to traditional roadmaps based on dates, releases, and feature lists.
Its logic is simple: the closer an initiative is to execution, the more detail and certainty it can have. The further away it is, the greater the uncertainty and the less sense it makes to commit to an exact date or a fixed solution.
This format is usually attributed to Janna Bastow and ProdPad, and it has spread among product teams working in changing environments.
Basic structure
| Horizon | What it contains | Level of detail | Level of commitment |
|---|---|---|---|
| Now | Current work or work about to start. | High: problem, scope, hypotheses, criteria, and dependencies are fairly clear. | Higher commitment, though still subject to learning. |
| Next | Likely priorities being prepared or validated. | Medium: there is clear direction, but uncertainties remain. | Moderate commitment; may change with new evidence. |
| Later | Future opportunities, problems, or bets. | Low: ideas, strategic themes, or areas of exploration. | Low commitment; serves to communicate intent, not a promise. |
The idea is not to sort tasks for convenience, but to represent the team's level of learning and decision-making.
Difference from a date-based roadmap
| Date-based roadmap | Now-Next-Later Roadmap |
|---|---|
| Organizes initiatives by months, quarters, or releases. | Organizes priorities by proximity, evidence, and trust. |
| Tends to create explicit commitments. | Communicates intent without promising distant dates. |
| Can give a false sense of certainty. | Makes it visible that uncertainty increases over time. |
| Tends to focus on outputs. | Can connect better with outcomes, problems, and opportunities. |
| Changing it can be perceived as a broken commitment. | Changing it can be understood as adapting to learning. |
A date-based roadmap is not always wrong. It may be necessary in contractual, regulatory, commercial, or complex coordination contexts. The problem arises when distant dates are used to feign certainty where there are still unvalidated hypotheses.
Now
The "Now" column includes the work the team is currently tackling or is ready to tackle immediately.
It should contain initiatives with:
- a well-understood problem;
- a clear connection with objectives or OKRs;
- a prioritized hypothesis;
- a reasonably defined scope;
- identified dependencies;
- success criteria;
- available capacity;
- enough evidence to justify the investment.
"Now" shouldn't be filled with everything someone considers urgent. If everything is in Now, the roadmap doesn't communicate focus.
Next
The "Next" column contains what will probably come afterward but still needs preparation.
It may include initiatives that:
- have a good strategic fit;
- require more discovery;
- depend on learnings from current work;
- need technical or market validation;
- are waiting for capacity;
- could change significantly before reaching execution.
"Next" is a useful space for conversations with stakeholders. It makes it possible to show that a need has been taken into account without prematurely committing to scope or a date.
Later
The "Later" column captures future opportunities, relevant problems, or bets that are not yet ready to be prioritized.
It may include:
- promising ideas without sufficient evidence;
- future strategic opportunities;
- research topics;
- identified but unprioritized needs;
- bets that depend on market changes;
- capabilities that could become relevant later on.
"Later" is not a dumping ground for ideas. It should be reviewed periodically. Some opportunities will move up to Next, others will be discarded, and others will lose relevance.
How to Use It with OKRs
A Now-Next-Later Roadmap gains value when it is connected to OKRs.
Each initiative should answer questions such as:
- What objective does it support?
- Which Key Result could it move?
- What outcome are we seeking?
- What evidence do we have?
- What is the opportunity cost?
- What would happen if we don't do it?
- Is it in Now, Next, or Later because of evidence or because of political pressure?
OKRs help prevent the roadmap from turning into a wish list. Initiatives are included because they contribute to results, not because they were committed out of inertia.
Outcome-Oriented Roadmap
Although many roadmaps show features, the Now-Next-Later format works best when it is oriented toward problems, opportunities, or outcomes.
Weak example:
| Now | Next | Later |
|---|---|---|
| New dashboard | Internal chat | Mobile app |
More useful example:
| Now | Next | Later |
|---|---|---|
| Reduce support tickets about data access in enterprise accounts. | Improve recovery of users who abandon onboarding. | Explore advanced self-service for administrators. |
The second roadmap doesn't eliminate solutions. It simply avoids committing to them before validating that they are the best way to achieve the outcome.
Criteria for Moving Items
Moving an initiative between columns should be an explicit decision.
From Later to Next
It makes sense when:
- the problem gains strategic importance;
- new evidence emerges;
- there are market or customer signals;
- it connects with an upcoming OKR;
- the team needs to research or prepare the opportunity.
From Next to Now
It makes sense when:
- capacity is available;
- the problem is sufficiently understood;
- the outcome is defined;
- the level of uncertainty is acceptable;
- the main dependencies are resolved;
- the team has success criteria.
From Now to Next or Later
It can happen when:
- new information emerges;
- the strategy changes;
- the opportunity cost increases;
- a blocking dependency is discovered;
- the expected impact decreases;
- another initiative becomes more important.
Moving something backward should not always be seen as failure. It can be a mature adaptive decision.
Review cadence
A Now-Next-Later Roadmap should not be left frozen.
A reasonable cadence might be:
- light weekly or biweekly review for Now;
- monthly review for Next;
- quarterly review for Later;
- ad hoc review when OKRs, the market, capacity, or evidence change.
The purpose of the review is not to reopen everything constantly, but to keep the strategy alive without falling into improvisation.
How to communicate it to stakeholders
The Now-Next-Later Roadmap can generate resistance if stakeholders are used to fixed dates.
To communicate it well, it helps to explain:
- that Now carries a higher level of commitment than Next and Later;
- that the time horizon does not disappear, but it is not falsified;
- that Later expresses direction, not a promise;
- that the roadmap is reviewed based on evidence;
- that each initiative is connected to objectives and results;
- that changes are explained through trade-offs, not as whims.
A useful phrase:
“We're not avoiding commitment. We're distinguishing between what we know, what we're preparing, and what is still a bet.”
Relationship with Scrum
In Scrum, the roadmap does not replace the Product Backlog. They are distinct artifacts.
| Artifact | Purpose |
|---|---|
| Now-Next-Later Roadmap | Communicates direction, priorities, and strategic horizon. |
| Product Backlog | Orders the product work in greater operational detail. |
| Sprint Backlog | Gathers the work selected for the sprint. |
The roadmap helps guide the Product Backlog. The Product Backlog turns strategic direction into ordered options. The Sprint Backlog defines a time-bound selection to achieve the Sprint Goal.
Relationship with discovery and delivery
Now-Next-Later can help visualize what is in discovery and what is in delivery.
- Now can include current delivery and immediate discovery.
- Next usually contains opportunities in discovery, validation, or preparation.
- Later works as a portfolio of future opportunities.
This prevents the roadmap from being seen as a conveyor belt of features. Not everything in Later has to make it to Now. Some ideas should die as more is learned.
Now-Next-Later Roadmap and AI
AI can help maintain and analyze a Now-Next-Later roadmap, but it should not decide priorities on its own.
It can help with:
- synthesizing user feedback;
- detecting recurring themes in interviews, tickets, or support requests;
- proposing groupings of opportunities;
- identifying initiatives with no clear connection to OKRs;
- preparing trade-off scenarios;
- checking whether there is too much work in Now;
- drafting explanations for stakeholders;
- detecting old items in Later that should be reviewed.
But the decision to move initiatives between horizons requires human judgment: strategy, opportunity, risk, cost, organizational politics, and accountability.
Common mistakes
Turning it into a date-based roadmap with different names
If Now means "Q1," Next means "Q2," and Later means "Q3," without acknowledging uncertainty, the format loses its purpose.
Filling Now with too many initiatives
Now should communicate focus. If it contains more work than the team can take on, it stops being a strategic tool.
Using Later as an idea graveyard
Later shouldn't pile up everything nobody dares to discard. It must be reviewed and cleaned out.
Showing only features
If the roadmap only contains outputs, it will be hard to connect decisions to outcomes. It is better to express problems, opportunities, or expected results.
Not explaining changes
Flexibility without communication looks like arbitrariness. Every significant change should be explained by new evidence, a strategic shift, or a trade-off.
Best practices
To use a Now-Next-Later Roadmap:
- Connect each initiative to an objective. If it doesn't contribute to any outcome, question why it's there.
- Keep Now limited. Focus is part of the format's value.
- Give less detail the further away the initiative is. Avoid false precision.
- Review Later periodically. Archive or discard whatever no longer makes sense.
- Explain the confidence level. Not all initiatives have the same evidence.
- Distinguish the problem from the solution. Whenever you can, show the problem before the feature.
- Communicate trade-offs. Moving something up to Now means displacing something else.
- Don't promise distant dates if uncertainty is still high. It's better to communicate the horizon and the decision criteria.
Common mistake
Using Now-Next-Later as a cosmetic layer over a fixed roadmap. The most common mistake is to rename the columns while keeping the same logic of fixed commitment. If every item is still tied to a rigid date and is not reviewed based on evidence, it is not a Now-Next-Later Roadmap: it is a traditional roadmap with new labels.
Resources
🏦 OKRs y estrategia de producto [OKRs and Product Strategy, in Spanish]Skill Arena · Scrum Manager
📄 Product Owner v.2.0 [in Spanish]Free download · Scrum Manager
References
- Bastow, Janna. (2022). "Why I Invented the Now-Next-Later Roadmap", ProdPad.
- Cagan, Marty. (2018). Inspired: How to Create Tech Products Customers Love. Wiley.
- Productboard. (2020). "Product Roadmap Example: 7 Real-World Samples", Productboard.
- ProductPlan. (2026). "The Ultimate Guide to Product Roadmaps", ProductPlan.
- Scrum Manager. (2026). OKRs y estrategia de producto [OKRs and product strategy, in Spanish]. Scrum Manager.
- Torres, Teresa. (2021). Continuous Discovery Habits. Product Talk LLC.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.