The Hook
Your quarterly roadmap is full: 20 features in development. But customers keep asking "What's coming next?" You don't have a clear answer beyond this quarter.
Without a longer vision, customers don't know if you're headed in a direction they care about. So they leave for competitors with clearer roadmaps.
Now-Next-Later framework communicates: What's happening now (this quarter), what's next (next quarter), what's later (vision, 6+ months out).
The Framework
| Timeframe | Commitment | Uncertainty |
|---|---|---|
| Now | Committed to shipping this quarter | Low (mostly planned) |
| Next | High-confidence priorities for next quarter | Medium (subject to change) |
| Later | Vision for 6+ months out | High (exploratory) |
This structure prevents: "We ship 10 features every quarter but I don't know where this product is going."
Actionable Steps
1. Communicate Now-Next-Later Publicly
Use this structure for customer communication:
Now: Specific features + ship dates Next: General direction (e.g., "Improving integrations for power users") Later: Vision (e.g., "Building enterprise collaboration features")
Customers see: You have a plan beyond this quarter, but you're flexible on specifics.
2. Revisit the Roadmap Quarterly
Update Now → Next → Later every quarter:
- What was in "Now" is shipping (done)
- What was in "Next" moves to "Now" (committed)
- New priorities become "Next"
- Vision gets refinement in "Later"
This creates predictable rhythm without rigid commitment.
Key Takeaways
-
Now-Next-Later balances clarity with flexibility. Customers see direction without forcing you into immovable commitments.
-
Update quarterly, not annually. This prevents strategic drift while allowing tactical flexibility.
-
Later is for vision, not promises. Use it to signal direction, not specific features.
The Problem With Date-Based Roadmaps
Case Study: The Roadmap Promise That Failed
A B2B SaaS company published a roadmap: "Advanced reporting in Q2 2024, Mobile app in Q3 2024."
What happened:
- Q2: Advanced reporting hit a technical blocker. 2-week delay.
- Q2 end: Mobile app started slipping; complex infrastructure work.
- Q3: Customers asked "Where's the mobile app? You said Q3."
- Actual mobile launch: Q4 (late)
- Customer impact: 3 customers left ("You ship late, your roadmap is meaningless")
The problem: By committing to dates, you owned responsibility for external factors: technical surprises, dependencies, market changes.
Lesson: Date-based roadmaps create trust issues when they slip. Now-Next-Later roadmaps assume slips are normal.
Now-Next-Later vs. Other Roadmap Formats
| Format | Accuracy | Customer Clarity | Flexibility | Risk |
|---|---|---|---|---|
| Date-based | Low (90% slip) | High (clear) | Low (committed) | High (broken promises) |
| Feature-based | Medium (feature scope clear) | Medium (timing unclear) | High (vague) | Medium |
| Now-Next-Later | High (realistic) | High (vision clear) | High (flexible) | Low |
Now-Next-Later gives you the best of all worlds.
How to Build a Now-Next-Later Roadmap
Step 1: Define "Now" (Next 90 days)
"Now" is what you're actively building. High confidence. Mostly designed. Engineering in progress.
Criteria: "We will ship this within 12 weeks."
Example Now roadmap:
- Customer audit trails (in design review)
- Advanced permissions matrix (in development)
- Mobile API improvements (starting development)
- Bug fixes & stability improvements (ongoing)
Step 2: Define "Next" (90–180 days)
"Next" is your roadmap for 1–2 quarters ahead. You have confidence on direction, not on exact scope.
Criteria: "We're confident we'll do something in this area in the next 2 quarters."
Example Next roadmap:
- Improving integrations for power users
- Building webhooks for custom automation
- Enhancing mobile app performance
Notice: Not specific features. Themes. Directions.
Step 3: Define "Later" (6+ months)
"Later" is your vision. Where are you headed? What are the big bets?
Criteria: "We might do this in the next 6–12 months if business conditions support it."
Example Later roadmap:
- Building enterprise collaboration features
- Exploring AI-powered analytics
- Considering white-label capabilities
Notice: These are explorations, not commitments.
The Communication Challenge: Different Stakeholders Need Different Views
For Customers:
Show Now-Next-Later exactly as is. Lets them see direction without over-committing.
For Internal Teams (Engineering):
Add more detail. Engineering wants more specificity on "Now" and "Next" (what exactly are we building?).
For Leadership/Board:
Emphasize "Now" (What ships this quarter?) and strategic bets in "Later" (Where are we going?).
For Investors (Due Diligence):
Show "Now" + "Later" connected to business goals (how does this roadmap support revenue growth?).
Anti-Patterns: Now-Next-Later Misapplication
Anti-Pattern 1: "Treating Later like it's committed"
You put "AI-powered insights" in Later. Customers take it as gospel. 18 months later, you haven't done it. Customer churn.
Fix: Use language like "Exploring" or "Considering" in Later. Make it explicit that Later is vision, not commitment.
Anti-Pattern 2: "Never updating the roadmap"
You set a Now-Next-Later roadmap at the start of the year. You never update it. By Q3, it's stale.
Fix: Update the roadmap every quarter. Religiously. It's a living document.
Anti-Pattern 3: "Treating Now as flexible"
You put features in Now. Then stakeholders keep asking for exceptions. "Can we add one more?" Now becomes a negotiation zone.
Fix: Protect Now. It's committed. If something new is critical, something must move out of Now.
The Economics: Now-Next-Later Prevents Customer Churn
Scenario A: Date-based roadmap (broken promises)
- Q1: Announce "Feature X in Q2"
- Q2: Miss deadline (slips to Q3)
- Q3: Customers disappointed. 2 customers leave. -$100K ARR
- Customer trust degraded. Future announcements receive skepticism.
- Cost of repair: Lost sales pipeline (harder to close new customers)
Scenario B: Now-Next-Later (realistic)
- Q1: Announce "Now: Feature Y, Next: Direction toward Feature X"
- Q2: Deliver Feature Y on time (increases trust)
- Q3: Deliver direction on Feature X (fulfills promise)
- Customer trust increases. Easier to close new customers. +$200K ARR from improved pipeline.
The difference: Honest roadmaps lead to trust, which leads to growth.
Prodinja Connection (Updated)
A Now-Next-Later roadmap is only as good as the prioritization behind it. Prodinja's RICE/Kano prioritization tool is designed to help you decide what actually belongs in Now versus Next versus Later: score each candidate on Reach, Impact, Confidence, and Effort, tag it with a Kano category, and watch the ranking update live as you adjust inputs or priorities shift mid-quarter. Instead of debating which items deserve a committed "Now" slot from memory, you can walk through the scores together and let the re-ranked list show you what earns its place — and what should move to Next or Later instead.
Key Takeaways (Updated)
-
Date-based roadmaps are fantasy; Now-Next-Later is realistic. Dates slip. Timelines don't matter. Commitment levels do.
-
Now is committed, Next is directional, Later is exploratory. Be explicit about confidence levels at each stage.
-
Update quarterly. Now-Next-Later only works if you keep it current. Stale roadmaps hurt trust more than no roadmap.
-
Communicate differently to different audiences. Customers see vision. Engineering sees details. Leadership sees strategy alignment.
-
Now-Next-Later reduces customer churn by managing expectations. Customers forgive delays on directional features ("Later") but not on committed features ("Now").