Now Next Later Roadmap
The Now/Next/Later roadmap, popularized by Janna Bastow at ProdPad, replaces date-based roadmaps with three time-bucketed columns: Now (currently being built), Next (validated and queued), Later (under exploration). It explicitly refuses to commit dates beyond 'Now.' This format encodes the truth that confidence in your roadmap decays exponentially with time horizon — the things you'll do in 9 months are guesses, not commitments. By formatting them as guesses, you stop being held to them. Now/Next/Later is the most-adopted alternative roadmap format in product because it solves the political problem (sales wants commitments) by giving them a structured way to see future direction without being able to extract a ship date.
The Trap
The trap is letting Next and Later become 'soft commitments' that sales sells against. The moment a sales rep tells a prospect 'this is in our Next column, so 6–9 months,' the format has been broken — you're back to date-based commitments with extra steps. The other failure mode: items that camp in Later for 3+ years, signaling the team has no actual intention of building them but won't admit it. Later should turn over — items move forward to Next, get killed, or get archived. A stagnant Later is a graveyard.
What to Do
Limit each column: 3–5 items in Now, 5–8 in Next, 8–15 in Later. Force movement: items in Now exit when shipped (90 days max). Items in Next earn promotion to Now via discovery validation, not calendar pressure. Items in Later get a quarterly review where each one moves up, gets killed, or stays — but stays must be justified. Train sales on the language: Now = building, Next = under exploration, Later = being considered. No dates.
In Practice
Janna Bastow created the Now/Next/Later format at ProdPad in 2014 specifically to solve the date-commitment problem in B2B SaaS. ProdPad's own product team has used it ever since, and the format has been adopted by thousands of product teams including Atlassian (for some product lines), GoCardless, and many YC-funded startups. Bastow's published guide explicitly addresses the political dynamic: 'The format works because it gives stakeholders a window into priorities without giving them ammunition to commit to customers.' Source: Janna Bastow, ProdPad blog and Mind the Product talks.
Pro Tips
- 01
Janna Bastow: 'Now/Next/Later is not a planning tool — it's a communication tool. Your real plan lives elsewhere. The roadmap is what you tell the company to align them without lying about certainty.'
- 02
Pair with a 'recently shipped' column. Sales and CS need to see what's already done — without it, they default to asking about Next as if it were Now. The shipped column absorbs the 'where is X?' questions.
- 03
Reorder Now/Next/Later within columns deliberately. Position signals priority within the bucket. 'Top of Next' is a real signal; 'middle of Later' communicates honest ambivalence.
Myth vs Reality
Myth
“Now/Next/Later is for early-stage startups only”
Reality
Larger companies including Atlassian product lines and GoCardless use it because the certainty problem doesn't go away with scale — it gets worse. The format scales with the org as long as there's a separate detailed plan for engineering execution.
Myth
“Sales hates Now/Next/Later”
Reality
Sales hates being lied to. Date-based roadmaps that miss create more sales damage than Now/Next/Later. The actual challenge is training sales on how to communicate the format to prospects — once that's done, sales adopts because it's defensible.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your sales team complains that Now/Next/Later 'doesn't give them anything to sell against.' A prospect needs to know if SSO will ship before they sign. What's the most disciplined response?
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
ProdPad
2014–present
Janna Bastow created Now/Next/Later at ProdPad in 2014 to solve the date-commitment problem her customers (product teams) faced. ProdPad's own product team has used the format continuously since, and ProdPad as a tool now has the format built in as the default roadmap view. Thousands of teams have adopted it including Atlassian product lines and GoCardless. The defining insight: roadmap format is a communication problem, and Now/Next/Later codifies the honest level of certainty at each horizon.
Format Age
11+ years
Companies Using It
Thousands (estimate)
Core Promise
No dates beyond Now
A format that survives 11+ years and scales from startup to enterprise solves a real problem. The problem here was always communication, not planning — and most teams confused those two.
Hypothetical: A Series B B2B SaaS
2024
A Series B B2B SaaS adopted Now/Next/Later but allowed sales to communicate Next items with 'rough timing' to prospects — '~Q3' for top-of-Next, '~end of year' for bottom. Within 6 months, half of contract negotiations included specific feature delivery dates derived from the Next column. When Q3 came and 3 of those features hadn't shipped, the company faced 4 contract renegotiations and lost 2 deals. They reverted to date-based roadmaps in Q4, concluding 'Now/Next/Later didn't work for us.' The format hadn't failed — its enforcement had.
Format Adoption Period
6 months
Sales Commits Derived from Next
~50% of contracts
Contracts Renegotiated
4
Deals Lost
2
Now/Next/Later requires sales training and explicit prohibition on date inference. Without that, the format is decorative and arguably worse than a date roadmap because it pretends to be honest while enabling implicit commitments.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Now Next Later Roadmap into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Now Next Later Roadmap into a live operating decision.
Use Now Next Later Roadmap as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.