Now-Next-Later Roadmap: How to Build One

7 min read · 2026-10-08

Answer: A now-next-later roadmap organizes work into three time horizons—Now, Next, Later—without committing to specific release dates. Now covers active, committed work. Next covers the problems you will tackle after Now. Later captures direction and options. It is an outcome-oriented roadmap, not a Gantt chart.

This guide covers the definition, a step-by-step build process, a worked example, tool choices, and how to measure progress. You will also see how to socialize the roadmap and avoid common mistakes.

The roadmap at a glance

Goal: Build and operate a now-next-later roadmap that aligns stakeholders on outcomes and adapts as evidence changes. Duration: 6 to 8 weeks

  1. Set Outcomes and Constraints (Week 1)

    Define the measurable outcomes the roadmap must serve before discussing features.

    • Write three to five product outcomes using OKR format.
    • List business constraints such as budget, compliance, and headcount.
    • Interview two to three customers about current pain points.
    • Review last quarter's delivery data and support themes.
    • Agree on one primary outcome for the next cycle.

    Milestone: A one-page outcome brief signed off by product, engineering, and design.

  2. Collect and Shape Opportunities (Weeks 2-3)

    Turn raw requests, data, and discovery notes into opportunity statements.

    • Cluster feedback from support, sales, and user research into themes.
    • Write opportunity statements in the form: user needs a way to...
    • Map each opportunity to an outcome using an opportunity solution tree.
    • Score opportunities with RICE or weighted shortest job first.
    • Park out-of-scope ideas in a parking lot for Later.

    Milestone: A prioritized opportunity backlog with clear links to outcomes.

  3. Draft the Three Horizons (Weeks 3-4)

    Place opportunities into Now, Next, and Later based on evidence and capacity.

    • Estimate team capacity for the Now horizon using historical velocity.
    • Select Now items that are validated, urgent, and resourced.
    • Place medium-confidence items in Next with a trigger condition.
    • List speculative bets and strategic options in Later.
    • Write a one-line rationale for every item's horizon.

    Milestone: A one-page now-next-later roadmap reviewed by the product trio.

  4. Pressure-Test and Communicate (Weeks 5-6)

    Challenge assumptions and align stakeholders without overcommitting.

    • Run a pre-mortem to identify what could make Now fail.
    • Check each Now item against the primary outcome.
    • Present the roadmap to sales, support, and leadership for feedback.
    • Replace date commitments with horizon language and evidence notes.
    • Publish the roadmap in a shared tool with a changelog.

    Milestone: Stakeholder sign-off on horizons and a shared definition of Now.

  5. Operate and Refresh (Weeks 7-8 and ongoing)

    Establish a cadence to move items between horizons as evidence changes.

    • Review Now progress in weekly product trio stand-ups.
    • Revisit Next and Later every four to six weeks.
    • Promote items from Next to Now only when capacity opens.
    • Demote or delete items when evidence invalidates them.
    • Share a monthly roadmap changelog with stakeholders.

    Milestone: A living roadmap that changes at least once per quarter with clear reasons.

How Now-Next-Later Differs from a Timeline Roadmap

Timeline roadmaps promise specific features on specific dates. They force teams to estimate before discovery and turn assumptions into commitments. A now-next-later roadmap replaces dates with horizons of confidence. Now means the team is actively working on it. Next means the problem is likely next, but the solution may change. Later means the direction is plausible, but evidence is thin. This keeps the conversation on outcomes and learning.

Use horizon language in every stakeholder conversation. Instead of saying Q3, say Now or Next. When someone asks for a date, explain the trigger that moves an item from Next to Now. That trigger could be a discovery finding, a capacity opening, or a compliance deadline. The roadmap becomes a communication tool, not a contract.

  • Now: validated problem, resourced team, active work.
  • Next: clear problem, likely timing, solution still flexible.
  • Later: strategic direction, low confidence, no capacity yet.
  • Replace dates with triggers and evidence notes.

How to Choose What Goes in Now

Now is the most expensive horizon because it consumes real capacity. Only place work in Now when three conditions are true. First, the problem is validated by research or data. Second, the team has the skills and time to solve it. Third, the outcome is agreed with leadership. If any condition is missing, the item belongs in Next.

Use a simple filter. Write each candidate as an opportunity statement: a user needs a way to achieve a result. Then score it with RICE (reach, impact, confidence, effort) or weighted shortest job first (WSJF). Compare the score to your primary outcome. Pick the smallest set of items that can move that outcome. Leave everything else in Next or Later.

  • Validate the problem before estimating the solution.
  • Confirm capacity with engineering and design.
  • Tie each Now item to one primary outcome.
  • Limit Now to two or three major items.

Tools and Artifacts That Support the Method

You can run a now-next-later roadmap in many tools. Productboard, Aha!, and Roadmunk offer horizon views with scoring. Jira and Linear track the delivery work behind Now. Notion and Confluence host the narrative and decision log. Miro and Figma help teams map opportunities and sketch solutions. The tool matters less than the artifact: a one-page roadmap with three columns and a rationale for each item.

Keep a decision log next to the roadmap. Record why an item moved between horizons, what evidence triggered the change, and who approved it. Use a simple table in Notion or a Confluence page. This log prevents re-litigating old decisions and helps new stakeholders understand the reasoning.

  • Productboard, Aha!, Roadmunk for horizon views.
  • Jira, Linear for Now delivery tracking.
  • Notion, Confluence for narrative and decision logs.
  • Miro, Figma for opportunity mapping.

How to Practice and Socialize the Roadmap

Socialize the roadmap before you finalize it. Walk through the three horizons with sales, support, marketing, and leadership. Ask what they would need to see to move an item from Next to Now. Capture their concerns and add them as risks or triggers. This turns the roadmap from a product document into a shared plan.

Run a monthly roadmap review. Spend ten minutes on Now progress, ten on Next triggers, and ten on Later assumptions. Invite one stakeholder from a different function each time. Keep the meeting focused on evidence, not opinions. Publish the updated roadmap and changelog in a central place.

  • Present the roadmap as a story: outcome, opportunity, horizon.
  • Ask stakeholders for triggers, not dates.
  • Share a changelog after every update.
  • Use the roadmap in sprint reviews and quarterly planning.

How to Measure Progress and Adapt

Measure the roadmap by outcome progress, not feature delivery. Track leading indicators such as discovery interviews completed, experiments run, and assumptions validated. Track lagging indicators such as activation, retention, or revenue tied to the primary outcome. If the outcome is not moving, change the work in Now.

Review horizon health every four to six weeks. Ask: How many Now items are still tied to the primary outcome? How many Next items have a clear trigger? How many Later items are still relevant? Delete items that no longer serve the strategy. A healthy roadmap shrinks as often as it grows.

  • Track outcome metrics weekly, not just output.
  • Count validated assumptions, not story points.
  • Review horizon health every four to six weeks.
  • Delete Later items that lose strategic fit.

Common mistakes to avoid

  • Treating Now as a fixed release date; fix by defining Now as the current focus with a clear outcome and a review cadence.
  • Filling Later with vague wishes; fix by writing Later as strategic options with a trigger or hypothesis.
  • Letting the loudest stakeholder dictate Next; fix by scoring opportunities against outcomes and capacity.
  • Skipping outcome definitions; fix by writing OKRs before placing any feature.
  • Publishing the roadmap once and never updating it; fix by scheduling a monthly horizon review.
  • Using the roadmap as a sales promise; fix by training sales on horizon language and evidence notes.

Frequently asked questions

What is a now-next-later roadmap?

A now-next-later roadmap is a product planning artifact that groups work into three horizons: Now, Next, and Later. Now contains validated, resourced problems the team is actively solving. Next contains problems likely to be tackled after Now, with flexible solutions. Later contains strategic options and direction. It replaces date-based commitments with confidence levels, so teams can learn and adapt without breaking promises.

How is it different from a Gantt chart?

A Gantt chart shows tasks on a timeline with start and end dates. A now-next-later roadmap shows relative priority and confidence. Gantt charts assume you know the solution and duration upfront. Now-next-later assumes you need discovery. Use a Gantt chart for execution planning inside Now. Use the horizon roadmap for strategic planning across quarters.

How often should I update a now-next-later roadmap?

Review Now weekly in the product trio. Revisit Next and Later every four to six weeks. Update the roadmap whenever a trigger condition changes or new evidence invalidates an assumption. Share a changelog monthly with stakeholders. The goal is a living document, not a quarterly artifact.

What tools work best for now-next-later roadmaps?

Use a tool that supports horizon views and scoring. Productboard, Aha!, and Roadmunk are built for this. Jira or Linear track Now delivery. Notion or Confluence hold the narrative and decision log. Miro or Figma help map opportunities. Many teams start with a simple spreadsheet or Notion board. The tool matters less than the discipline of updating horizons.

How do I handle stakeholder requests for dates?

Replace dates with triggers. Say: This is in Next. It moves to Now when we validate the problem and free capacity. If a date is truly fixed, such as a compliance deadline, place it in Now and explain the trade-offs. Offer to share the discovery plan and the trigger conditions. Most stakeholders accept horizon language when you show the evidence behind it.

Generate this roadmap with AI