Now-Next-Later Roadmap Template: Build One This Month

What actually belongs in each horizon

The sorting rule is attention, not size. Now holds work someone is actively doing this week or this cycle: it has a named owner, a problem statement, and a definition of done. If two people are debating whether something is "basically started," it isn't in Now. Now should be short enough that you could list every item from memory.

Next is understood but unstarted. These items have a problem statement and usually a rough approach, but no one is working on them. The useful discipline is attaching a promotion trigger to each one — a customer commitment, a technical spike result, a dependency clearing. Without a trigger, Next quietly becomes a wish list that grows every month.

Later is the graveyard with dignity. It holds real ideas you've consciously deferred, each with a one-line reason. It is not a backlog of tickets and it is not where you hide things you're avoiding. If an item has sat in Later for several review cycles and nobody has asked about it, that's data: it probably belongs on the not-doing list.

• Now: named owner, active this week, clear definition of done
• Next: problem understood, promotion trigger written down
• Later: real idea, explicit reason for deferral
• Not doing: decided against, with the reason kept visible

The not-doing list is the template's real engine

Most roadmaps fail because they only record what's in. A Now-Next-Later template earns its keep by recording what's out — and why. The not-doing list is a short, visible set of items the team has decided against for now, each with a reason: too expensive, wrong customer segment, blocked by a dependency, or simply less valuable than the top of Next.

This list changes conversations. When a stakeholder asks for something you've already rejected, you point at the reason instead of relitigating from scratch. When the reason expires — the dependency clears, the customer segment becomes strategic — you have a documented trigger to revisit. That's far better than pretending the idea was never raised.

Keep the list to a handful of items and prune it quarterly. A not-doing list that grows to forty entries is just another backlog, and nobody reads it. The test: can you explain each rejection in one sentence without looking it up?

How to run the weekly review in 30 minutes

The weekly review is not a status standup. Its job is to keep the three columns true. Run it with a fixed agenda: what moved, what's new, what's stuck, and one risk. Anything that needs a status update belongs in a separate channel; if you spend the meeting describing progress, you've turned the roadmap into a report.

Start with movement. For each Now item, ask the owner two questions: is it still being worked on, and is the definition of done still right? If the answer to the first is no, it moves out of Now — either back to Next or onto the not-doing list. Then take new requests from a single intake point rather than discussing whatever arrived in Slack that morning.

Close with the changelog. One line per moved item, dated. This takes two minutes and is the single best artifact you'll have when an executive asks why the roadmap looks different from last month. It also stops the quiet drift where items appear in Now with no discussion.

• What moved since last week, and why
• Is every Now item still actively worked on
• New requests: intake, then sort — don't debate live
• Not-doing additions and expiry checks
• One risk or dependency to watch

Presenting to executives who want dates

Executives asking "when?" are usually asking two different questions: when will I see value, and can I trust this plan. Answer both without inventing dates. For each Now item, give a confidence statement tied to evidence — "in build, shipping this cycle" — and for Next, name the trigger rather than a month. "When the spike confirms the approach" is a real answer; "Q3" is a guess dressed as a commitment.

Lead with outcomes, not horizons. Nobody outside the team cares that something moved from Later to Next. They care which customer problem gets solved next and what you're explicitly not doing. Show the not-doing list in the first few slides. It signals that the roadmap is a set of tradeoffs made on purpose, which builds more trust than a busy timeline.

Expect the follow-up question about a specific date. Have one ready line: "I can give you a range once it's in Now and someone is working on it." Then offer the alternative — a monthly review where they see movement — so the ask for dates gets replaced by an ask for visibility. If dates are genuinely contractual, keep them in a separate delivery plan and don't contaminate the roadmap with them.

Filled example: a small SaaS team's map

A six-person B2B SaaS team adopting this template wrote the following. Now: add SSO login for two enterprise prospects; fix the onboarding email sequence that drops users before first value; rewrite the billing settings page. Three items, three owners, all active. Next: usage-based pricing experiment, self-serve trial without a demo call, admin audit log — each with a trigger like "after SSO ships" or "when the pricing spike is done."

Later: mobile app, a public API, a partner marketplace. Each has a one-line reason: capacity, no customer demand yet, and dependency on the API respectively. Not doing: a Slack integration (too expensive for the segment we're targeting), a free tier (would undercut the trial we're testing), and a redesign of the marketing site (different team, different quarter).

The map fits on one slide. In the weekly review, the team moved the trial change from Next to Now when the SSO work shipped, and added the free tier to not-doing after a pricing discussion. That's the whole system — three columns, a rejection list, and a thirty-minute meeting. For teams that want a visual version, Roadmap Creator turns a goal sentence into connected phase and step nodes and exports to PDF or a read-only link, which is faster than building the slide from scratch.

Tools that fit this template

A Now-Next-Later roadmap is simple enough to live almost anywhere, so pick the tool your stakeholders already open. Notion is the best fit if your team already documents there: three columns or three statuses, a properties view, and a page you can share. It's flexible but gives you no structure — you'll need to enforce the horizon definitions yourself. Trello or Linear boards work if the roadmap doubles as the work tracker, though Linear is built for issue tracking and will tempt you toward sprint detail the roadmap doesn't need.

For a board that is genuinely just a board, Miro or a slide in Google Slides or PowerPoint is fine; nothing beats a slide for executive review, and nothing is worse for maintaining over months. Aha! and Productboard are full product-management suites with idea portals, scoring, and stakeholder views — worth it if you need feedback intake and prioritization at scale, overkill if you need three columns and a meeting.

Roadmap Creator sits at the visual, no-dates end of that range: it turns a one-sentence goal plus a timeframe into an editable map of phases, steps, and milestones, with an AI Assistant on each node to break a step down. It's honest about limits — no real-time multiplayer editing, no team invites or comments, no dependency tracking, no dates or Gantt timeline, no Jira or GitHub integrations. If you need issue tracking or a feedback inbox, keep your existing tool and use this only for the shareable map.