A Now-Next-Later roadmap is a powerful way to show your product's direction without getting boxed into rigid, brittle timelines. It boils everything down to three simple columns: Now (what the team is actively building), Next (what's queued up), and Later (ideas bubbling for the future). It’s perfect for any team that needs to stay agile and focused on what really matters: delivering value to customers.
Your Framework for a High-Impact Roadmap
Stop making roadmaps that nobody looks at. As a product leader who has hired and mentored dozens of PMs at companies like Google and Meta, I’ve seen way too many teams get bogged down by date-driven Gantt charts. They're obsolete the second they’re published. The Now-Next-Later roadmap, which was really popularized by innovative companies like Intercom, is the antidote to that chaos.
This isn't just a new way to organize features. It’s a fundamental shift in mindset. You move from project management ("When will it be done?") to true product management ("What problem are we solving and why does it matter?"). This framework is a core skill for PMs at all levels; a Senior PM at a Series B startup making $180k is expected to master this communication style just as much as a Director at a FAANG company.
The Core Components of the Framework
The goal here is to create a living document that communicates direction and priorities, not a list of unbreakable promises. The framework’s biggest strength is its simplicity and flexibility. It lets you react to new customer feedback or a sudden market shift without having to tear up your entire plan.
Here’s a breakdown of how the three columns should work:
- Now: Your team's current focus. These items are high-confidence, fully scoped, and being actively worked on in the current development cycle (e.g., the current 2-week sprint). This is where you build credibility.
- Next: What's on deck for the upcoming quarter. These initiatives have been validated and prioritized, but the deep-dive design and scoping work hasn't kicked off yet. This is your 1-3 month outlook.
- Later: Your strategic backlog for 3+ months out. It’s a parking lot for promising ideas, big swings, and future opportunities that align with your long-term vision but need more discovery before any real commitment.
The key takeaway from this visual is that a roadmap should be a dynamic tool for alignment, not a static checklist of features. It's a conversation starter.
Now vs Next vs Later Framework Breakdown
To make this even clearer, here is an actionable template you can use to explain the distinct purpose and commitment level for each column to your stakeholders. Getting everyone on the same page is the first step to success.
| Column | Time Horizon and Focus | Commitment Level | Example Items |
|---|---|---|---|
| Now | Immediate term (current sprint/quarter). Focus on execution. | High. These are firm commitments. The team is building this. | Finalizing user profile redesign Fixing critical login bug |
| Next | Mid-term (1-3 months out). Focus on validation and scoping. | Medium. High confidence, but details can still change. | Researching a new third-party integration Designing a new dashboard |
| Later | Long-term (3+ months out). Focus on ideas and discovery. | Low. These are possibilities, not promises. | Exploring international expansion Investigating a machine learning feature |
Using this structure helps manage expectations and keeps conversations focused on the right level of detail for each stage.
Setting the Ground Rules for Success
Before you even start filling out your roadmap, you have to set some ground rules with your stakeholders. This is probably the most critical step, and it's a cornerstone of what we cover in our guide on product roadmap best practices. It's the same principle that makes a powerful book marketing plan effective; strategic planning is everything.
The most important rule of a Now-Next-Later roadmap is this: only 'Now' has a high degree of commitment. 'Next' and 'Later' represent direction and priority, not a promise of delivery on a specific date. This distinction is critical for managing expectations.
Getting this clarity upfront stops the sales team from selling features parked in the 'Later' column. It also gives your engineering team the breathing room they need to do high-quality work without constantly being asked about dates for things that are months away.
Why This Approach Works So Well Today
Technology is in a state of constant motion. As of early 2024, there are over 5.35 billion internet users. Customer needs and competitive threats are evolving faster than ever. The Now-Next-Later framework is purpose-built for this reality, giving you a way to meet immediate market demands while still keeping an eye on the bigger picture. It's the standard for modern, agile product teams.
Populating the Now Column with Confidence
The "Now" column isn’t just another to-do list. Think of it as your team’s public commitment—it’s the bedrock of your credibility as a product manager. When anyone from the CEO to a new hire looks at this column, they should see an undisputed source of truth for what engineering is actively building.
Your job is to make sure every single item here is clearly defined, tightly scoped, and has an exceptionally high degree of confidence for completion. This is where abstract strategy gets real, fast. At places like Google and Meta, the "Now" column is a direct reflection of the current sprint or development cycle. These items have graduated from the idea phase; they are now broken down into specific user stories and epics.
From Strategic Goal to Actionable Work
A classic rookie PM mistake is dropping a high-level goal like "Improve user onboarding" into the "Now" column. That’s a great theme, but it belongs in "Next" or even "Later." For something to earn its spot in "Now," it must be translated into concrete, buildable chunks of work.
Here’s a step-by-step process to break it down:
- Start with the Initiative: Improve user onboarding.
- Break into Epics: 1) Streamline account creation, 2) Enhance the in-app welcome experience, 3) Improve the welcome email flow.
- Write Specific User Stories (for the "Now" column):
- As a new user, I want to sign up with my Google account so I can create an account in one click.
- As a new user, I want to see a 3-step welcome modal that explains the core features.
- As a new user, I want to receive a welcome email with a link to the help documentation.
See the difference? Each of these is a specific, well-defined piece of work a developer can actually pick up and run with. This level of granularity is completely non-negotiable for anything you put in "Now."
As a product leader, I’ve seen trust erode quickly when vague promises land in the 'Now' column. The rule is simple: if you can't write a clear user story for it and your engineering lead hasn't signed off on the scope, it doesn't belong here.
Collaborating with Engineering for High Confidence
Your most important partner for filling the "Now" column is your engineering lead. This relationship is what turns a prioritized feature into something that is truly "ready for development." Before any card officially moves into "Now," you and your tech lead need to have a very explicit conversation.
Use this pre-flight checklist for your alignment meetings:
- [ ] Confirm the "Why": Start by restating the customer problem and the business goal. This gives the engineering team context, not just a task list.
- [ ] Review the Scope: Walk through every user story and its acceptance criteria. Is anything ambiguous? Are there hidden complexities lurking?
- [ ] Identify Dependencies: Does this work rely on another team’s API? A design system update? These need to be flagged and managed before work begins.
- [ ] Get an Effort Estimate: While your roadmap isn't about hard dates, you need a rough estimate (often in story points) to make sure the work realistically fits into the current cycle's capacity.
This isn't about pinning them down on a deadline. It's about building a shared understanding and mutual confidence. A senior PM I know at a B2B SaaS company put it perfectly: "I don't move a single card into 'Now' until my tech lead gives me a thumbs-up. That's our pact."
Defending Against Scope Creep
Once an item is in the "Now" column, its biggest enemy is scope creep. It's inevitable. A stakeholder will see the work in progress and hit you with the classic, "While you're in there, could you just add…?"
How you respond in that moment defines your effectiveness. Instead of a hard "no," use the roadmap as your shield. A great response is, "That's a great idea, and it sounds valuable. Right now, the team is fully committed to delivering the current scope. Let's add your idea to the 'Next' column so we can prioritize it for an upcoming cycle."
This approach does three things beautifully: it validates their input, protects your team from distraction, and reinforces the disciplined structure of your now next later roadmap. It keeps the "Now" column clean, ensures you deliver on your promises, and builds the trust you need to grow in your career.
Prioritizing the Next Column for Maximum Impact
If your "Now" column is all about the team's immediate, tactical commitments, the "Next" column is where your strategic vision starts to take shape. This isn't just a parking lot for good ideas; it’s the on-deck circle for validated, high-impact initiatives you'll tackle the second your team has capacity.
Mastering this column is what separates proactive, career-making PMs from those who just manage a backlog. It's about turning a dozen potential projects into a strategic, sequenced plan that actually pushes the business forward.
Your goal for the "Next" column is simple: have a short, ranked list of initiatives—usually 3 to 5 big items—that have already been vetted for both business value and customer impact. These are the problems you've already decided are the most important ones to solve after the current work wraps up.
Applying Prioritization Frameworks in the Real World
To build a "Next" column that you can actually defend, you need to get past gut feelings and lean on a structured framework. One of the most effective and straightforward models is RICE scoring. It forces you to get systematic about four key variables for every potential initiative:
- Reach: How many users will this feature actually impact over a specific period? (e.g., 5,000 users per month)
- Impact: How much will this move the needle on our main metric? (Keep it simple: 3 for massive impact, 2 for high, 1 for medium, 0.5 for low)
- Confidence: How sure are you about your Reach and Impact numbers? (100% for high confidence, 80% for medium, 50% for low)
- Effort: How much time will this really take from product, design, and engineering? (Estimate this in "person-months")
The final RICE score is calculated with a simple formula: (Reach x Impact x Confidence) / Effort. This gives you a clear, quantifiable way to compare wildly different ideas.
Example in Action: A Fintech PM's Choice
Let's make this real. Imagine you're a PM at a fintech startup. Your backlog has two major initiatives competing for a spot in the "Next" column:
- New Payment Integration: Adding a popular new payment method.
- UI Enhancements: A series of small tweaks to improve the dashboard experience.
Using a RICE scoring template, your analysis might look like this:
| Feature | Reach (users/mo) | Impact (0.5-3) | Confidence (50-100%) | Effort (person-mo) | RICE Score |
|---|---|---|---|---|---|
| New Payment Integration | 2,000 | 3 | 80% | 4 | 1200 |
| UI Enhancements | 10,000 | 0.5 | 100% | 2 | 2500 |
Surprise! The UI enhancements come out on top, even with a much lower individual impact score. The reason is simple: the reach is 5x higher and the effort is half, making it a far more efficient way to deliver value across your entire user base. This is the kind of data-driven approach that helps you justify your decisions to leadership.
If you want to go deeper, we've got a complete guide on how to prioritize a roadmap that really breaks down these techniques.
Leading Prioritization Meetings with Data
Your RICE score is the starting line, not the finish line. The real magic happens when you bring this data into your prioritization meetings. Don't just show up with the scores; tell the story behind them.
The most effective PMs I've hired are storytellers who use data as their source material. They come to meetings armed not just with spreadsheets, but with qualitative evidence that breathes life into the numbers.
This means digging into tools like Gong to find direct quotes from sales calls where prospects specifically asked for a feature. It means using data from Pendo to show exactly where users are dropping off in a workflow you plan to fix. When you can confidently state, "30% of our enterprise prospects mentioned this integration in the last quarter," your argument becomes pretty hard to refute.
This kind of forward-looking prioritization is critical for staying relevant. According to Deloitte's comprehensive analysis, global IT spending is projected to grow substantially, driven by demand for AI and cloud infrastructure. Understanding these larger market trends helps you shape what goes into your "Next" and "Later" columns, ensuring your product doesn't just solve today's problems but is also ready for tomorrow's opportunities.
By blending quantitative frameworks with qualitative data and a sharp awareness of the market, you build a now next later roadmap that is not only strategic but also deeply connected to what your customers actually need.
Managing the Later Column as a Strategic Backlog
The "Later" column is easily the most misunderstood—and abused—part of the Now-Next-Later roadmap. All too often, it morphs into a messy, infinite backlog. It becomes a dumping ground for every random feature request from a sales call or a stray "wouldn't it be cool if…" idea. That’s a huge mistake.
Instead, think of your "Later" column as your strategic opportunity fund. This isn’t a junk drawer. It’s where you capture big ideas, potential market shifts, and ambitious bets without prematurely committing precious engineering time. It’s your long-term vision board, designed to keep your "Now" and "Next" columns razor-sharp and focused.
Turning Noise into Strategic Themes
Your first job here is to play triage nurse. Ideas will come flooding in from support tickets, competitive analysis, and customer feedback. Don't just list them out. Your real role is to synthesize all that raw input into powerful thematic buckets.
A single request for "better reporting" is weak and easy to dismiss. But once you start grouping related feedback, you can form a compelling theme like "AI-Powered Predictive Analytics" or "Self-Service Enterprise Dashboards." These are the kinds of strategic initiatives that belong in "Later."
Here’s what this looks like in practice:
- Raw Requests: "Can we export to Google Sheets?", "I need more filter options," "Can I schedule a weekly report?"
- Strategic Theme: Advanced Reporting & Automation Suite
- Raw Requests: "Can the app suggest what to do next?", "I wish it knew my preferences," "Competitor X has smart recommendations."
- Strategic Theme: AI-Powered Personalization Engine
- Raw Requests: "Do you support GDPR?", "We need French language support," "Can we process payments in Euros?"
- Strategic Theme: European Market Entry Readiness
This approach immediately elevates the conversation from small, tactical features to significant, value-driven initiatives that actually align with the company's bigger goals.
Gracefully Saying Not Right Now
One of the most valuable skills a product manager can have is the ability to say "no," or more accurately, "not right now," without shutting down great ideas. Your "Later" column is the perfect tool for this. When a stakeholder brings you an idea that just doesn’t fit into your "Now" or "Next" priorities, you can frame the conversation like this:
"That's a fantastic idea, and I see the value in it. It's a bit too early for us to commit engineering time, but this is exactly the kind of strategic thinking we need. I'm adding it to our 'Later' column under the 'AI-Powered Personalization' theme so we can properly research and validate it in a future quarter."
This response does a few critical things. It validates the person's idea, shows you’re actively listening, and transparently explains where their suggestion fits into the broader product strategy. You turn a potentially contentious "no" into a collaborative "not yet."
From Later to Next: A Real-World Example
Ideas in the "Later" column shouldn't just sit there gathering dust. They're candidates for promotion. At one company I worked for, we had a card labeled "AI Content Suggestions" sitting in our "Later" column for almost a year. It was a cool concept, but the tech felt a bit out of reach and we didn't have the data to make it truly effective.
Then, two things happened in parallel. The market for AI tools absolutely exploded, and our internal data warehouse finally hit a critical mass of user behavior data. Suddenly, our "low confidence" idea had a clear path to becoming a high-impact feature. We spun up a quick proof-of-concept, the results were promising, and that card moved decisively from "Later" right to the top of our "Next" column.
This is exactly how the "Later" column is supposed to work—it holds valuable bets until the timing, technology, and business case all click into place. Major technology trends, which you can explore on long-term technology trends on Bain & Company's website, often start as "Later" items. Capturing these big-picture ideas early, even before they feel fully baked, is how you stay ahead of the curve.
Communicating Your Roadmap to Get Buy-In
A brilliant plan that lives only on your laptop is useless. Building a strategically sound Now-Next-Later roadmap is honestly just half the battle. The real test comes when you have to communicate it—inspiring action, creating alignment, and securing genuine buy-in from every corner of the organization.
https://www.youtube.com/embed/b4YVHTqQPk8
As a product leader, I can tell you that your career velocity is directly tied to how well you can articulate the "why" behind your plan. This isn't just about sharing a link to a document. It's about tailoring your message to connect with what each audience truly cares about.
Speaking the Language of Leadership
When you're in front of executives, you have to elevate the conversation from features to financials. Their minds are constantly on company OKRs, revenue targets, and market position. Your roadmap is simply a tool to show them how product is driving those outcomes.
Forget listing user stories. Instead, frame your "Now" and "Next" columns as direct answers to their biggest strategic questions.
- Instead of: "We're building a new checkout flow."
- Try: "Our 'Now' focus is a checkout redesign, which we project will reduce cart abandonment by 15% and directly contribute to our $2M Q3 revenue goal."
Tie every major initiative back to a specific business metric. If you really want to master this, understanding the principles of how to present to executives is non-negotiable. It teaches you how to build a narrative around impact. You need to draw a clear, logical line from the work your team is doing to the numbers the leadership team reports to the board.
Equipping Sales and Marketing for Success
Your sales and marketing teams are on the front lines. They need to speak confidently about the product's future, but without making promises the engineering team can't keep. The Now-Next-Later roadmap is perfect for this, but only if you arm them with the right talking points.
Give the sales team clear, simple scripts for handling questions from prospects about features that aren't available yet. Teach them how to use the "Next" and "Later" columns to build excitement and show a clear vision.
Sales Talking Point: "That’s a great question. While our engineering team is currently focused on [mention a key 'Now' item], improving our integration capabilities is a top priority you'll see in our 'Next' phase. We recognize how important that is for customers like you, and it's high on our list for the upcoming quarter."
This approach does a few things perfectly: it validates the customer's need, gives them a transparent (but non-committal) peek at your priorities, and pivots back to the value you're delivering today. It turns a potential "no" into a conversation about strategic direction.
Empowering Engineering with Purpose
Engineers build better products when they understand the why behind their work. Your roadmap is the single most powerful tool you have to connect their lines of code to real customer value.
So, when you're kicking off a new project from the "Next" column, don't just hand over a list of requirements.
Start that kickoff meeting by showing them the roadmap. Explain why this particular initiative was prioritized over everything else on the list. Share the customer feedback, the market data, or the business opportunity that pushed it to the top. When an engineer understands that the bug they're fixing is part of a "Now" initiative to boost user retention by 10%, their work suddenly has a much deeper meaning.
Choosing the Right Communication Strategy
Tailoring your communication isn't just about the words you use; it's about understanding what different teams need from your roadmap. Each group has a different goal and is susceptible to different misunderstandings. Thinking about this ahead of time can save you from a world of misalignment down the road.
Here's a quick breakdown of how to adapt your message for key stakeholders.
Roadmap Communication Strategy by Audience
| Audience | Primary Goal | Key Message Focus | Common Pitfall to Avoid |
|---|---|---|---|
| Executives | Strategic Alignment | Link initiatives directly to OKRs, revenue impact, and market share. Keep it high-level. | Getting lost in feature-level details or technical jargon. |
| Sales | Closing Deals | Provide clear, customer-safe talking points about "Now" and "Next" items. | Over-promising specific features from the "Later" column or giving hard deadlines. |
| Marketing | Building Narrative | Use "Now" for immediate campaigns and "Next" to build forward-looking excitement. | Announcing "Later" items publicly, which can create unmet customer expectations. |
| Engineering | Context & Purpose | Explain the "why" behind priorities—the customer problem and business impact. | Presenting the roadmap as a fixed list of demands without room for technical input. |
Ultimately, treating your now next later roadmap as a living communication artifact is the goal. By intentionally shaping your message for each audience, you transform your plan from a static document into a powerful engine for alignment that moves the entire organization forward together.
Common Questions About the Now-Next-Later Roadmap
As a product leader, I’ve seen firsthand how adopting a Now-Next-Later roadmap can bring amazing clarity and get a team genuinely excited. But I also know that shifting away from the comfort of date-driven plans brings up some tough, valid questions.
Let’s get into the most common ones I hear from PMs, along with some advice you can actually use today.
How Do I Handle Pressure for Feature Delivery Dates?
This is the biggest challenge PMs face, especially from sales or marketing teams who need to plan their own activities around your launches. It's a constant battle.
The key is to consistently shift the conversation away from "when" and towards "why" and "what." You have to resist the temptation to give a vague guess. We all know that even a whispered "maybe Q3" will be treated as a blood oath.
So, when a sales leader corners you asking for a date on something in your "Next" or "Later" column, frame your response around shared goals and transparency.
Your Response Framework: "I'm glad you're excited about that feature; we are too. It's prioritized in our 'Next' column because we agree it's critical for the enterprise segment. Right now, engineering is fully focused on delivering [mention a key 'Now' item], which addresses the performance issues impacting our largest customers. Once that's launched, we'll begin discovery and scoping for the new feature. I'll make sure to include you in that process."
This script does a few things really well. It validates their need, subtly reinforces the roadmap’s strategic purpose, and manages expectations without painting you into a corner with a date you can't guarantee. It's a collaborative deflection, not a stonewall.
What Is the Difference Between This Roadmap and a Gantt Chart?
This one comes up a lot. People try to use them interchangeably, and it's a recipe for frustration because they serve fundamentally different purposes. They're built to answer completely different questions.
A Now-Next-Later roadmap is a product management tool. A Gantt chart is a project management tool.
- A Gantt chart is all about execution. It answers the question, "When will this specific project be done?" It's focused on timelines, dependencies, and resource allocation for a project with a very clearly defined scope and end date. It's meant to be rigid.
- A Now-Next-Later roadmap is all about strategy. It answers, "What problems are we solving and in what order?" Its job is to communicate direction and priorities, intentionally leaving the timelines for "Next" and "Later" flexible so you can adapt as you learn new things.
Think of it this way: you might use a Gantt chart to manage the nitty-gritty execution of an initiative that's currently in your "Now" column. But the roadmap itself is your strategic North Star, not a project plan.
How Often Should I Update My Roadmap?
Your roadmap should be a living document, not some static artifact you create once a quarter and then forget about. The update cadence, however, isn't one-size-fits-all. It should be multi-layered to match the commitment level of each column.
-
Now Column (Continuous Update): This should be a real-time reflection of what your team is actively working on. It needs to align perfectly with your current sprint or development cycle. No excuses.
-
Next Column (Every 2-4 Weeks): I like to review and adjust this column frequently, often in sync with sprint planning or monthly business reviews. This is where you pull in the next highest-priority item as engineering capacity frees up. It keeps the momentum going.
-
Later Column (Quarterly Review): The "Later" column is your long-term vision, so it requires a more strategic, high-level review. Revisit it each quarter with your leadership team to make sure it still aligns with company OKRs and what's happening in the market.
This layered approach ensures your roadmap is both tactically relevant day-to-day and strategically aligned over the long haul. It transforms it from a simple document into a powerful tool for actually driving your product forward.
Ready to dive deeper into product strategy and accelerate your career? In my newsletter, Aakash Gupta provides actionable insights, frameworks, and career advice from over 15 years of product leadership experience. Join the largest community of PMs in the world at https://www.aakashg.com.
