Skip to content
CoursesLog in
← Statistics glossary

Now-Next-Later roadmap

Also called: Now / Next / Later, Now Next Later roadmap

A roadmap format with three columns instead of dates: what the team is working on now, what comes next and what is planned for later, with certainty and detail decreasing from left to right.

A Now-Next-Later roadmap drops the calendar and sorts work into three columns:

  • Now: what the team is actively working on. Well understood, fairly detailed, high confidence.
  • Next: what comes after, once capacity frees up. The problem is clear; the solution is still open.
  • Later: important directions further out. Broad themes, little detail, most likely to change.

The format solves a classic roadmap problem: dates written months ahead become promises, and most of them slip. Columns still show sequence and priority, which is what most stakeholders really need, while leaving room to learn. They also make uncertainty visible without extra decoration: the further right, the less certain.

Now-Next-Later has become a common default for outcome-based roadmaps since the late 2010s. Product Roadmaps Relaunched (2017) still presents it as one option among quarters and half-years. Current practice adds a few conventions that make it work in real organizations:

  • Explicit horizons. Say roughly what each column means for your team, e.g. Now = this quarter, Next = the following one, Later = six months and beyond.
  • Confidence cues. A percentage per column, or a line in Now between commitments and stretch items.
  • Themes, not features, especially in Next and Later.
  • Regular review. Items move left as they become clear, and some drop out.

Quarter-based roadmaps remain useful where partners must plan ahead (hardware, enterprise contracts, regulated industries). The two can coexist: Now-Next-Later for the product, fixed external dates shown alongside.

Example

A Ukrainian HR SaaS for companies of 20–200 people:

  • Now (this quarter, ~80% confidence): Ensure managers approve time-off requests within a day. Mobile approvals in development; Slack reminders in testing.
  • Next (~50%): Ensure payroll accountants never retype data. Problem confirmed in 12 interviews; options include an import from accounting software or an API.
  • Later (~20%): Help companies with several legal entities manage them in one place. Early signals from sales; discovery needed.
  • External date: new reporting rules take effect on 1 January. Shown as a fixed event, not as a ship date.

Common mistakes

  • "Later" as a dumping ground. If every unwanted idea goes to Later, the column means nothing. Review it and delete freely.
  • No shared meaning for the columns. Without rough horizons, sales may read Next as "next month". Define them.
  • Detailed features in Later. Specific features far out imply a commitment. Keep them as problems.
  • Pretending there are no dates at all. Real deadlines (contracts, regulation, seasonal peaks) belong on the roadmap as fixed external events.
  • An overloaded Now. If Now holds ten items, nothing is really "now". Limit it to what the team can actually work on.

Learn it in the course