The Now-Next-Later Roadmap, Explained

The now-next-later roadmap is the most useful format most teams have never formally adopted. It replaces a grid of dates with three simple buckets, and in doing so it solves the problem that breaks every timeline-based roadmap: false precision.

What the three horizons mean

The format sorts every item into one of three columns, ordered by how confident you are and how soon you will start.

• Now. Work that is committed and actively underway. You know what it is, why it matters, and roughly when it lands. This is the only horizon where specifics are safe.
• Next. Work that is planned and likely, but not yet started. The shape is clear, the timing is not. Items here can still be reordered or dropped as evidence changes.
• Later. Directional bets. Problems you intend to solve eventually, described loosely. No commitment to scope or sequence. This is where ambition lives without becoming a promise.

The genius of the format is that confidence and time move together. An item drifts from later to next to now as you learn more, and the roadmap stays honest at every step.

Why dates make roadmaps lie

A dated roadmap forces you to assign a calendar slot to work you barely understand. You guess, the guess gets quoted back to you, and you spend the next quarter managing disappointment. Now-next-later sidesteps this by communicating timing in relative terms. Nobody can hold you to a date you never gave.

This does not mean you abandon planning. Inside the now column you can still track sprints and rough delivery windows. The horizons just stop you from broadcasting precision you do not have to people who will treat it as a contract.

Keeping each horizon honest

The format only works if you respect the boundaries. Two failure modes are common. The first is stuffing the now column with more than the team can deliver, which turns a confidence signal into noise. The second is letting later become a graveyard where ideas go to be forgotten. Prune it. If something has sat in later for a year with no movement, it is not a plan, it is a wish.

Feed the horizons with evidence. Items earn their way from later toward now as customer demand, revenue weight, and feasibility become clearer. Pulling from a scored product backlog keeps the promotion decisions grounded rather than political. Our product roadmap software is built around exactly these horizons.

Sharing it with customers

Now-next-later translates cleanly into a public roadmap. Customers understand the difference between committed and directional without a legend. They see that now is real, next is likely, and later is a maybe, and they calibrate their expectations accordingly. A public roadmap in this shape sets honest expectations by default.

When an item moves between horizons or ships, the people who asked for it should hear about it. Kithspark sends those lifecycle notifications automatically, so promotion from next to now becomes a moment of contact rather than a silent edit.