From Chaos to Clarity: The Now-Next-Later Roadmap Guide

Planning a project doesn't just require you to list every task, step, and milestone. It demands flexibility and accountability for unexpected changes along the way. The traditional deadline-oriented approach doesn't always cater to the reality of the situation. That's where the Now-Next-Later roadmap comes in.

This strategic planning tool is often used in product development but can be applied to many other types of projects. It helps prioritize tasks and initiatives without taking away flexibility. The Now-Next-Later approach allows you to understand the focus, evaluate upcoming priorities, and build long-term plans.

This guide can help you understand the Now-Next-Later framework and figure out how to implement it for your initiatives.

A Now-Next-Later roadmap is a visual framework that organizes tasks and initiatives into three clear categories:

• What needs immediate attention (Now)

• What comes after (Next)

• What is further down the road (Later)

It was created by Janna Bastow to battle the strict deadline-oriented project frameworks.

This framework differs from traditional project roadmaps because it doesn't tie tasks strictly to deadlines. Instead, it focuses on the sequence of priorities, which allows for more flexibility.

A Now-Next-Later roadmap simplifies planning by breaking down tasks into clear phases of action. It encourages teams to focus on the most important tasks first while maintaining a high-level view of the overall project trajectory.

To create this roadmap, you need three lists: Now, Next, and Later.

Now

In this list, you place tasks that your team needs to work on immediately. These are the top priorities and demand your full attention.

This list might include tasks that are near completion or that need to be addressed now to keep the project moving. The highly transparent "Now" category keeps everyone focused on the most pressing work without getting distracted by future tasks.

Next

This section covers the tasks that follow the Now items. These are the next most important steps to take once the current priorities are complete.

When you have a well-defined "Next" category, your team has time to prepare and gather resources without diverting attention from the tasks at hand. It helps manage expectations for stakeholders and creates a smooth transition to the next set of tasks.

Later

This part focuses on long-term initiatives that must be done in the future but aren't urgent. These low-priority tasks will eventually need the team's attention but don't have to loom over them while they are focusing on "now."

In short, the "later" category prevents these long-term goals from getting lost while still keeping the team focused on the more immediate work.

With so many project planning tools and roadmaps, you might wonder why you need another one.

Key benefits of implementing the Now-Next-Later roadmap include:

Transparent prioritization

The Now-Next-Later roadmap helps teams focus on what matters most without getting bogged down by a long list of tasks. Instead of juggling multiple jobs at once (as often happens in product development), teams can direct their attention to the "Now" tasks and then naturally progress to other items.

This structure reduces decision fatigue and keeps the team's energy directed toward urgent matters.

Flexibility for changing priorities

Traditional roadmaps tied to strict deadlines can become volatile when unexpected issues arise. The Now-Next-Later framework allows you to move tasks from one category to another without changing the outcome. This helps your team remain agile and responsive without the accompanying stress.

Clear communication

The simple and visual nature of a Now-Next-Later roadmap promotes better communication within teams. The clear breakdown of tasks allows team members to remain on the same page and gives additional clarity to stakeholders.

Improved productivity

By limiting the number of tasks in the Now section, the team can concentrate its efforts on completing current priorities before moving on to the next phase. This minimizes the temptation to multitask or shift focus prematurely. The natural workflow supported by the framework contributes to higher productivity.

Long-term vision

One of the key benefits that make the Now-Next-Later approach stand out from traditional project planning is the long-term vision. It keeps the long-term priorities on the agenda without being pushy about achieving them immediately. Teams work on the pressing tasks without feeling disconnected from the larger picture.

Improved resource allocation

The Now-Next-Later framework supports more effective resource management. Since you have a clear understanding of what must be done now and what can wait, you can easily allocate a suitable budget.

This approach also allows you to anticipate upcoming resource demands (in the next section) and prevent waste.

While highly beneficial, the Now-Next-Later roadmap comes with certain downsides. They include:

• Lack of time frames: without deadlines, progress tracking becomes difficult

• Oversimplification: complex projects may not fit neatly into three categories

• Limited long-term visibility: focus on current tasks can obscure long-term strategy

• Unclear prioritization: teams may struggle to determine what moves from "Next" to "Now."

This framework may not be suitable for every team and project. However, it could still be an excellent secondary roadmap that complements traditional project planning approaches.

The Now-Next-Later roadmap can be easier to create than traditional project roadmaps. Let’s look at the key steps to implementing this approach.

Define what now, next, and later mean for the project

Now," "Next," and "Later" can vary depending on the context. Defining them will create the foundation for the entire roadmap.

In some projects, "Now" could mean tasks that must be completed within the week. In other cases, it could mean tasks that have to be done in the current quarter.

Similarly, "Next" could represent initiatives you plan to tackle within the next few weeks or months, depending on the overall timeline.

"Later" might refer to long-term goals that won't be addressed for months or even years.

List your tasks

After defining categories, begin listing all the initiatives, features, or validated ideas from your product discovery process. This could include everything from customer-driven feature requests to internal process improvements.

At this stage, you're not worried about the order or priority of the tasks. You’re simply making sure you capture all ideas that could potentially impact the project.

Prioritize your tasks

This involves evaluating each task based on two primary factors:

• How important is this initiative to your end users?

• How urgently does this initiative need to be completed?

Consider the overall impact of each task. Does it solve a key customer pain point? Are there market pressures that require specific initiatives to be tackled immediately?

Categorize your tasks

After prioritization, you can start categorizing your initiatives into the Now, Next, and Later categories.

• Now: Place the top-priority tasks in this category. These are the initiatives your team must focus on immediately. Important: Don't overload this category—keeping it lean ensures the team can work effectively without becoming overwhelmed.

• Next: The tasks in "Next" are the ones you've already identified as important, but they don't need immediate attention. These should remain visible to the team because they might require preparation.

• Later: The "Later" category includes long-term initiatives. These are items that will be worked on eventually but don't require focus in the near future.

While categorization is important, it's not set in stone. You can make changes to the map in the future.

Leverage tools to create your final roadmap

Using special tools can help you create a shareable roadmap, which can be easy to adjust along the way. Here are some tools you can use to bring your roadmap to life:

• Trello

• Asana

• Monday.com

• Notion

• Miro

Each of these tools can help you keep the roadmap visible. You can also use internal communication systems to share the framework.

Here is a basic Now-Next-Later roadmap template for a food delivery app development project:

Now

• Conduct market analysis and user surveys to identify core needs

• Define key features and user personas (e.g., customers, delivery partners, restaurants)

• Develop features (basic order placement, restaurant selection, menu browsing)

• Set up foundational APIs for user registration, login, and order processing

• Arrange database setup for restaurants, customers, orders, and payments

• Implement initial integration with a reliable payment processor

Next

• Implement real-time tracking for deliveries (geolocation services)

• Add customer reviews and ratings for restaurants and delivery partners

• Optimize server performance for handling large order volumes

• Implement multi-factor authentication for users and partners

• Launch digital marketing campaigns to build a user base (social media, influencer marketing)

• Implement referral programs for customers and restaurants

Later

• Build machine-learning algorithms for personalized restaurant and meal recommendations

• Integrate digital wallets and cryptocurrency payment options

• Add multi-language support and adapt the app for global markets

• Integrate with third-party apps (fitness, calorie trackers) and loyalty programs

• Implement eco-friendly delivery options (bike delivery, electric vehicles)

You can break down the tasks in each category into separate subcategories. This can help with delegating tasks to relevant teams and departments.

The Now-Next-Later roadmap is an excellent project planning tool. It can take teams away from strict deadlines and give them more room to maneuver. Building this roadmap can speed up project execution, save money, and improve transparency. However, it can sometimes be challenging to implement.

While not all teams can benefit from this framework, for many it can be a useful alternative to the traditional project-mapping approach.