Most SaaS roadmaps fail in the same way. The team publishes a timeline, a few dates slip, and the roadmap quietly turns from a trust signal into a list of broken promises.

A Now-Next-Later roadmap is the simplest fix many small product teams can adopt this week. It keeps the roadmap honest about uncertainty, still shows customers where the product is heading, and works well on a public roadmap board.

Quick Answer

A Now-Next-Later roadmap groups work into three horizons instead of calendar dates. Now holds the problems the team is actively solving, Next holds the problems it expects to tackle once current work finishes, and Later holds valid ideas that still need evidence or capacity. Janna Bastow of ProdPad, who created the format, describes it as a way to communicate priorities and direction without creating false certainty. For SaaS teams, the format works best when each card describes a customer problem, has an owner, links to evidence, and is reviewed on a fixed rhythm.

Why Timeline Roadmaps Break Trust

Timeline roadmaps look precise. That precision is usually the problem.

Early-stage teams rarely know exactly when a feature will ship. Discovery changes the scope, a dependency moves, a support fire takes a sprint, or a better opportunity appears. When the roadmap carries a date, every one of those normal events becomes a visible miss.

Customers do not see the reasons. They see that "Q3" became "Q4" and then disappeared.

Atlassian describes a roadmap as a shared source of truth for the vision, direction, priorities, and progress of a product over time, and stresses showing why work matters, not only what is being built. A Now-Next-Later roadmap keeps that purpose while removing the dates that the team cannot yet defend.

What Goes in Each Column

Now

Now is for work that is funded, staffed, and actively moving. A good rule: if nobody is working on it this cycle, it does not belong in Now.

the team has started discovery, design, or build;

there is a named owner;

the problem is clear enough to explain in one sentence;

the team can describe what "done" looks like.

Keep Now small. Three to five items is usually plenty for a small SaaS team. A crowded Now column signals that the team is spread thin.

Next is for problems the team intends to solve once capacity frees up. The problem is validated, but the solution may still change.

evidence exists, such as repeated requests, votes from target customers, or support patterns;

the team has a rough idea of size and risk;

the item could move into Now within the next one or two cycles.

Next is a strong intention, not a promise. Say that plainly on the public board.

Later

Later holds ideas that are worth keeping visible but are not ready. That includes requests with weak evidence, large bets that need discovery, and items waiting on another dependency.

the problem is plausible but not yet proven;

the item may be split, merged, or dropped after review;

it should carry a short note explaining what evidence would move it forward.

Later is not a graveyard. If an item has sat in Later for several review cycles with no new evidence, retire it with a short explanation instead of leaving it to rot.

Write Cards as Problems, Not Features

The biggest upgrade most teams can make is to describe outcomes rather than solutions.

Feature wording:

"Add CSV export."

Problem wording:

"Finance teams need to get monthly usage data out of the app without asking support."

Problem wording leaves room for the team to choose the best solution, keeps customers focused on the need, and makes it easier to connect the card to a business goal. It also ages better: if the team ships a scheduled report instead of a CSV button, the card is still accurate.

A Simple Card Template

Use the same fields on every card so reviews stay fast:

Problem: one sentence describing the customer need;

Who it helps: the customer segment or plan;

Horizon: Now, Next, or Later;

Owner: the person accountable for the next decision;

Evidence: votes, request count, support tickets, churn or lost-deal notes;

Confidence: low, medium, or high;

Public wording: what customers will read;

Next review: the date the card will be checked again.

The public wording field matters. Internal notes can be blunt about trade-offs, while the public line should be useful, short, and careful about commitments.

How to Move Items Between Horizons

Movement between columns should follow evidence and capacity, not volume or pressure.

Move an item from Later to Next when:

repeated requests arrive from your target customers;

the problem links clearly to retention, activation, or revenue;

a dependency that blocked it is resolved.

Move an item from Next to Now when:

a team member has capacity and is assigned;

the scope is understood well enough to start;

the item outranks the alternatives in your feature prioritization matrix.

Move an item out of Now when it ships, stalls, or is deliberately paused. If it stalls, say so publicly rather than leaving it frozen in Now.

Mapping Now-Next-Later to a Public Roadmap Board

Many public roadmap tools, including RoadmapR, organize items by status rather than by horizon. RoadmapR boards use four statuses: Under Review, Planned, In Progress, and Completed. RoadmapR does not ship a dedicated Now-Next-Later view, but the horizons map cleanly onto those statuses:

Now maps to In Progress;

Next maps to Planned;

Later maps to Under Review;

shipped work moves to Completed and should point to a changelog entry.

With that mapping, customers can vote on Under Review and Planned items, the team can see which Later ideas are gaining support, and Completed items close the loop. The status hygiene checklist explains how to keep those statuses accurate over time.

Review Rhythm

A Now-Next-Later roadmap only stays honest if someone reviews it on a schedule.

Every cycle or sprint: update Now, confirm owners, and move shipped items to Completed.

Monthly: review Next and Later, check new votes and requests, and retire stale items.

Quarterly: check that the roadmap still reflects company goals and that each Now item ties to one of them.

Keep the review short. The goal is calm, regular adjustment, not a monthly debate about every request.

Common Mistakes

Sneaking dates back in. Adding "Next (Q2)" turns the format back into a timeline. If a date is truly committed, state it on that single card and explain why.

Overloading Now. Ten items in Now means nothing is really a priority.

Using Later as a dumping ground. Later still needs owners for the review and an exit rule.

Feature lists without context. Cards without a problem statement invite arguments about solutions instead of needs.

Ignoring votes from the wrong audience. Votes are evidence, but weight them by customer segment. A popular request from free trial users and a blocker for paying teams are different signals.

When You Still Need Dates

Some audiences need dates: enterprise customers with contract commitments, partners planning a launch, or regulatory deadlines. Keep those dates on the specific items where the team can defend them, and keep the rest of the roadmap in horizons. Internally, the delivery plan can carry estimates; the public roadmap does not need to.

How RoadmapR Fits

RoadmapR helps SaaS teams publish a public roadmap with feature voting and a changelog. Teams can collect requests, let users vote, organize items by status, and show what shipped. It does not decide priorities for you: the horizons, evidence, and trade-offs still belong to the product team. If you are new to public boards, start with why public roadmaps build trust and the difference between a roadmap and a backlog, then compare RoadmapR plans.

FAQ

What is a Now-Next-Later roadmap?

It is a product roadmap that groups work into three horizons, Now, Next, and Later, instead of calendar dates. It communicates priorities and direction without implying delivery certainty the team does not have.

Who created the Now-Next-Later roadmap?

Janna Bastow, co-founder of ProdPad, created the format as an alternative to timeline roadmaps that encouraged deadline negotiations over product discovery.

Is a Now-Next-Later roadmap good for a public roadmap?

Yes. Customers mostly want to know what is being worked on, what is likely soon, and what is under consideration. Horizons answer those questions without exposing the team to missed dates.

How many items should be in Now?

Keep it small enough that every item has an owner and active work. For many small SaaS teams that means three to five items.

Does RoadmapR have a Now-Next-Later view?

No. RoadmapR uses Under Review, Planned, In Progress, and Completed statuses. Teams can map Later, Next, and Now onto Under Review, Planned, and In Progress respectively.

Should a Now-Next-Later roadmap include dates?

Usually not. Add a date only to individual items with a firm, defensible commitment, and explain the reason on that card.

Ready to build your public roadmap?

Roadmapr gives you a public roadmap, feature voting, and a changelog in one place. Start on the Free plan and upgrade when your team grows.

Get Started Free

Now-Next-Later Roadmap: A Practical Guide for SaaS Teams