The now-next-later roadmap is having a moment again on LinkedIn. Two well-shared posts this fortnight list seven and eight product roadmap formats respectively, and in both comment threads the same argument plays out: the timeline roadmap promises dates it cannot keep, so teams switch to now-next-later, and then stakeholders ask the question the new format was designed to dodge. “Fine. When?”
This article answers that question for the people who actually have to ship the “now” column: release managers and delivery leads working in Jira. The short version is that now-next-later is the right format for intent and the wrong artifact for commitment, and that the fix is not to pick one format but to pair the roadmap with a release plan that carries a date and a confidence level together. If you are new to that distinction, start with our release planning guide and the shorter piece on roadmap vs release plan.
What the now-next-later roadmap fixes
A timeline roadmap draws a bar for every initiative against a calendar. It looks like a plan, so it gets read as one. Six months out, the bars are guesses dressed as dates, and every slipped bar spends credibility the team never meant to bet.
The now-next-later roadmap replaces the calendar with three buckets of decreasing certainty. “Now” is what the team is working on and confident about. “Next” is what is likely to follow, still being shaped. “Later” is direction, not commitment. The format is honest about uncertainty in a way a Gantt bar never is, which is exactly why product managers in those LinkedIn threads defend it so hard.
What it leaves out
Everything in the “now” column still has to land somewhere. A marketing launch, a regulatory deadline, a customer contract, a dependent team’s own release: these all consume a date, and “now” is not one. So the date gets negotiated in a side channel, written into a slide or a spreadsheet, and detached from the backlog it depends on. The roadmap stays clean. The commitment lives nowhere the team can see it move.
That is the failure mode the comment threads circle without naming. The format did not eliminate the date. It just stopped tracking it.
Pair the roadmap with a release plan that carries confidence
The pairing that works is simple to state. The now-next-later roadmap owns what and why. A release plan owns what, by when, and how sure we are. The “now” column maps to one or more releases; each release has a target date, the scope committed to it, and a confidence level that the team re-checks as sprints close.
- Roadmap column answers a stakeholder asking “is this a priority?”
- Release date answers “when will it ship?”
- Confidence level answers “how much should I plan around that date?”
Publish the date without the confidence level and you are back to the timeline roadmap’s false precision. Publish the confidence without a date and you are back to “now”. Both, together, is the only version stakeholders can plan against. Our piece on release date forecasting covers how the confidence number is derived from velocity and remaining scope rather than from optimism.
Doing this inside Jira
In practice the roadmap lives in a product tool or a Confluence page, and the release plan should live where the work is: in Jira, attached to the versions and epics that make up each release. Advanced Release Planning, Roadmaps & Management for Jira is built for the second half of this pairing. Each release carries a committed date and a confidence level side by side, the scope under it is the real Jira backlog rather than a copy, and the confidence is revisited as sprints close so a date that is quietly drifting shows up before the week it was due.
The workflow is short. Take the items in the “now” column and group them into releases. Give each release a target date and hold a confidence vote with the people who will do the work. Publish the date and the confidence together. When a sprint closes, re-check the confidence against what actually shipped, and renegotiate the date early if the number falls, rather than late when it is already missed. The roadmap format never has to change; the release plan underneath it is what keeps it honest.
The answer to “fine, when?”
“Now” means it is in an active release with a target date and a confidence level you can read. “Next” means it has been sized but not yet scheduled into a release. “Later” means it has neither. Stakeholders who get that answer stop asking for a timeline roadmap, because they have the part of it that was ever useful: a date with an honest error bar. For the wider method, see the complete release planning guide.
Leave a Reply
Your email is safe with us.