How do I create a Now/Next/Later roadmap?

Expert answer on building a Now/Next/Later roadmap. Practical advice for product managers.

How to Create a Now/Next/Later Roadmap

A Now/Next/Later roadmap replaces fixed dates with confidence zones. "Now" is committed work for the current sprint or month. "Next" is planned work for the following 1-3 months. "Later" is exploratory work beyond that. The further out you go, the less specific items become.

Setting Up the Three Columns

Now (Committed): These are in-progress or about to start. Define them at the feature level with clear acceptance criteria. Your team has estimated these and agreed to deliver them. Include 3-5 items maximum.

Next (Planned): These are validated problems you intend to solve soon. Define them as outcomes or themes, not specific features. "Reduce onboarding drop-off by 20%" belongs here. Specific UI changes do not, because the solution might shift after discovery. Include 5-8 items.

Later (Exploring): These are opportunities worth investigating but not committed. Define them as problem statements or strategic bets. "Explore enterprise pricing model" or "Investigate API marketplace." Keep 5-10 items here as a pipeline.

The Key Principle

Specificity decreases as you move right. Now has tickets. Next has themes. Later has hypotheses. This is the whole point. You are communicating that certainty drops with time horizon, which is honest and prevents the false precision problem that plagues date-based roadmaps.

Use the roadmap templates collection to find a Now/Next/Later template that fits your team's style.

Building It in Practice

Start by dumping your backlog into three piles based on confidence level, not urgency. If you know exactly what to build and have validated demand, it goes in Now. If you know the problem but not the solution, it goes in Next. If you are still exploring whether the problem is worth solving, it goes in Later.

Score the Now and Next items using RICE or weighted scoring to rank within each column. Later items do not need scoring yet. They need validation.

Updating the Roadmap

Review weekly for Now, biweekly for Next, monthly for Later. Items flow left as they gain clarity: Later becomes Next when you validate the problem. Next becomes Now when you define the solution and estimate effort. Items also flow right or off the board entirely when priorities shift.

The roadmap building guide covers update cadences and stakeholder communication in detail.

Frequently Asked Questions

How do I handle executive pressure for specific dates on Later items?+

Reframe the conversation around confidence. "We are 90% confident on Now items, 60% on Next, and 20% on Later. Putting a date on Later items implies confidence we do not have." If they insist, give a quarter, not a date, and attach a confidence disclaimer.

Can Now/Next/Later work alongside sprint planning?+

Yes. The Now column feeds directly into sprint planning. Sprint items are a subset of Now. Next informs backlog grooming and discovery work. Later informs research spikes and customer interview topics.

How many items should be in each column?+

Now: 3-5 (committed capacity). Next: 5-8 (planned pipeline). Later: 5-10 (exploration backlog). If any column has more than 10 items, you are not making decisions. Ruthlessly cut or combine items.