Now
Work in active development this quarter. Each item is scoped, committed, and has a named owner. If something is in 'Now,' the team has said: we will ship this. Keep this column short — three to five initiatives maximum.
Free template
Free product roadmap template — now, next, later on one board.
Lay out what you're building, in what order, and why — on a whiteboard everyone can read from the back of the room. Snap it and BoardSnap turns the board into a structured plan.
Download on the
App Store
Free to start. Pro from $9.99/mo or $69.99/yr.
When to run this
Build or refresh the product roadmap at the start of each quarter, after a major strategy shift, or whenever the existing roadmap no longer reflects what the team is actually building. The roadmap session should include product, engineering, and at least one stakeholder who can speak to customer needs.
A whiteboard roadmap forces hard choices. There's only so much space — you can't add a 47th initiative without erasing something else. That constraint is the most valuable thing the format does.
The structure
Next
The top candidates for the following quarter. Roughly prioritized, not fully scoped. Items here are the team's best current thinking — they can change as you learn. Each item should have a one-line rationale for why it ranks where it does.
Later
Validated ideas that aren't prioritized yet. Not a trash bin — these items are real candidates that lost the prioritization contest this cycle. Anyone who asks 'when are you doing X?' gets a straight answer: 'Later — here's where it sits.'
Themes (row headers)
Group roadmap items by strategic theme — Growth, Retention, Platform, Developer Experience, etc. Themes run as row labels on the left; columns run Now/Next/Later. The intersection shows which themes have work in each horizon.
Dependencies
Draw lines between items that depend on each other. A 'Next' item that depends on a 'Later' item is a planning problem — surface it now. Dependencies are often invisible until you draw them on a board.
How to run it
- Align on themes (10 min)
Write the 3–5 strategic themes for the quarter on the left as row headers. These come from the company strategy or OKRs. Everything on the roadmap should trace back to at least one theme — items that don't fit any theme probably don't belong.
- Populate Now (15 min)
Place active, committed work in the Now column. Be honest about what's actually scoped and owned. If you can't name the engineer and the ship date, it doesn't belong in Now.
- Prioritize Next (20 min)
Write candidate items for Next, then rank them. Use dot voting if the group can't agree. Each item that makes the column gets a one-line 'why now' rationale written on the sticky.
- Populate Later, then prune
Write Later items, then apply the one-year test: if you haven't done it in a year, would you miss it? Items that fail the test get erased. Keep Later honest — it's not a graveyard.
- Draw dependencies
Connect dependent items with arrows. Identify blockers: which Later items need to move up because a Now item depends on them?
- Snap and distribute
Snap the board with BoardSnap. The AI reads the roadmap structure and outputs a clean summary — themes, items by horizon, dependencies — ready to share with stakeholders who weren't in the room.
Why product roadmaps on a whiteboard + BoardSnap is better than digital
A Jira roadmap or Notion table is invisible to most of the company. A whiteboard on the product team's wall is a conversation starter. Engineers walking by ask questions. Sales asks what's coming. The physical roadmap creates alignment that a shared doc never does — because you actually have to walk past it.
BoardSnap preserves the artifact. Snap the roadmap after every quarterly session and BoardSnap reads the full structure — themes, Now/Next/Later items, dependencies — and outputs a shareable summary. The board becomes the single source of truth; the snap makes it portable.
Frequently asked
How is a Now/Next/Later roadmap different from a timeline roadmap?
A timeline roadmap puts items on specific dates. A Now/Next/Later roadmap uses relative horizons — this quarter, next quarter, someday. Timeline roadmaps communicate false precision; horizon roadmaps are more honest about uncertainty. For most product teams, Now/Next/Later is more useful because it doesn't pretend to know what you'll be prioritizing in Q4.
How do you handle stakeholder requests that don't fit the roadmap?
Add them to Later with a note. Then walk the stakeholder through the prioritization logic. 'Here's where it sits and why it's not in Now' is a much better answer than 'we'll get to it.' The visible board makes that conversation objective rather than political.
How often should the roadmap be updated?
Formally, quarterly. Informally, whenever a major new piece of information (customer research, competitive move, technical constraint) changes the priority order. Snap the board each time you update it — BoardSnap timestamps the artifact so you have a history of how the roadmap evolved.
Should engineering be involved in roadmap planning?
Yes — at least senior engineers or tech leads. The most common roadmap failure is product planning without understanding technical dependencies and complexity. Engineers in the room surface 'that's actually a month of work' before it's committed, not after.
Run your next product roadmap and BoardSnap will summarize it.
No exporting, no transcription. Snap the board, get the action plan.
Free · 1 project, 30 boards
Pro $9.99/mo · everything unlimited
Pro $69.99/yr · save 42%