frameworkDelivery & agility

Now–Next–Later Roadmap

A roadmap format that groups priorities into three confidence horizons instead of assigning speculative dates to distant work.

Download Markdown (.md)

01What it means

A Now–Next–Later roadmap organizes product direction into three horizons. “Now” contains the most immediate, understood focus; “Next” contains likely subsequent priorities that still need learning; “Later” signals important possibilities with the least certainty. The columns express confidence and order, not equal time periods.[1][2]

Confidence horizons, not calendar buckets Commit most specifically to Now and preserve options toward Later
  1. 01NowImmediate, understood focus with ownership and evidence
  2. 02NextProbable priorities with unresolved questions
  3. 03LaterStrategic possibilities with least certainty

The columns express confidence and order, not equal durations; hard dates, dependencies, and forecasts need separate communication.

02Why it matters

Long-range dates often turn guesses into perceived commitments. This format communicates direction while making uncertainty visible, supports reprioritization as evidence arrives, and keeps discussion focused on why an initiative belongs in a horizon rather than on invented precision.

03When to use it

Use it for products in changing markets, continuous product development, or stakeholder conversations where strategic sequence matters more than a release calendar. Pair it with a delivery plan when contractual, regulatory, or operational dates genuinely require scheduling.

04How it works

  1. Define the outcomes, themes, or problems that qualify for roadmap inclusion.
  2. Place only actively investigated or delivered priorities in Now, with clear ownership and evidence.
  3. Put probable follow-on priorities in Next, noting the questions that must be resolved before promotion.
  4. Use Later for strategically relevant options, keeping descriptions broad enough to avoid premature solution commitment.
  5. Set explicit movement criteria and review the horizons on a regular cadence.
  6. Communicate separately any hard dates, dependencies, and delivery forecasts that the horizon view cannot represent.

05A practical example

Example

For an expense product, Now contains reducing failed receipt uploads, Next contains improving manager review speed, and Later contains cross-border reimbursement. When research reveals that approval policy—not interface speed—causes delays, the team changes the Next initiative without having to “miss” a fabricated date.

06Where it breaks

The labels can be vague unless teams define what qualifies for each horizon. Stakeholders may interpret Now as a delivery promise or Later as a quiet rejection. The format also hides capacity and dependency detail, so it should not replace release coordination or operational forecasting.

Common mistakes

  • Defining the columns as fixed calendar periods while claiming they are confidence horizons.
  • Filling Now with more work than teams can actively pursue.
  • Moving items mechanically instead of reassessing evidence and strategy.
  • Using Later as an unbounded parking lot for stakeholder requests.

07Sources

  1. Now, Next, Later Roadmap TemplateAha! · Product management template and guideNow, Next, Later Roadmap Template
  2. Introducing the Now, Next, Later RoadmapAha! · Product management articleIntroducing the Now, Next, Later Roadmap
View saved topics

Start typing to search titles, definitions, categories, and frameworks.