The Now-Next-Later Roadmap: A Simpler Way to Plan Product

A Now-Next-Later roadmap organizes product work into three time horizons — Now (in progress), Next (up soon), and Later (under consideration) — instead of pinning features to specific dates. It trades false precision for honest flexibility: near-term work is specific and committed, while later work stays deliberately fuzzy. Popularized by ProdPad co-founder Janna Bastow, the format has become the default for modern, outcome-driven product teams. The hardest question it raises is not how to draw the columns but what earns a place in each one — and that is a research question. Tools like Koji answer it by turning continuous customer interviews into the evidence that decides what moves from Later to Now.

This guide explains the three horizons, how to build and run the roadmap, what belongs in each column, and how to populate it with customer evidence instead of opinion.

Why date-based roadmaps fail

The classic Gantt-style roadmap — features stacked against quarters and months — looks reassuring and is almost always wrong. It implies a confidence about the future that no product team actually has. The problems are predictable:

• Dates become promises. Stakeholders treat a Q3 estimate as a contract, and every slip erodes trust.
• It rewards output, not outcomes. A timeline measures whether you shipped, not whether anything improved for customers.
• It resists learning. When research reveals a better bet, a date-locked roadmap makes changing course feel like failure.

The Now-Next-Later format fixes this by matching certainty to time. You know a lot about this month and very little about next year, so your roadmap should say a lot about the first and stay vague about the second.

The three horizons

Now — what the team is actively building. These items are well-defined, scoped, and tied to a clear problem or outcome. Confidence is high because the work is in flight. Keep this column short; a focused team has only a few things in "Now."

Next — what comes after the current work. These items are validated enough to believe in but not yet fully scoped. You know the problem is real; you are still shaping the solution. "Next" is your near-term intent, not a commitment to dates.

Later — ideas and problems worth considering but not yet validated. This is where opportunities live before they earn investment. Items here are intentionally loose — often framed as problems or opportunities rather than features — and many will never graduate. That is the point: "Later" is a holding area for bets you have not yet justified.

The flow of the roadmap is the flow of evidence: an idea enters Later, accumulates research support, gets validated into Next, and is committed into Now.

How to build a Now-Next-Later roadmap

1. Anchor each column to outcomes, not features

Frame items as the problem to solve or the outcome to move ("reduce onboarding drop-off"), not the feature to ship ("add a setup wizard"). This keeps the team focused on impact and leaves room to discover the best solution.

2. Keep "Now" ruthlessly short

A team that has eight things in "Now" has nothing in "Now." Limit work in progress so the column reflects reality.

3. Make movement evidence-based

The discipline of the format is the promotion rule: nothing moves from Later to Next, or Next to Now, without evidence that it is worth it. This is where most roadmaps quietly fall back into opinion — and where research becomes the engine.

4. Review on a cadence

Revisit the board every sprint or month. Promote what new evidence supports, demote what has gone cold, and retire ideas that research has invalidated. The roadmap is a living document, not an annual artifact.

What earns a slot: research, not loudest opinion

The weakness of any roadmap is that columns fill with whoever argued hardest. Now-Next-Later only works if movement between horizons is earned with customer evidence. That means a continuous stream of insight feeding the board — exactly the problem AI interviews solve.

With Koji, you run always-on customer research that keeps the roadmap honest:

• Discover problems for "Later" — continuous interviews surface unmet needs and friction you didn't know to ask about, populating the opportunity column with real demand.
• Validate before "Next" — before promoting an idea, send an AI interviewer to test it with the people who'd use it. Koji runs voice or text conversations 24/7, probes each answer with follow-ups, and analyzes every transcript automatically.
• Confirm impact after "Now" — once something ships, interview users to check the outcome actually moved.

Because the interviews are automated and continuous, the evidence layer keeps pace with the roadmap instead of lagging a quarter behind.

Structured questions to score what moves

When you are deciding what graduates from Later to Next, mix narrative with countable signal. Koji's six structured question types make demand measurable:

• open_ended — the unmet need in the customer's words, with AI probing
• scale — how severe the problem is, or how valuable a proposed solution would be
• single_choice — which of several problems hurts most
• multiple_choice — which scenarios trigger the need
• ranking — order competing opportunities by importance
• yes_no — would they use the proposed solution at all

That gives you both a demand score and the verbatim reasons, so promotion decisions rest on evidence rather than the loudest voice in the room. See the structured questions guide to design them, and pair this with a weighted scoring model when you need to rank several validated candidates.

Communicating the roadmap to stakeholders

Now-Next-Later is also a stakeholder-management tool. When an executive asks "when will X ship?", the honest answer is often "it's in Later — here's the evidence we'd need to see to promote it." That reframes the conversation from dates to confidence, and invites stakeholders into the prioritization logic instead of holding you to a guess. Pair the board with the research behind each item and the roadmap sells itself.

Common mistakes

• Turning Later into a graveyard — if nothing ever graduates, the column is just a backlog. Review and prune it.
• Over-specifying Later — detailed specs for unvalidated ideas waste effort and create false commitment.
• Promoting on opinion — without evidence-based movement, the format is just three colored columns.
• Letting "Now" sprawl — too much in progress means nothing actually gets finished.
• Treating it as static — the value is in the regular, evidence-driven review.

A worked example

Imagine a Now-Next-Later board for a B2B analytics product. Now holds "cut time-to-first-dashboard" — in active development, scoped, tied to an activation metric. Next holds "shared team workspaces," validated through a dozen AI interviews where teams described workarounds for collaboration but not yet fully designed. Later holds a loose cluster: "Slack alerts," "white-label reports," "mobile view" — ideas raised by sales and support that nobody has tested. Over the next month, continuous interviews reveal that white-label reporting is a repeated dealbreaker in lost deals, so it accumulates enough evidence to graduate into Next, while "mobile view" goes cold and is demoted. Nothing moved because someone argued for it; each promotion was earned by customer evidence. That is the format working as intended — a roadmap that updates itself as the research stream brings new signal in.

Related Resources

• Structured Questions Guide — score opportunities with the six question types
• Research-Driven Roadmap Prioritization — the prioritization methods that decide what moves
• Weighted Scoring Model — rank validated candidates objectively
• Kano Model — classify features by how they affect satisfaction
• Continuous Discovery & User Research — keep the evidence stream feeding the board
• Impact Mapping Guide — connect roadmap items to business outcomes