What Is a Now-Next-Later Roadmap

What does a Now-Next-Later roadmap mean?

A Now-Next-Later roadmap is an outcome-focused roadmap format that organizes work into three horizons based on confidence rather than fixed dates: Now holds what the team is actively working on, Next covers problems being validated for likely near-term work, and Later captures strategic bets still under consideration. Per ProdPad, whose co-founders Janna Bastow and Simon Cast say they created the format in 2012, the roadmap frames items as problems to solve rather than features to ship, and it deliberately avoids the promised dates that make traditional timeline roadmaps break trust the moment a deadline slips. ProdPad describes the right-hand column plainly: "Later holds the big bets: strategic problem areas the team cares about but has not yet shaped into something workable."

How long is Now, Next and Later?

Noah Weiss, writing as SVP Product at Foursquare in his 2014 Medium post Roadmaps without the Drudgery, put numbers on the three buckets: Now is the next 2 to 4 weeks, Next is 1 to 3 months out, and Later is 3 or more months out. He argued that companies between 20 and 1,000 people are the sweet spot for a lightweight system like this, small enough that heavy planning committees are overkill and large enough that nobody can hold the plan in their head.

Column	Timebox (Weiss)	Confidence	What the item looks like
Now	Next 2 to 4 weeks	High: problem validated, solution chosen	A scoped piece of work with acceptance criteria and an owner
Next	1 to 3 months out	Medium: problem validated, solution open	A problem statement plus the experiments still to run
Later	3+ months out	Low: problem area believed to matter	A one-line bet and the signal that put it there

The timeboxes are Weiss's convention, not a law. ProdPad's version refuses fixed durations entirely and sorts only by confidence, which is the safer choice for a public roadmap where a customer will read "Next" as "within three months." Pick one convention, write it on the roadmap itself, and stick to it.

What detail should each column carry?

Specs belong in Now, and only in Now. Weiss makes the same point about the far column, where he says ideas can stay much less specific than in the first two buckets, and he is blunt about ranking inside it: "The prioritization within this bucket is not that important, since you'll revisit it all in a few months anyways." The practical rule is that detail should be proportional to commitment.

A Now item is build-ready: the solution is chosen, the acceptance criteria are written, and engineering has sized it. A Next item is discovery-ready: the problem has evidence behind it, but the team is still testing which solution works, so what it carries is a problem statement, the riskiest assumption, and the experiment that will test it. A Later item is a placeholder for a problem area, with a sentence on why it might matter and no solution at all. Writing a full spec for a Later item is wasted work, since the problem will have changed by the time the team reaches it.

The common failure is a roadmap where all three columns look the same: nine neatly written features, each with a paragraph of solution detail. That roadmap has the same false precision as a Gantt chart, only with the dates removed.

Now-Next-Later roadmap example

Take a fictional scheduling app for independent physiotherapy clinics. The quarter's goal is to cut no-shows, which cost the clinics revenue on every empty slot.

Column	Item	What is written on the card
Now	SMS reminder 24 hours before each appointment	Scoped: message template, opt-out handling, sends from clinic's number. Acceptance criteria written. Ships in the current sprint.
Next	Let patients reschedule from the reminder	Problem: patients who cannot make it simply do not show. Assumption to test: a one-tap reschedule link fills the slot. Experiment: manual reschedule link for 3 clinics.
Later	Waitlist that auto-fills cancelled slots	Bet: clinics lose revenue on late cancellations. Signal: raised by several clinic owners. No solution yet.
Later	Insurance pre-authorisation check	Bet: admin time on insurance is high. Signal: one large clinic asked. Needs discovery before it moves.

If the reschedule experiment works, the reschedule link moves into Now with a real spec. If it fails, the card is rewritten around what the team learned. The waitlist stays visibly parked in Later rather than silently dropped, so a clinic owner asking about it gets an honest answer instead of a vague maybe. This structure pairs naturally with a triple-track roadmap, where Now maps to the build track and Next maps to active discovery.

Is a Now-Next-Later roadmap the same as an outcome roadmap?

A Now-Next-Later roadmap can be a feature roadmap or an outcome roadmap, and the difference sits in what the cards say, not in the columns. A feature roadmap lists solutions that leadership has already chosen ("add SMS reminders"), and the columns only express timing. An outcome roadmap lists problems or goals tied to an objective ("reduce no-shows by making it easy to cancel early"), and the team chooses the solution as it moves right to left. The example above is an outcome roadmap in Next and Later and a feature roadmap in Now, which is exactly how it should look: solutions only become fixed once they are about to be built.

The honest limitation is that the three columns hide parallel work. Within one quarter a team is usually running discovery on Next items, building Now items, and measuring what it shipped last month, all at the same time. A three-column board shows none of that measurement work, which is why teams that need to show discovery, build and measurement explicitly move to a triple-track roadmap.

Why a Now-Next-Later roadmap matters for product managers

Builders Camp's own template library describes this format directly as a roadmap that organizes work by time horizon and eliminates low-value items rather than letting everything accumulate on a single undifferentiated list. The practical benefit for a PM is honesty with stakeholders: Later items are visibly less certain than Now items, which gives a PM a legitimate way to say a specific date has not been committed to, without that answer sounding evasive the way it does on a roadmap that presents every item with the same false precision. That same honesty makes the format easier to defend in front of an executive who wants a date, since the structure itself explains why one column has commitments and the other two do not.

Deciding what earns a place in Now is a prioritization question, not a roadmap question. The prioritization matrix and the step-by-step sequence in how to prioritize features cover that part, and a blank layout to fill in is in the product roadmap template.

Where to practise building a roadmap like this

Product Manager Foundations is a 2 week Builders Camp bootcamp with 4 live sessions, taught by Andre Albuquerque and part of the Product Management Starter Track. Vision, strategy and roadmapping is one of its six published topics, alongside prioritization and MVP thinking, and its practical challenge takes one real product problem from problem statement through a PRD, a metrics framework and a growth plan. Product Strategy covers the portfolio thinking that decides which bets belong in Later in the first place.

See the Product Manager Foundations bootcamp