A dated roadmap for something nine months out isn't more useful than Now/Next/Later — it's just more confidently wrong. Now/Next/Later replaces fake precision with an honest signal: how locked-in is this, really.
What each column actually commits to
"Now" is what the team is actively working on — committed, scoped, in progress. "Next" is what's coming after that — directionally decided, not yet fully scoped, still open to reordering if something urgent appears. "Later" is a direction, not a plan — things worth doing eventually that haven't been scoped at all and shouldn't be treated as promises to anyone.
The format prevents a specific kind of stakeholder argument
A dated roadmap invites the question "why did this date slip" even when the date was always a guess dressed up as a commitment. Now/Next/Later sidesteps that argument entirely, because nothing in "Next" or "Later" was ever presented as a date — there's nothing to have slipped. This doesn't make stakeholders happy about uncertainty, but it's an honest kind of uncertainty instead of a roadmap that quietly trains people to distrust every date on it.
"Next" needs a clear graduation rule into "Now"
Without a rule for promoting items from Next to Now, the column either never empties (a graveyard of good intentions) or moves arbitrarily by whoever pushes hardest. A simple rule — items move into Now only at sprint or cycle boundaries, and only after being scoped — keeps "Next" honest about what's actually about to happen versus what's just been sitting there.
Later isn't where ideas go to die — it's where they go to wait
The risk with a "Later" column is that it becomes a polite way to say no without saying no, and the team stops trusting that anything in it will ever move. Reviewing "Later" on a cadence — even just "does any of this still matter" — keeps it a real holding area instead of a place stakeholders learn to stop checking.