The Now-Next-Later Roadmap Format Explained

The Now-Next-Later roadmap format organizes a product roadmap into three simple horizons — Now (actively being worked on), Next (planned soon, not yet started), and Later (directionally planned, not yet scoped in detail) — instead of assigning exact dates to every item. It's one of the most widely used roadmap formats specifically because it communicates real priority honestly, without the false precision that comes from putting a specific date on something that hasn't even been scoped yet.

Quick facts

• The three horizons: Now (in active development), Next (planned, not yet started), Later (directional, not yet scoped).
• Items get deliberately vaguer the further out they go, reflecting genuinely lower certainty about far-future work.
• This format avoids the trust problems that come from a date-based roadmap missing its committed dates.
• It connects directly to the broader roadmapping process in How to Build a Product Roadmap.

The three horizons, explained

Horizon	What it means	Typical detail level
Now	Actively being built this cycle	Specific — a defined scope the team has committed to
Next	Planned for the near future, not yet started	Moderately specific — a clear theme, rough scope
Later	Directionally planned, further out	Vague and thematic — a direction, not yet scoped in detail

Why this format avoids the trust problems of date-based roadmaps

A traditional roadmap with exact dates for every item creates a specific trap: far-future items get the same apparent certainty as near-term committed work, even though a feature planned for six months from now hasn't actually been scoped or estimated yet. When priorities inevitably shift — and they usually do — that far-future date gets "missed," creating the impression the team failed to deliver on a promise, even though the item was never realistically a firm commitment in the first place. Now-Next-Later avoids this by being honest about certainty from the start — items in "Later" are understood by everyone to be directional, not committed, so there's no broken promise when they shift.

A worked example

Now:

• Redesigned onboarding flow (in active development, targeting release this sprint cycle)
• Bug fixes for the reporting module (in progress)

Next:

• Team collaboration features (defined at a high level, not yet broken into detailed stories)
• Mobile app performance improvements (planned, scoping starting soon)

Later:

• AI-assisted content suggestions (a direction we're exploring, not yet scoped)
• Expanded integrations marketplace (a longer-term strategic direction)

Reading this, a stakeholder immediately understands: the "Now" items are real, active commitments; the "Next" items are coming reasonably soon but details may still shift; the "Later" items are genuine directions the team believes are important, but nobody should expect a specific delivery date for them yet.

How items move through the three horizons over time

As work in "Now" completes, items from "Next" move up to take their place, getting more detailed and specific in the process. As "Next" items move up, new items from "Later" move into "Next," getting scoped in more detail as they do. This natural flow keeps the roadmap continuously current without requiring a full rebuild each planning cycle — it's a living structure that items pass through as understanding and priority develop, not a static document.

Why "Later" should stay genuinely vague

A common mistake is trying to add false precision to "Later" items, listing specific features or dates for things that haven't actually been validated or scoped yet. This defeats the format's core purpose — "Later" items should stay intentionally thematic and directional ("improve collaboration features" rather than "add real-time commenting with @mentions by Q3") specifically because committing to specifics this far out is usually more confident than the team's actual certainty justifies.

Common mistakes when using Now-Next-Later

• Adding specific dates to "Next" or "Later" items anyway, which reintroduces the exact false-certainty problem this format is designed to avoid.
• Letting items sit in "Next" indefinitely without ever moving to "Now." This erodes trust in the roadmap's usefulness as a planning tool if "Next" items never actually seem to progress.
• Making "Now" too large or vague, rather than keeping it focused on what's genuinely actively being worked on with real, near-term specificity.
• Never revisiting or updating the roadmap. Like any roadmap format, Now-Next-Later only stays useful if it's kept current as work actually progresses and priorities shift.

FAQ

How often should a Now-Next-Later roadmap be updated? Many teams update it at the start of each planning cycle (often quarterly), with lighter updates as items move between horizons in between — the "Now" section especially should stay closely aligned with what's genuinely in active development.

Can Now-Next-Later be used alongside more detailed internal planning? Yes, and often should be — the Now-Next-Later view is typically a simplified, external-facing or broad-stakeholder view, while the team's internal backlog and sprint planning can hold much more granular detail without needing to expose all of it externally.

Is Now-Next-Later suitable for every type of product or company? It works especially well for products with meaningful uncertainty in future plans, which describes most software products — for extremely predictable, low-uncertainty environments (some regulated or infrastructure projects), a more traditional date-based roadmap might still be appropriate.

How is Now-Next-Later different from a traditional Gantt-chart roadmap? A Gantt-chart-style roadmap typically shows specific dates and dependencies across a timeline, useful for detailed project scheduling. Now-Next-Later deliberately avoids this level of date-specificity in favor of communicating relative priority and confidence — the two serve different purposes and audiences.