A now-next-later roadmap groups product work by how close the team is to acting on it. It helps customers understand what you are working on, what you are investigating next, and which longer-term problems are still uncertain. The labels need an explanation: a customer may otherwise read “Next” as a delivery promise for the next release.
ProdPad's explanation of the format describes the columns as confidence horizons. Work becomes more concrete as the team learns. A practical customer-facing version should make that uncertainty visible while giving people enough detail to discuss their needs.
Define the columns before adding cards
Publish a short description of what each column means for your team. For example:
- Now: work the team is actively delivering or testing with users.
- Next: problems being investigated for a future delivery decision.
- Later: relevant opportunities that still need evidence, scope, or capacity.
These descriptions are an example policy. Use wording that matches your process. If your team does no discovery on items in Next, call them candidates and explain when you will review them.
Avoid putting a calendar month behind each label unless you are ready to maintain those dates. Moving an item from Next to Later then looks like a broken promise, even if the team only intended to show a changing priority.
A worked roadmap for a reporting product
Imagine a small team building software that helps account managers prepare weekly client reports. Customers complain about manual preparation and difficulty explaining changes in the numbers. Here is a fictional roadmap built around those tasks:
| Horizon | Customer problem | Current plan | Evidence still needed |
|---|---|---|---|
| Now | A failed import makes people rebuild their report | Preserve the draft and identify invalid rows | Check the fix with people who reported the failure |
| Next | Weekly reports require repeated manual setup | Investigate reusable report settings | Observe which settings people reuse and which change |
| Later | Readers cannot explain a sudden metric change | Explore ways to add context to reports | Learn whether notes, comparisons or another approach helps |
The Now item has a specific change the team can test. Next names a direction while leaving the design open. Later describes a problem worth understanding without committing to a solution.
Compare that with cards named “Import v2,” “Templates,” and “AI insights.” Those labels may be convenient internally, but customers have to guess what will change for them. A sentence about their task gives them something they can confirm or correct.
Write a card that invites useful feedback
A public roadmap card can stay short. Include the affected audience, the problem, and what the team currently knows. Add a focused question when a decision would benefit from customer input.
For the report-settings example, a card could say:
Account managers repeat the same report setup each week. We are investigating which settings could be reused safely. If you prepare recurring reports, which details stay the same and which do you change for every client?
The question asks about a real workflow. “Would you like templates?” would be easier to answer, but a yes would tell you little about what to build.
Keep sensitive context private. A public card should not reveal a customer's revenue, contractual terms, security details, or identifying support conversation. Link to the appropriate public request and retain confidential evidence in an access-controlled place. Our guide to public and private product roadmaps explains how to choose the audience.
Decide what moves an item forward
Review each proposed move using the same questions. Is the problem relevant to the current product goal? Do you understand who experiences it? Is there a feasible next step? Does the team have capacity to act?
For a Later item, a few customer conversations might reveal that the initial framing was wrong. “Add notes to charts” could turn out to mean “help a reviewer understand why this week's result differs from last week's.” The revised problem may suggest a simpler solution.
Before moving an item into Now, agree on what you will deliver or test and how you will tell whether it helped. Where several candidates compete for capacity, a RICE scoring exercise can expose the assumptions behind the choice. It does not replace a check of prerequisites or commitments.
Explain changes without rewriting history
Suppose reusable report settings move out of Next because an import failure affects existing customers. Update the card with a brief explanation. Keep the discussion available so people can see both their original input and the changed decision.
An update could say: “We are prioritizing the import recovery work before reusable settings. We have kept your examples and will use them when we return to this investigation.” Use that statement only if the examples are actually retained and the team intends to revisit the work.
If the team has decided not to pursue an idea, make that decision explicit. Leaving it in Later indefinitely creates a misleading expectation and makes the roadmap harder to read. Explain the reason and any available alternative, without promising that every declined request will return.
Keep delivery dates where they are useful
Some work has a real deadline: a contractual integration, a migration window, or an event the team has committed to support. Record those dates and their owners in the delivery plan. A now-next-later roadmap does not remove the need to manage them.
When a date is firm enough to share publicly, explain what is included and who it applies to. A limited beta date and a general release date answer different questions. Customers should be able to tell which one they are reading.
After release, connect the completed roadmap item to a changelog entry that explains how to use the change. People who followed the request can then find the result without searching through unrelated announcements.
Give the roadmap an owner
Choose someone responsible for keeping the customer-facing explanation aligned with the team's decisions. Review it when priorities change and before sharing it in a customer conversation. A brief regular check is also useful for spotting cards with stale wording or no clear next step.
Productroad roadmaps let teams share planned work alongside feedback. Choose statuses that match how your team makes decisions, and check which customers can see each roadmap before sharing it.
Productroad helps you collect user feedback, prioritize it, make a roadmap of a project and inform customers via changelog about new cool features.



