Organise work by confidence, not calendar dates. Now is in-sprint and specified; Next is validated with a rough plan; Later is directional intent — honest about what you don't yet know.
▸ Try the interactive toolThe Now-Next-Later roadmap organises product work into three confidence tiers instead of calendar dates. Now is what the team is actively building — spec'd, estimated, in sprint. Next is what follows — a validated problem, a clear approach, a rough estimate. Later is the strategic horizon — directional intent without commitment.
This structure is honest about a fact that date-based roadmaps hide: certainty decreases the further out you look. A Gantt chart promising a feature on a specific date eight months out is fiction dressed as a plan. Now-Next-Later communicates real confidence at each horizon, sets expectations stakeholders can trust, and avoids the credibility damage of missed date-based commitments — while still showing clear direction.
Now — actively building; spec'd, estimated, committed
Next — validated problem, clear approach, rough estimate
Later — strategic direction, no commitment to specifics or timing
Date-based roadmaps promise a precision that doesn't exist for distant work, then destroy trust when the dates inevitably slip.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| False date precision | A specific date eight months out is a guess presented as a promise. | Confidence tiers communicate honest certainty at each horizon. |
| Missed-commitment whiplash | Slipped dates erode stakeholder trust repeatedly. | No far-out dates to miss — trust is built on honest horizons. |
| Over-planning the uncertain | Detailed specs for distant work that will change anyway. | Later stays directional, so effort isn't wasted on specifics that will shift. |
| No visible direction | Pure backlog with no strategic horizon for stakeholders. | Later shows where the product is heading without over-committing. |
Place each item by how certain you are, not by a target date. In-sprint, specified work is Now; validated-but-not-started is Next; directional bets are Later.
Now should be genuinely in-progress and achievable. A bloated Now is just a wish list with a confident label — limit it to real current work.
Items earn their way into Next by having a validated problem and a clear approach. Promotion from Later to Next means discovery has reduced the uncertainty.
Resist the urge to spec Later items. State the strategic intent and the problem space; leave the solution open, because it will change before you get there.
The roadmap flows: as Now ships, Next moves up and Later items get validated into Next. It's a living tiering, not a fixed plan with deadlines.
A team maintained a date-based roadmap with features pinned to specific months up to a year out. Distant dates slipped repeatedly — not from poor execution but because the future was genuinely uncertain — and each slip eroded stakeholder trust a little more.
Switching to Now-Next-Later, they committed firmly to a small Now, showed a validated Next with rough estimates, and expressed Later as direction rather than dated promises. Stakeholders actually trusted it more: there were no far-out dates to miss, the direction was clear, and the honesty about uncertainty read as competence rather than vagueness.
The deliverable is work sorted into Now / Next / Later by confidence — committed near term, directional far term.
| Horizon | Confidence | What's shown |
|---|---|---|
| Now | High — in progress | Specific, estimated, committed work |
| Next | Medium — validated | Problem & approach clear, rough estimate |
| Later | Low — directional | Strategic intent, no dates or specs |
A roadmap is a communication tool, and its job is to convey honest confidence — not to manufacture a precision the future doesn't have. Now-Next-Later builds trust by admitting what date-based roadmaps pretend to know.
The discipline is resisting two temptations: bloating Now into a wish list, and over-specifying Later to look thorough. A small, truly-committed Now is what makes the roadmap credible; a deliberately vague Later is what keeps it honest. Counterintuitively, stakeholders trust a roadmap that openly says “we're not certain about the far horizon” more than one that promises specific distant dates — because the first is borne out and the second is repeatedly broken. The roadmap flows as a living tiering, not a contract of deadlines.
A huge Now is a wish list pretending to be committed work. Keep it to what's genuinely in progress.
Detailed plans for distant work waste effort and will change. Keep Later directional.
Adding “Later = Q4” reintroduces the false precision the format removes. Resist it.
The horizons should flow continuously as work ships and discovery progresses. Re-sort regularly.
The roadmap is the rung that turns product strategy (Tool 01) into sequenced work.
Now-Next-Later shows what; OKRs (Tool 26) show the outcomes that work should move.
What earns a place in Now and Next comes from prioritisation frameworks (RICE, MoSCoW) and discovery.
How you present the horizons to stakeholders is a communication skill covered in Module 6.
Take any roadmap or backlog you know. Sort the items into Now (in progress, certain), Next (validated, rough plan), and Later (directional only) — by confidence, not date.
Check your Now: is everything in it genuinely being worked on, or is it a wish list? Trim it to what's real.
If your honest “Now” is much smaller than your date-based roadmap implied, you've discovered how much false certainty the calendar was hiding — and why those distant dates kept slipping.