Now / Next / Later Roadmap
The roadmap format that communicates priorities without over-committing to dates. How to build one, real examples, and why it works better than timelines for agile teams.
Features.Vote's roadmap uses this format natively — see all roadmap templates
The Three Columns
Current sprint / this month
Confidence: High — committed, in progress
What you're actively building right now. These items have been prioritized, scoped, and assigned. The team is working on them. Max 3-5 items — if you have more, you're spreading too thin.
Rules
- Max 3-5 items — forces ruthless prioritization
- Each item has a clear owner and definition of done
- Items should ship within the current sprint or month
- Moving something to 'Now' is a commitment, not an aspiration
Example Items
CSV export for analytics dashboard
Onboarding flow redesign (Phase 1)
Slack integration — webhook notifications
1-3 months out
Confidence: Medium — planned, not committed
What you're planning to build after the current sprint. These items are validated (users want them) and scoped enough to estimate, but not yet committed. They'll move to 'Now' when current work ships.
Rules
- 5-10 items — more specificity than 'Later', less commitment than 'Now'
- Items should be refined enough to estimate (not vague ideas)
- Priority order matters — top items move to 'Now' first
- Review and reorder monthly based on new data (votes, feedback, strategy)
Example Items
Dark mode support (47 votes)
Team permissions and roles
API v2 with webhook support
3+ months out
Confidence: Low — directional, not committed
What you might build in the future. These are ideas validated by user demand (votes, requests) but not yet scoped or committed. 'Later' communicates direction without making promises. Items may move up, get merged, or be deprecated.
Rules
- 10-20 items max — 'Later' is not a backlog dump
- Items represent themes or capabilities, not specific implementations
- Review quarterly — archive stale items, promote validated ones
- Be honest: some 'Later' items will never happen, and that's okay
Example Items
Mobile app (23 votes, monitoring demand)
Advanced analytics with custom dashboards
White-label / multi-tenant support
Why Now/Next/Later Works
Forces prioritization
Max 3-5 items in 'Now' means you can't hide behind a 50-item 'in progress' list. If everything is priority, nothing is. Now/Next/Later makes the hard choices visible.
Honest with users
Timeline roadmaps imply promises: 'March 15.' Now/Next/Later says 'this is current priority.' When priorities shift, users understand — you changed direction, not broke a promise.
Data-driven movement
Items move from Later → Next → Now based on user votes, strategic alignment, and feasibility. A voting board naturally feeds this pipeline — top-voted items earn their way up.
Always current
Timeline roadmaps go stale when dates slip. Now/Next/Later is always accurate because it reflects current priorities, not past plans. Update it in 5 minutes during sprint planning.
Now/Next/Later vs. Timeline Roadmap
Date commitments
Now/Next/Later
No — communicates priority, not dates
Timeline
Yes — implies specific delivery dates
Flexibility
Now/Next/Later
High — reorder anytime without 'broken promises'
Timeline
Low — changing dates feels like missing deadlines
Communication
Now/Next/Later
"We're building X now, Y is next"
Timeline
"X will ship on March 15"
Audience
Now/Next/Later
Agile teams, customers, public roadmaps
Timeline
Executives, boards, contract-driven stakeholders
Over-commitment risk
Now/Next/Later
Low — 'Next' and 'Later' are explicitly not committed
Timeline
High — dates create expectations and pressure
Planning cadence
Now/Next/Later
Review monthly, adjust continuously
Timeline
Plan quarterly, update reluctantly
Best for
Now/Next/Later
Continuous delivery, SaaS, startups
Timeline
Fixed releases, enterprise, regulated industries
Need a timeline roadmap instead? See our 10 roadmap templates including timeline, kanban, and RICE-scored formats.
Real Examples
Basecamp
Uses a 'Hill Chart' variation of Now/Next/Later — work moves from 'figuring out' to 'making it happen.' No timeline, just progress visualization.
Lesson: You don't need dates to show progress. Direction + momentum is enough.
Linear
Roadmap shows projects with status (Planned, In Progress, Completed) without specific dates. Public roadmap uses the same format.
Lesson: The best engineering teams in the world don't commit to dates on their public roadmap — they commit to priorities.
Buffer
Public roadmap organized by 'Exploring', 'In Progress', 'Done'. Users vote on ideas. Most-voted items move from Exploring to In Progress.
Lesson: A public Now/Next/Later roadmap powered by user votes is the ultimate transparency play.
Ghost
Open-source CMS with a public roadmap showing 'Planned', 'In Progress', 'Shipped'. Community contributes to prioritization through GitHub discussions.
Lesson: Open-source products benefit enormously from transparent prioritization — the community self-selects what to contribute to.
How to Build Yours
List everything you're building right now
Look at your current sprint. What's actively in progress? These are your 'Now' items. If there are more than 5, you're over-committed — move excess to 'Next.'
Identify what's validated and coming next
Review your voting board, customer interviews, and strategic priorities. What has the most votes? What aligns with this quarter's goals? These are 'Next' — 5-10 items, ordered by priority.
Capture directional ideas in 'Later'
Everything else that's validated by demand but not yet scoped goes to 'Later.' This isn't a backlog dump — max 20 items that represent real future directions.
Make it public and add voting
Share the roadmap publicly. Add a voting board so users can influence what moves from Later → Next → Now. Features.Vote connects voting directly to roadmap status.
Review and update regularly
Now: every sprint. Next: monthly. Later: quarterly. When you ship from 'Now,' pull the top item from 'Next.' When new data (votes, strategy shifts) arrives, reorder.
"Was very easy and intuitive to get started and I was able to do it in a few minutes which was good."
Joe Bloxsome,
Founder at GoPasswordless
Frequently Asked Questions
Still not convinced?
Here's a full price comparison with all top competitors
Is it lacking a feature you need?
Chances are, we're already working on it. Check our roadmap
Okay, okay! Sign me up!
Start building the right features today ⚡️