Now-Next-Later

Origin & evolution

Janna Bastow, co-founder of ProdPad, introduced Now / Next / Later publicly around 2013 as the default roadmap shape built into ProdPad. She has written that the format came from a simple frustration: teams were producing date-anchored roadmaps that nobody believed, and the act of assigning a quarter to a feature⭐FeatureProduct SpecificationA product capability or featureView reference → created false commitments that eroded trust with stakeholders🧑‍💼StakeholderTeam & OrganisationA person with influence over the productView reference →. The format has antecedents in agile planning and kanban horizon thinking, but Bastow's articulation gave it a name and a clear rationale. It has since been adopted as a first-class roadmap type in Productboard, Roadmunk, Aha!, and other planning tools, and is now the most common alternative to the Gantt-style timeline roadmap.

How it works in practice

Each roadmap item🚩Roadmap ItemProduct SpecificationAn item on the product roadmapView reference → is placed in one of three buckets based on commitment level and readiness.

• Now: work the team is actively doing this cycle. The scope is fixed, delivery is expected, and the item should not move unless something critical changes.
• Next: work the team has committed to beginning once the current cycle closes, typically within four to six weeks. The shape is understood but not yet fully scoped.
• Later: directions the team believes in but has not committed to. These are opportunities🚪OpportunityDiscoveryA validated gap worth solvingView reference → and initiatives🚀InitiativeStrategyA large coordinated effort to achieve a strategic goalView reference →, not specified features. The shape may change substantially before the team reaches them.

A worked example. A B2B SaaS product places "redesign the notification system" in Now (sprint is underway), "add CSV export to the reporting module" in Next (engineering has sized it and it begins after the current sprint), and "native mobile application" in Later (the team sees clear demand but has not scoped it and will not for at least two quarters). The stakeholder reading this roadmap gets genuine direction on where the product is going without false precision on when.

The discipline is in resisting dates. The moment a Next item gets a quarter label, the format converts into a calendar roadmap and the original purpose dissolves. Each horizon also carries its own review cadence: Now reviews weekly, Next reviews monthly, Later reviews quarterly.

When to use it (and when not)

Now / Next / Later is the right format when stakeholders need🫀NeedUserA user need, pain, desire, or constraintView reference → direction visibility and the team genuinely does not know what it will be building in six months. It works well at any stage where the roadmap has become a negotiation about Q3 versus Q4 and the team wants to return the conversation to strategy. It is particularly strong for teams that have lost credibility with date-based commitments and need to reset expectations.

It is a poor fit when procurement, regulatory compliance, or contractual delivery requires firm dates. In those contexts, date precision is not false confidence, it is a contractual fact. The format also breaks when used to park work that is actually rejected: Later is for genuine intent, and items placed there should have a plausible path to becoming real. Using Later as a polite graveyard misleads stakeholders and degrades the format's credibility.

In the Unified Product Graph

Now / Next / Later is a table framework in the planning category. It maps to three entity types, reflecting the different levels of specificity in each horizon.

• The Now column holds feature⭐FeatureProduct SpecificationA product capability or featureView reference → entities: work that is fully specified and in delivery.
• The Next column also holds feature⭐FeatureProduct SpecificationA product capability or featureView reference → entities: work that is committed and scoped enough to have a feature-level definition.
• The Later column holds initiative🚀InitiativeStrategyA large coordinated effort to achieve a strategic goalView reference → entities: directional bets that are not yet decomposed into features.

The distinction between feature⭐FeatureProduct SpecificationA product capability or featureView reference → and initiative🚀InitiativeStrategyA large coordinated effort to achieve a strategic goalView reference → in the Unified Product Graph mirrors the framework's own logic. A Later item that gets promoted to Next should be decomposed into a feature at that point, and the graph captures that transition explicitly. The same nodes appear across framework views, so an initiative in the Later column of a roadmap is also visible in the discovery view and the OKR view, without any duplication.