Now-next-later roadmap

The Now-Next-Later roadmap is a strategic planning format that organizes product initiatives into three time-based horizons without committing to specific dates. "Now" shows what's currently in progress, "Next" shows what's planned to follow, and "Later" shows longer-term intentions. This approach provides strategic direction while embracing the uncertainty inherent in product development.

Why it matters

Traditional date-based roadmaps create a problem: they promise more precision than planning allows. When you commit a feature to "Q3," you're betting on estimates, priorities, and resources that will inevitably change. When dates slip - as they always do - stakeholders lose trust and product teams spend energy explaining what changed rather than building products.

The Now-Next-Later format acknowledges uncertainty while still communicating priorities. Stakeholders understand what's most important and approximately when things might happen, without the false precision that leads to disappointment. Teams can adapt to learning and changing circumstances without "breaking promises."

For product managers, this format reduces roadmap maintenance overhead. Instead of constantly adjusting dates across a timeline, you adjust items between buckets as priorities evolve. The conversation shifts from "when exactly will this ship?" to "what's most important right now?"

The three horizons

Each horizon represents a different level of commitment and detail.

Now. Work currently in active development. These items are well-understood, scoped, and have assigned resources. Commitment is high - barring significant disruption, these will be delivered. The Now horizon typically spans the current sprint or development cycle.

Next. Work planned for the near future. These items are prioritized and reasonably well-defined but not yet in active development. They'll move to Now when current work completes. Commitment is moderate - priorities could shift, but these are likely. Next typically represents 1-3 months ahead.

Later. Work intended for the future but not yet fully planned. These items represent strategic direction without detailed commitment. They'll be refined and potentially reprioritized as they get closer to execution. Commitment is low - these may change significantly. Later represents anything beyond the Next horizon.

Benefits of the format

The Now-Next-Later approach offers several advantages.

Honest communication. The format explicitly acknowledges that distant plans are less certain than immediate ones. This honesty builds trust with stakeholders who appreciate not being misled.

Reduced planning overhead. Without specific dates, there's no need for detailed estimation and scheduling of work months away. Planning effort goes where it matters - the near term.

Flexibility. When priorities change or new information emerges, items move between horizons without triggering cascading date changes across the roadmap.

Appropriate detail levels. Now items are detailed because they need to be for execution. Later items are sketches because detail would be premature. The format encourages appropriate investment.

Alignment on priorities. The format makes clear what's most important (Now), what's next most important (Next), and what's on the radar (Later). This priority ordering helps teams and stakeholders make trade-off decisions.

Creating a now-next-later roadmap

Building an effective roadmap requires thoughtful curation.

Start with strategy. The roadmap should reflect strategic priorities. What problems are you solving? What outcomes are you targeting? Items should connect to strategic goals, not just represent a feature wish list.

Size items appropriately. Roadmap items should be meaningful initiatives, not individual tasks. They might be epics, themes, or outcomes - large enough to represent real progress but small enough to fit within a horizon.

Limit the Now horizon. How much can your team realistically work on simultaneously? That's your Now capacity. Trying to have too much in Now dilutes focus.

Be selective about Later. Not every idea belongs on the roadmap. Later should show strategic intent, not every possibility. A cluttered Later horizon is as useless as an empty one.

Connect to outcomes. Where possible, frame roadmap items in terms of outcomes ("improve onboarding conversion") rather than outputs ("build new onboarding wizard"). This preserves flexibility in how you achieve goals.

Presenting to stakeholders

How you present the roadmap matters as much as its content.

Explain the format. Not everyone is familiar with Now-Next-Later. Explain what each horizon means and what level of commitment it represents.

Set expectations about changes. Later items will change. Some Next items will too. Prepare stakeholders for this reality so they're not surprised when it happens.

Share the "why." Don't just list items - explain why they're prioritized where they are. What problem does this solve? What outcome does it drive? Context helps stakeholders understand and support priorities.

Show movement. Over time, show how items have progressed from Later to Next to Now. This demonstrates progress and builds confidence in the planning process.

Invite discussion on trade-offs. If a stakeholder wants something moved up, discuss what would move down. The roadmap is constrained by capacity - something has to give.

Common variations

Teams adapt the format to their needs.

Adding outcomes. Some roadmaps show the expected outcome or benefit for each item, making the "why" explicit.

Adding themes or goals. Grouping items under strategic themes or objectives shows how individual initiatives connect to larger goals.

Adding confidence levels. Some teams indicate confidence for each item - high confidence for Now, medium for Next, low for Later - making uncertainty explicit.

Adding swimlanes. Horizontal swimlanes might separate different product areas, teams, or customer segments while maintaining the time horizon structure.

Adding an Exploring column. Some teams add a fourth column for ideas under investigation but not yet planned - earlier in the pipeline than Later.

When dates are necessary

Sometimes stakeholders legitimately need dates - for marketing campaigns, sales commitments, compliance deadlines, or partner coordination. The Now-Next-Later format can accommodate this.

Attach dates to specific items. "The enterprise SSO feature (currently in Next) is targeted for March to support the compliance deadline." The date applies to one item, not the whole roadmap.

Maintain the format for everything else. Most items don't need dates. Use the time-horizon format as the default, with dates as exceptions.

Communicate date confidence. A date for something in Now is more reliable than a date for something in Next. Make this uncertainty explicit when sharing date targets.

Common mistakes

Several patterns undermine Now-Next-Later roadmaps.

Too much in Now. If Now is overwhelming, focus is lost. Limit Now to what's actually in progress.

Stale roadmaps. The roadmap should be a living document, updated as circumstances change. A roadmap that hasn't changed in months isn't being used.

No strategic connection. A roadmap of features without connection to strategy is just a feature list. Items should link to outcomes and objectives.

Treating Later as a dumping ground. Later should show strategic intent, not every idea ever suggested. Be willing to remove items that won't realistically be prioritized.

Hiding uncertainty. The format's value is honest acknowledgment of uncertainty. If you present it like a timeline with dates, you've lost the benefit.

Evolution and review

Roadmaps need regular maintenance.

Review cadence. Most teams review roadmaps quarterly or monthly. The rhythm should match your planning cycles.

Movement assessment. Has work progressed as expected? Have items moved from Next to Now, Later to Next? If nothing moves, something's wrong.

Priority reassessment. Have priorities changed based on what you've learned? Should items move between horizons or be removed entirely?

Stakeholder feedback. Are stakeholders getting value from the roadmap? Do they understand the format? What questions does it leave unanswered?

The Now-Next-Later roadmap is a tool for alignment and communication, not a contract for delivery. Used well, it enables productive conversations about priorities while acknowledging that the future is inherently uncertain. Tools like Klero help connect customer feedback to roadmap priorities, ensuring that what moves to "Now" reflects real customer needs rather than internal assumptions.