Quick Answer (TL;DR)
A Now-Next-Later roadmap organizes product work into three time horizons. Now, Next, and Later. Instead of fixed calendar dates. It gives teams the flexibility to adapt priorities as new information arrives while still communicating a clear strategic direction to stakeholders. This format is the preferred choice for agile teams that ship continuously and want to avoid the false precision of date-driven plans.
What Is a Now-Next-Later Roadmap?
A Now-Next-Later roadmap is a planning framework that groups initiatives into three commitment levels based on temporal proximity rather than specific dates. The "Now" column holds work that is actively in progress or about to start, "Next" contains validated priorities that will follow, and "Later" captures ideas and opportunities that need further research before the team commits. Unlike traditional Gantt-chart roadmaps, this format deliberately avoids assigning calendar dates, which reduces pressure to hit arbitrary deadlines and encourages honest conversations about what the team can realistically deliver.
The framework was popularized by Janna Bastow, co-founder of ProdPad, as a response to the problems created by date-driven roadmaps in product organizations. It has since become one of the most widely adopted roadmap formats in the agile community because it balances transparency with adaptability. Product managers use it to align engineering, design, and leadership around a shared set of priorities without creating the rigid contracts that traditional timelines impose.
When to Use a Now-Next-Later Roadmap
The Now-Next-Later format is ideal when your team operates in an environment of high uncertainty. If customer needs shift frequently, your market is evolving rapidly, or you are running a discovery-driven product process, locking work to specific dates creates more problems than it solves. This roadmap type acknowledges that certainty decreases as you look further into the future and structures the plan accordingly.
Early-stage startups benefit significantly from this format because their priorities can change week to week as they learn from user feedback and market signals. The framework lets founders communicate direction to investors and advisors without making delivery promises they cannot keep. It also works well for platform teams and internal tools groups where requirements emerge from multiple internal stakeholders on unpredictable timelines.
Teams that ship on a continuous deployment model. Rather than scheduled release trains. Will find the Now-Next-Later format aligns naturally with their workflow. For a side-by-side comparison of this approach versus date-driven formats, see Now-Next-Later vs. Timeline Roadmap. The absence of hard dates means the roadmap never becomes stale the moment a deadline passes; instead, it stays current as items flow from one horizon to the next based on evolving priorities.
Key Components
- Now column: Work actively in progress or starting within the current iteration. Items here carry the highest commitment level and should have defined scope, assigned owners, and clear acceptance criteria.
- Next column: Validated initiatives that the team has agreed to pursue after current work completes. Scope may still be evolving, but the strategic intent is firm.
- Later column: Ideas, opportunities, and strategic bets awaiting further research or validation. These carry the lowest commitment and may be promoted, deferred, or removed entirely.
- Confidence indicators: Tags such as High, Medium, or Low that communicate how certain the team is about each initiative, helping stakeholders calibrate expectations.
- Effort estimates: Lightweight sizing (t-shirt sizes or story points) that give reviewers a sense of the investment required for each item.
- Review cadence rules: Defined frequencies for reassessing each column. Typically weekly for Now, biweekly for Next, and monthly for Later. To keep the roadmap accurate and trustworthy.
How to Create a Now-Next-Later Roadmap
1. Collect All Candidate Initiatives
What to do: Gather every potential initiative from your product backlog, customer feedback channels, OKR discussions, sales requests, and technical debt logs into a single list.
Why it matters: Starting with a complete inventory prevents important work from being overlooked and sets the stage for honest prioritization rather than recency bias.
2. Prioritize Using a Scoring Framework
What to do: Apply a lightweight scoring model. Such as RICE (Reach, Impact, Confidence, Effort) or a simple Impact vs. Effort matrix. To rank each initiative objectively. The RICE Calculator can help you score each item consistently, and our guide to prioritization covers additional frameworks like MoSCoW and Weighted Scoring.
Why it matters: Scoring removes gut-feel decision-making and gives the team a shared language for debating trade-offs. It also creates an auditable rationale for why certain items were prioritized over others.
3. Assign Items to Horizons
What to do: Place the top-scored items into Now (respecting your team's capacity), the next tier into Next, and everything else into Later. If an item scores low across all dimensions, remove it from the roadmap entirely.
Why it matters: Explicit horizon placement forces the team to make real priority decisions rather than labeling everything as urgent. The Now column should contain no more than three to five items per team to signal genuine focus.
4. Enrich Cards with Context
What to do: Add a brief description, owner, effort estimate, confidence level, and any links to supporting research or customer evidence for each initiative card.
Why it matters: Context-rich cards reduce the need for follow-up meetings and allow anyone. From an engineer to a board member. To understand the rationale behind each priority.
5. Define Transition Rules
What to do: Document the criteria for moving items between columns. Specify who has decision authority, what evidence is required to promote an item from Later to Next, and what triggers a demotion.
Why it matters: Without explicit rules, the roadmap becomes a political battleground where the loudest voice wins. Clear governance keeps the process fair and repeatable.
6. Establish a Review Rhythm
What to do: Schedule recurring reviews. A weekly standup for Now, a biweekly planning session for Next, and a monthly strategy review for Later. Assign a facilitator for each.
Why it matters: A roadmap that is never reviewed decays into fiction. Regular cadence ensures the plan reflects current reality and builds organizational trust in the process.
Common Mistakes
- Overloading the Now column: Teams often put ten or more items in Now, turning it into a backlog rather than a focus signal.
Instead: Enforce a strict capacity limit of three to five items per team. If everything is a priority, nothing is.
- Treating Later as a graveyard: Items placed in Later are forgotten and never revisited, which wastes the effort spent capturing them.
Instead: Schedule a monthly review of the Later column. Promote items that have gained supporting evidence, and explicitly archive items that are no longer relevant.
- Adding dates under pressure: Stakeholders push for delivery dates, so the team quietly attaches timelines to each column, defeating the purpose of the framework.
Instead: Use approximate time ranges like "this quarter" or "this half" if executives need temporal anchoring, but resist specific dates on individual items.
- Skipping confidence levels: Without confidence tags, stakeholders assume every item is a firm commitment, leading to disappointment when Later items shift or disappear.
Instead: Always include a confidence indicator on every card and explain what each level means during roadmap reviews.
Best Practices
- Keep the Now column sacred. It should represent your team's actual capacity, not aspirational throughput. If the team cannot realistically deliver more than four initiatives in a cycle, do not put five in Now.
- Use the roadmap as a communication artifact, not just a planning tool. Share it broadly across the organization so that sales, support, marketing, and leadership all understand what the team is focused on and why.
- Link every initiative to a strategic objective. Each card in Now and Next should trace back to a company-level OKR or strategic theme. Our guide to creating OKRs covers how to write effective objectives and key results. This connection justifies the priority and helps stakeholders see how daily work ladders up to business outcomes.
- Pair with a detailed execution plan. The Now-Next-Later roadmap operates at the strategic level. Complement it with a Kanban board or sprint plan for tactical execution so that engineers have the granular tasks they need to deliver. For a presentation-ready version, grab the Now-Next-Later Roadmap PowerPoint template or follow our step-by-step guide to building a roadmap in PowerPoint.
Key Takeaways
- A Now-Next-Later roadmap replaces rigid date-based plans with a flexible, priority-driven framework that adapts to changing conditions.
- The Now column should be deliberately small. Three to five items. To signal genuine focus and protect the team from overcommitment.
- Confidence indicators and effort estimates on every card give stakeholders instant clarity on certainty and investment size.
- Establish a recurring review cadence (weekly, biweekly, monthly) for each horizon to keep the roadmap accurate and trustworthy.
- This format pairs well with Kanban boards for execution and portfolio roadmaps for multi-team visibility.