Product Roadmap Template: The Now/Next/Later One-Pager

What belongs on the one-pager and what belongs in Jira or Linear

The one-pager answers two questions: why this quarter matters and what change each theme should produce. Jira or Linear answers a different question: which ticket is someone working on today. Keep those layers separate and both stay readable. Each template row carries a theme, an outcome written as a change in customer or business behavior, an owner named by role, a status of Now, Next, or Later, and a confidence level. That is the whole schema — resist adding to it.

Anything with a due date, an estimate, or a reviewer belongs in the tracker. Epics, acceptance criteria, sprint assignments, defect backlogs, and dependency chains live one layer down, linked from the row if you need the thread. The one-pager also needs a visible Not Doing list; a roadmap that only shows what you said yes to invites the same three questions every week. Add a last-updated date in the footer so nobody argues with a stale version.

• Keep on the one-pager: theme, outcome, owner by role, horizon, confidence, Not Doing list, last-updated date.
• Move to Jira or Linear: epics and tickets, acceptance criteria, estimates, sprint assignment, defect queues.
• Move to a linked doc: research notes, competitive teardowns, pricing decisions, decision logs.
• Leave off entirely: individual names on tasks, hour estimates, dependency arrows, and vague placeholders with no stated outcome.

The 90-minute session, minute by minute

Book 90 minutes with three people: the product manager, the design lead, and the engineering lead. Everyone else reacts to the draft afterward. One laptop, one screen, no side threads. The purpose is commitment, not collaboration theater.

Spend the first 10 minutes restating the quarter's goal and who reads this page. Use minutes 10 to 25 to review what actually shipped against the previous version — this is where honesty gets calibrated. From minute 25 to 55, commit Now and nothing else, capping it at two or three themes. Sketch Next until minute 75, rough out Later plus the Not Doing list, then finish with a read-aloud test: someone reads the page cold and explains it back.

If a blank template is the reason the meeting keeps slipping, generate a first draft before you walk in. Roadmap Creator turns a one-sentence goal plus a timeframe into an editable visual roadmap with phases, steps, and milestones — useful as a straw man to argue with rather than a beautiful page nobody questions.

• Cap Now at three themes; the cap is the whole discipline.
• Write outcomes in the present tense so they are testable.
• Name owners by role when the person is not yet decided.
• Record every question the read-aloud test surfaces and fix the row, not the reader.

How to keep it from becoming a Gantt chart

A Gantt chart is a promise about sequence and duration. A Now/Next/Later roadmap is a statement of priority and intent. The two get confused the moment you add dates, bars, or columns that look equally wide for unequal work. Once a date is on the page, someone will treat it as a commitment, and every slip becomes a renegotiation instead of a reprioritization.

The fix is structural, not cultural. Use three columns of equal width, write every item as an outcome, and put the quarter's goal in the top row where a schedule header would normally sit. Publish a written change rule so movement is expected rather than negotiated: Now changes when something ships or when a deal or a support escalation proves the priority wrong.

Pick a tool that does not tempt you. Roadmap Creator deliberately has no dates or Gantt timeline — a roadmap there is a connected map of phases, steps, and milestones, which makes date-shaped promises awkward to add. It also has no dependency tracking or real-time multiplayer editing, so it stays a communication artifact while Jira keeps the execution detail.

• Replace "by June 12" with "Now" and keep the detail in the tracker.
• Keep columns equal width so nothing reads as a duration.
• Write outcomes as the change, not the feature that causes it.
• Put confidence on the page; it does the job dates pretend to do.

A filled-in B2B SaaS example

Say you run product for a B2B SaaS workflow tool sold to operations teams. The quarter goal at the top reads: make new workspaces reach first value without a customer success call. The audience line names the exec team, the sales org, and the platform engineering group. Everything below that is a row, not a paragraph.

Notice how little of it reads like a feature list. Each Now row names a customer problem, the behavior change expected, an owner by role, and a confidence level. Reporting sits in Next because the outcome is understood but the shape is not; integrations sit in Later with no owner because committing now would be fiction. The Not Doing list does real work by answering the mobile question before it is asked.

This page takes about a minute to read, which is the actual success test. If a sales rep cannot answer "what's coming for admin permissions?" by pointing at one row, the template failed and no amount of visual polish will rescue it.

• Now — Onboarding: new workspaces reach first value without a CSM call. Owner: PM, onboarding squad. Confidence: high.
• Now — Admin and permissions: IT grants scoped access without shared logins. Owner: engineering lead, platform. Confidence: medium.
• Next — Reporting: a weekly usage export replaces the manual spreadsheet. Owner: PM, reporting. Confidence: medium.
• Later — Integrations: two-way sync with the CRM the sales team already uses. Owner: unassigned, revisit next quarter.
• Not Doing — native mobile app; revisit when the web editor stabilizes.

Slides, spreadsheets, or a roadmap tool

Google Slides, Pitch, and Canva are best when the roadmap is a presentation for an exec review and the deck is the deliverable. Google Sheets, Notion, and Airtable are best when the roadmap is a living document your team already opens every day and wants to filter. Productboard, Aha!, and Jira Product Discovery are best when you need idea intake, scoring, and customer feedback tied to roadmap items. Miro and FigJam are best for the workshop itself. None of these is wrong; pick based on where your readers already are.

Roadmap Creator is the option for turning a one-sentence goal into a visual, editable roadmap quickly, with AI on every node to expand or break a step down. It exports to PDF or PNG, shares via a read-only public link, and embeds in Notion or any site, which covers the socialization part of the quarter. It is a focused roadmap tool, not a project management suite: no team invites or comments, no sprint or issue tracking, no Jira or GitHub integrations.

One practical pattern: workshop in FigJam, publish in the format your audience reads, and keep execution in Linear. A spreadsheet is a perfectly good starting point too — most teams already have one, and the discipline of column headers forces the schema conversation early.

• Slides for a single live review with a fixed audience.
• Spreadsheets or Notion for a team that wants to filter and copy rows.
• Productboard or Jira Product Discovery when feedback intake is the bottleneck.
• Roadmap Creator when you need a visual draft fast and a shareable link.
• Jira or Linear always, for the tickets themselves.