The Now-Next-Later Roadmap: When Dates Hurt More Than They Help
By Sebastiaan Jansen · · 7 min read
A now next later roadmap sorts work by commitment: what the team is building now, what it picks up next, and what it might do later. It shows the work and how sure you are about it, and nothing unscoped gets a ship date. Use it when people need a shared direction and a calendar would pretend the finish line is already known.
Dates belong on real commitments, like a renewal, a compliance deadline, or a conference demo. Put a month on every idea just because the slide has a quarter column, and people read it as a promise. Teams then pad estimates, or explain slips, on dates that were never estimates.
When dates hurt more than they help
A date claims intent and a known finish. The intent can be real while the finish is a guess. Once the date is printed, sales quotes it, and the next meeting starts from it.
Calendar roadmaps get brittle in three cases.
- Discovery is still open, so a month freezes a design you have not chosen yet.
- A partner API, a legal review, or another squad's migration can slip by weeks.
- The backlog is bigger than the quarter, and a full column turns later ideas into fake commitments.
This week can have dates. Next quarter often should not. A product roadmap records choices, not every request, and horizons keep those choices visible as confidence drops. A fixed-scope delivery with a real end still needs a project roadmap with dates.
How to build a now next later roadmap
If Now holds more than this cycle can finish, it is a backlog with a friendlier name.
Now
Now is staffed: someone is on it, or it is the next ticket they pull. Name the outcome and why it is current, whether that's a blocked customer, a recurring incident, or a bet you agreed to test. "Cut failed invoice retries for annual plans" is a Now item. "Retry service v2" belongs on the ticket. Say "this cycle" while scope is stable, and hold off on a specific day until review unless it comes from outside the team.
Next
Next is ordered but unscheduled. It's what you would start when Now clears, in a sequence you can defend, without a design, estimate, or customer promise. Cap it at what one team could start in one or two cycles if Now emptied tomorrow. Anything further out goes in Later.
Later
Later has no owners, estimates, or months. Each item gets one sentence on why it matters and what would move it up: a metric, a segment, or a cleared dependency. If it sits two quarters with no new evidence, delete it.
| Column | Commitment | Time language that fits | What does not belong |
|---|---|---|---|
| Now | Staffed, in motion | This cycle, or a real external date | Unscoped ideas |
| Next | Ordered, not promised | After Now, no month | A quarter of pre-assigned dates |
| Later | Remembered, not queued | No date | Owners, estimates, customer promises |
A worked example
Northline is a fictional billing product. One squad owns invoicing, and leadership wants two quarters of plan. The lead will not date undesigned work.
Now. Stop same-day duplicate card charges; two engineers started on it Monday after a support spike. Show finance which invoices failed, and why, on the billing page.
Next, in order. Let admins exclude a tax region without filing a ticket. Shorten the month-end export so finance stops merging three files. Retry webhooks with a visible log, after the work that unblocks paying customers.
Later. Usage-based pricing, if sales brings three deals that cannot close on seats. Self-serve plan changes once the tax-region work is done. Multi-entity invoices stay listed, unsigned.
Sales may call Now in progress. Next has no date a contract can lean on, and Later is not a commitment. Only Now consumes the cycle, so pulling something from Later mid-cycle is an explicit swap.
Pair it with an outcome based roadmap
An outcome based roadmap names the behavior change and treats features as options. Horizons say how committed you are; outcomes say what the row means. A row should be something you could miss. "Improve billing" cannot fail in a way you would notice. "Cut same-day duplicate charges to rare exceptions, and show the reason on the invoice" can.
The approach can change (a filter, say, or a daily email) without redrawing the row. The row stays until the outcome is met or dropped. "Platform modernization" soaks up side projects, while "a new engineer ships a small billing change in week one without a pairing marathon" knocks half of them off. A goal with nothing in Now is a slogan. A Now item with no goal is local work you should defend out loud.
Keep the columns tied to the work
Link each Now item, and each Next item once it gets close, to the tickets that would deliver it. If the slide and the board disagree, trust the board and fix the slide that day. A cycle gives Now a start, an end, and a rule for leftovers. If the duplicate-charge work misses the cycle, say why in one sentence, then keep the row or swap it. Nothing rolls over silently.
Falrow keeps that link with a roadmap counted from tickets and cycles with reviewed rollover, but the same rule works in other trackers. If a tool lets someone put a month on an unscoped epic, someone will. Jira roadmaps can draw bars that fill the quarter. Keep dates on Now and on real external deadlines, and leave Next and Later undated.
Agile roadmaps plan ahead without treating the plan as knowledge, and three horizons are the short form of that. They fit poorly when a buyer will only sign if every milestone has a day. In that case, use a project plan with a schedule, buffers, and a change rule.
What you show, and what you refuse
Keep one list. Internally it has columns, outcome text, an owner on Now only, and ticket links. Externally you show the same rows, trimmed: Now in plain language, Next as intent, Later for direction only and never with a quarter. Sales does not keep a second list.
Refuse three asks. If someone wants a month on Next so the slide looks finished, give them the order. Adding to Now without removing anything ignores staffed capacity. When a loud customer wants an item moved, write down what breaks if it waits a cycle.
Review it once a cycle
The review takes thirty to forty-five minutes.
- Close shipped Now items. Mark each outcome met, partly met, or not met.
- Decide whether rollover stays, shrinks, or gets swapped.
- Pull from the top of Next until Now matches capacity. If you want to skip the top item, reorder Next first.
- Scan Later. Promote one item or delete stale ones, but don't promote by default.
Between reviews, change facts only: a ship, a split, or a date that a contract or regulator created. Weekly status is a note on Now. Reordering every week teaches people to hide work. Estimate near Now, not in Later. Product roadmap examples differ by audience, with columns where false precision gets punished and a timeline where the date is an outside constraint.
How it goes stale
Now swells into a quarter, Next into a year, and Later into every old idea. Cut until Now fits the cycle, and put the outcome in the title. "Q3" on a Later item is a date. An owner on Later implies a schedule. Split a blended board by team so each squad sees its own Now.
You should be able to read a row in one breath: outcome, column, and why it sits there. Each review should change the board because something shipped or someone made a swap on purpose.
FAQ
What is a now next later roadmap?
It's three columns matched to certainty. Now is the current cycle. Next is the ordered set you draw from when capacity frees up, with no ship date. Later is direction you are not scheduling.
How is this different from a feature list?
A feature list names what you will build. An outcome row names the change, such as fewer duplicate charges or a shorter month-end close, so tickets can change approach without a redraw.
When should the board include dates?
Date a Now item when scope is stable, or when a contract or compliance deadline sets the day. Leave Next and Later undated. If someone needs a month before they can plan, scope the work and reserve capacity, or tell them you will not promise it.
How often should you update it?
Update facts as they happen: a ship, a split, an external date. Reorder and promote in the cycle review, the same meeting that decides rollover. A weekly rebuild usually means the columns were never tied to the tickets.