Now Next Later roadmap: how the format works, with an example and answers to "but when?"

A Now Next Later roadmap replaces dates with three columns: Now is what the team is working on at the moment, Next is what it expects to pick up once that's done, and Later is the direction beyond that. Each column is less detailed and less certain than the one before it, because that's how much the team actually knows. You give up exact ship dates and get a roadmap that shows order and priorities honestly, survives new information and doesn't turn every row into a promise. The format was popularized by Janna Bastow at ProdPad and is now one of the most widely used alternatives to the date-based timeline.

What a Now Next Later roadmap looks like

The format works with any unit, but it works best with themes: customer problems tied to business objectives, as described in the outcome-based roadmap guide. A feature in Later is still a promise, just with a vague date. A problem in Later is an honest statement of priority: "this matters, and we'll get to it after the things on the left."

What each column means

Now

Work that is underway or starts as soon as someone is free. Items in Now are well understood: the team can name who owns them, which signal they are trying to move and which solutions they are testing. If Now holds more items than the team has people for, it isn't Now; it's a wish list.

Next

Problems the team expects to tackle once capacity frees up. This is where discovery happens (customer interviews, a look at the data, a rough size), so each item is ready by the time it moves to Now. Order inside Next matters: the top item moves first.

Later

Real priorities that aren't urgent yet or depend on something unfinished, plus bets the team isn't ready to size, written broadly on purpose. Later doesn't mean "maybe" or "never": ideas that serve no objective belong on a separate list (more on that below).

Confidence falls with distance

Estimates made months ahead are guesses, and every finished item teaches the team something that reshuffles the rest. A Now Next Later roadmap shows that openly, in two common ways:

• Confidence per column. State how likely it is that an item happens in that timeframe, in roughly that form: for example, Now 80%, Next 50%, Later 20%. Readers stop treating Later as a commitment when the page tells them it's a one-in-five bet.
• Stage of development. Label each item as discovery, design, in development, beta or released. Stakeholders see at a glance which items are still open problems and which are already concrete solutions.

A roadmap where Later is as detailed as Now is a warning sign: either the team picked solutions before learning anything, or someone added detail to make the plan look certain.

An example: CatChow as Now / Next / Later

CatChow, the Ukrainian cat-food shop with subscriptions and partner vet clinics from the outcome-based roadmap guide, defines its columns on the page: Now is this quarter, Next is the following one or two quarters, Later is beyond that.

Now (this quarter, about 80% confidence)

• Subscribers never run out between deliveries. Signal: cancellations that cite running out or bad delivery timing, from 30% to 15%. Trying: reorder reminders (in development) and flexible delivery dates (still being explored).
• Clinics restock prescription diets without phoning us. Signal: stock-outs from 6 a month to 1. Stage: pilot in two partner clinics.
• Enabling work: replace the warehouse system, because the clinic theme can't grow without it.

Next (the following one or two quarters, about 50%)

• New owners pick the right food on their first order. Signal: "Which food?" support calls from 250 to 100 a month. Stage: discovery.

Later (beyond that, about 20%)

• Long-term subscribers have reasons to stay beyond price.
• Clinics can easily recommend CatChow to pet owners.

The warehouse replacement sits in Now although no customer asked for it, because a Now theme depends on it. The Later themes have no signals yet; the team will define them when they move to Next.

How to answer "but when?"

Someone will ask, usually the CEO or a salesperson with a customer on the line. Here is what works better than making up a date:

1. Put the calendar meaning on the page. "Now = this quarter" answers most "when" questions before they're asked.
2. Answer with order and dependencies. "It's first in Next. It moves to Now when the clinic pilot is done, most likely early next quarter."
3. Give dates only where confidence is high. Work in progress with a known scope can carry a target date or a range, such as "the second half of November".
4. Ask what the date is for. A salesperson often needs something to tell a customer, not a ship date. A date when you'll know more ("we'll decide after the pilot review") may cover it.
5. Offer a trade. If an item must move to Now, ask what leaves Now to make room. That turns a date request into a priority decision, which is where it belongs.

What not to do: invent a date to end the conversation. By the afternoon it will have been repeated to a customer.

The disclaimer

Every Now Next Later roadmap needs a short, dated note that says how firm it is. A good one says that this is the current plan based on what the team knows today, that it isn't a commitment to specific features or dates, and when it will be reviewed. For example:

Updated 2 October. This is our current plan based on what we know today, not a promise of specific features or dates. We review it on the first Monday of every month; expect Next and Later to change.

Put it at the top, not in grey small print, and keep it on internal versions too: salespeople and other teams quote internal roadmaps as readily as customers do. "Subject to change without notice" alone isn't enough, because it doesn't say when or why things change. A roadmap for customers needs firmer wording and less detail.

When quarters work better

Now / Next / Later isn't always the right choice. Quarters or months fit better when:

• The business runs on a fixed calendar: seasonal peaks such as Black Friday for e-commerce, the school year for education products, tax deadlines for accounting software.
• Contracts or regulation set the dates: a law comes into force, or a partner integration has a signed launch date.
• Many teams need to hand work to each other, or hardware and manufacturing have long lead times.
• Budgets and headcount are planned by quarter, and leadership needs the roadmap in the same shape.

A hybrid often works: label the three columns with quarters, or keep Now / Next / Later and add fixed external events as markers. What matters isn't the column names but that certainty falls with distance and nothing far out looks like a promise.

The "Later is a dumping ground" critique

The most common complaint about the format: Later becomes the place where every idea nobody wants to reject waits forever. Stakeholders hear "Later" as "yes, eventually", and the column outgrows Now and Next combined. Some fixes:

• Every item in Later serves an objective. Everything else goes on a separate "not now, and why" list with a one-line reason.
• Cap it. If Later holds more than the team could plausibly finish in a year, cut.
• Keep Later as themes, not features. A feature in Later is a promise nobody has checked.
• Prune at every review. An item that has sat in Later for three reviews without moving gets a decision: promote it, merge it or drop it.
• Say no out loud. A clear "not now, because…" is kinder than a vague Later.

Review the roadmap on a fixed rhythm, monthly for most teams: check the signals in Now, move finished themes out, pull the top of Next into Now only after rechecking the evidence, and update the date in the disclaimer. If the order inside Next is contested, a transparent scoring method helps; see the RICE prioritization guide.

Key takeaways

• A Now Next Later roadmap shows order and priority in three columns instead of dates, with detail and certainty falling from left to right.
• Fill it with themes (customer problems tied to objectives), not features, and define each column in calendar terms on the page.
• Show confidence and stage of development so readers know which items are commitments and which are bets.
• Answer "but when?" with order, dependencies and dates only where confidence is high; never invent a date.
• Keep Later small and pruned, add a dated disclaimer, and switch to quarters when the business really runs on a fixed calendar.

FAQ

What is a Now Next Later roadmap?

It's a product roadmap with three time horizons instead of dates: what the team is working on now, what comes next and what it plans to tackle later. The further out an item is, the less detailed and less certain it is.

How long is "Now" on a Now Next Later roadmap?

There's no fixed length. Many teams use this month or this quarter for Now, the following one or two quarters for Next and anything beyond for Later. Whatever you choose, write it on the roadmap itself.

Can a Now Next Later roadmap have dates?

Yes, in two places: fixed external events, such as a conference or a regulatory deadline, and work in progress where the team is confident enough to give a target date or range. Themes in Next and Later shouldn't carry dates.

Learn it hands-on

The free lesson What a roadmap is (and isn't) starts with a CEO asking for every feature with a month next to it, and you practice answering with direction instead of dates. In Anatomy of a roadmap you define Now, Next and Later for CatChow and write your own disclaimer. Later modules go deeper: Timeframes and the disclaimer, Features, stage of development and confidence and Keeping it fresh, all part of the free course Outcome-Based Product Roadmaps. If you're starting from a feature list, read the outcome-based roadmap guide first.