Now next later roadmap: ditch the dates, keep the trust

Your stakeholders want a roadmap with dates. Your engineering team says estimates are unreliable. And you’re stuck in the middle, either overpromising and disappointing people or padding estimates so much they’re meaningless. The now next later roadmap solves this by shifting the conversation from “when exactly” to “what order” — and it’s become the default format at outcome-driven product teams for good reason.

Why date-based roadmaps create more problems than they solve

Traditional roadmaps with quarters and delivery dates feel professional. They look like project plans. Executives can put them in board decks. But they create a cascade of problems that undermine good product management.

False precision breeds false expectations. When you put “Q2 2024” next to a feature, stakeholders treat it as a commitment. But you made that estimate months ago, before you’d done discovery, before you understood the technical complexity, before that senior engineer left. Now you’re either shipping something half-baked to hit the date or having awkward conversations about delays.

Dates encourage output thinking. A roadmap that says “Launch recommendation engine in March” puts all the focus on shipping the thing. It says nothing about whether that recommendation engine actually improved the metric you cared about. Teams hit their dates and miss their outcomes.

Rigidity kills learning. Discovery might reveal that your original feature idea won’t solve the problem. But when it’s already on a dated roadmap that’s been shared with sales and the board, changing direction feels like failure rather than smart product management.

Marty Cagan has been making this argument for years: roadmaps full of features and dates are “essentially waterfall dressed up in Agile clothing.” The now next later roadmap offers a genuinely different approach.

How the now next later roadmap works

The format is exactly what it sounds like. Three columns — or time horizons — that communicate priority and sequence without committing to specific dates:

Now: What we’re actively working on this sprint or cycle. High confidence, well-defined, in progress.

Next: What’s coming up after current work completes. Medium confidence, discovery done or in progress, roughly scoped.

Later: What we’re considering for the future. Low confidence, needs more discovery, may change significantly.

The key insight is that confidence decreases as you move right. “Now” items are commitments. “Later” items are possibilities. This maps to how product development actually works — you know a lot about what you’re building this week and very little about what you’ll build in six months.

Janna Bastow, CEO of ProdPad, popularized this format and has written extensively about how it transforms stakeholder conversations. Instead of debating whether something will ship in Q2 or Q3, you discuss whether it should move from “Later” to “Next.”

How to fill each column

The “Now” column

This should reflect your current sprint or cycle’s committed work. Include:

• Features or improvements actively in development
• Problems you’re solving (not just solutions)
• The outcome you’re targeting with each item

Keep it tight. If you have more than 2-4 items in “Now,” you’re probably working on too many things at once. Spotify’s squad model emphasized this focus — teams that spread across many initiatives moved slower than teams concentrated on one or two.

For each “Now” item, you should be able to answer: What’s the problem? What’s the solution approach? What outcome are we measuring? Who’s working on it?

The “Next” column

These are items where discovery is complete or nearly complete. You understand the problem well, you have a general solution direction, and you’ve validated that solving this matters.

• Include items that will likely move to “Now” in the next 1-3 cycles
• Frame them as problems or opportunities, not just features
• Be prepared to explain why each item is prioritized here

The “Next” column is where Teresa Torres’s continuous discovery [INTERNAL_LINK: continuous discovery habits] becomes visible. Items here should be backed by customer research, not just stakeholder requests or gut feelings.

The “Later” column

This is your strategic backlog — ideas worth tracking but not yet worth committing to. Include:

• Problems you’ve identified but haven’t deeply researched
• Stakeholder requests that need validation
• Strategic bets that depend on earlier work succeeding
• Technical investments you’re considering

Be comfortable with ambiguity here. Items in “Later” might be phrased as questions: “How might we reduce support tickets for enterprise accounts?” rather than specific features.

Intercom’s product team has talked about using “Later” as a parking lot that prevents premature commitment while still acknowledging that ideas have been heard.

A simple now next later template

Here’s a structure you can adapt:

Now (Current cycle — high confidence)

1. Problem: [Description] → Approach: [Solution] → Outcome: [Metric]
2. Problem: [Description] → Approach: [Solution] → Outcome: [Metric]

Next (1-3 cycles out — medium confidence)

1. Opportunity: [Description] → Why now: [Reasoning]
2. Opportunity: [Description] → Why now: [Reasoning]
3. Opportunity: [Description] → Why now: [Reasoning]

Later (Future — low confidence, may change)

• [Problem or opportunity statement]
• [Problem or opportunity statement]
• [Problem or opportunity statement]

Notice how detail decreases as confidence decreases. “Now” items have specific solutions and metrics. “Later” items might just be problem statements.

How to present the now next later roadmap to stakeholders

The format change requires a positioning change. Don’t just show a different-looking document — explain why this approach serves everyone better.

Lead with outcomes, not format. “This roadmap shows what we’re prioritizing to hit our retention goals” lands better than “We’re trying a new roadmap format.”

Explain confidence levels explicitly. “Items in Now are committed. Items in Next are likely but could shift if we learn something in discovery. Items in Later are on our radar but may change significantly.”

Connect to company goals. Show how each column maps to strategic objectives. The roadmap isn’t a feature wishlist — it’s a plan for achieving outcomes the business cares about [INTERNAL_LINK: product strategy].

Invite discussion about priorities, not dates. “Should reducing churn be in Next, or should we prioritize the onboarding improvements first?” is a better conversation than “Will this ship in Q2?”

Lenny Rachitsky has shared examples from companies like Figma and Linear that communicate roadmaps this way, focusing stakeholder attention on strategic trade-offs rather than schedule negotiations.

Handling pushback when people want specific dates

You will get pushback. Sales needs to tell customers when features are coming. Executives need to plan around product launches. Marketing needs lead time for campaigns. Here’s how to handle it:

“Sales needs to tell customers when this will ship”

Offer ranges tied to confidence levels. “Items in Now typically ship within 4-6 weeks. Items in Next are usually 2-4 months out, but I’d recommend checking back monthly since priorities can shift.”

For major features that sales is actively selling against, consider a separate communication track with more specific timing — but make clear that’s a commitment with consequences if you miss it.

“The board/executives need dates for planning”

Reframe around milestones rather than features. “By end of Q2, we expect to have shipped solutions addressing customer churn. The specific solutions may evolve as we learn, but the outcome we’re targeting is a 15% reduction.”

This gives executives what they actually need — predictability around business outcomes — while preserving your flexibility on implementation.

“We’ve always done roadmaps with dates”

Acknowledge the discomfort and propose a trial. “I understand this feels different. Can we try it for one quarter and see if it actually gives you better information about what’s coming and why?”

Often the resistance is about familiarity, not effectiveness. Once stakeholders experience conversations focused on priorities instead of schedule debates, many prefer it.

“How do I know you’re making progress?”

This is a fair concern. Address it by establishing a regular cadence of updates where items visibly move from Later to Next to Now to Done. The roadmap becomes a living document that demonstrates velocity without date commitments.

Making the now next later roadmap work long-term

The format only works if you maintain it. Update regularly — at least every two weeks, ideally weekly. Stale roadmaps lose credibility regardless of format.

Review priorities monthly with stakeholders. This keeps alignment high and surprises low. If something is moving from Next to Later, they should hear about it before it happens.

Celebrate outcomes, not just launches. When something moves from Now to Done, share the results. Did it achieve the outcome you targeted? This reinforces that the roadmap is about impact, not output.

The now next later roadmap isn’t just a different visual format — it’s a different philosophy about what roadmaps are for. They’re not project schedules. They’re communication tools that align teams around priorities while preserving the flexibility to build the right thing.

Start by converting your current roadmap. Take your dated items and sort them into the three columns based on confidence level and priority. Then have a conversation with your stakeholders about what you learned from the exercise. That conversation alone will be more valuable than any Gantt chart.

Frequently asked questions