Reprioritizing and Moving Items Across Horizons in Now Next Later Agile
This skill teaches you how to run regular, disciplined reviews that promote, demote, or remove items between the Now, Next, and Later horizons so your roadmap stays aligned with reality instead of decaying into a stale wish list.
Run a structured review cadence, typically every two weeks for Now and monthly for Next and Later. For each item, evaluate whether new evidence, shifting strategy, or resource changes justify promoting it forward, demoting it back, or removing it entirely. Apply your predefined graduation criteria, document the rationale for every move, and communicate changes to stakeholders immediately so downstream teams can adjust.
Outcome: Your roadmap becomes a living document that reflects current strategic reality. You gain a repeatable review process that catches stale items, surfaces emerging priorities, and ensures the team is always working on the highest-value work available.
Prerequisites
- A populated Now-Next-Later roadmap with items already categorized across horizons
- Defined graduation criteria for what qualifies an item to move between horizons
- Basic familiarity with the Now-Next-Later Framework and its time horizons
- Access to recent customer feedback, usage data, or strategic updates that inform priority shifts
Overview
A now next later agile roadmap is only as good as the last time someone seriously questioned whether every item is still in the right place. Without regular reprioritization, your carefully categorized horizons degrade. Later items that should have moved to Next sit neglected. Now items that lost their urgency block higher-value work. New opportunities never find a home. The roadmap becomes a museum of past decisions rather than a tool for current ones.
Reprioritizing across horizons is the discipline of running structured reviews that evaluate every item against current evidence, then deliberately promoting, demoting, or removing items between Now, Next, and Later. This skill sits at the operational core of the Now-Next-Later Framework. Where categorizing items is the initial sorting, and defining graduation criteria sets the rules, reprioritization is the ongoing enforcement mechanism that keeps the framework honest. Without it, the framework is just a one-time exercise.
The concrete artifact you produce is a revised roadmap with a changelog: which items moved, in which direction, why, and what triggered the change. Over time, these changelogs become a decision log that helps teams learn their own patterns. You start to notice that Later items related to a specific customer segment consistently get promoted, which signals strategic gravity. You spot Now items that keep getting deferred, which signals false urgency or scope creep. The review itself becomes a lightweight strategic conversation, not just a backlog grooming session.
Success looks like a roadmap where no item has sat unchanged for more than two review cycles without someone explicitly affirming its position. If every item on your roadmap has been actively evaluated in the last 30 days, you have a living roadmap. If items are sitting in the same horizon they were placed in three months ago with no re-examination, you have a poster.
How It Works
Reprioritization works because it treats the roadmap as a hypothesis document, not a commitment register. Each item in a horizon is a bet: "Given what we know today, this item belongs here." New information constantly arrives, including customer feedback, market shifts, competitor moves, engineering discoveries, leadership changes, and budget adjustments. The review process is the mechanism that converts new information into roadmap changes.
The mental model is a three-lane highway with on-ramps and off-ramps between lanes. Items enter Later as exploratory ideas with low certainty. As evidence accumulates, like validated customer demand, a completed technical spike, or a strategic mandate, items earn promotion to Next. From Next, items move to Now when they are scoped, staffed, and ready for immediate execution. But the highway runs in both directions. A Now item can get demoted back to Next if its dependencies fall through, if a higher-priority emergency arrives, or if early execution reveals the problem was misunderstood. Items can also exit the highway entirely when they are no longer relevant.
The key insight is that promotion and demotion are not the same cognitive operation. Promotion is relatively natural, as teams want to advance work and it feels like progress. Demotion is psychologically difficult because it feels like admitting a mistake or disappointing a stakeholder who was promised the work. This asymmetry is why structured reviews matter. Without a formal process, teams over-promote and under-demote, which leads to a bloated Now column and stalled execution. A good review forces explicit demotion decisions by asking "Does this still deserve to be here?" for every item, not just the ones someone raises a flag on.
The review cadence should match the decision velocity of each horizon. Now items change fastest, so they need the most frequent review, typically every sprint or every two weeks. Next items change at a slower pace and benefit from monthly review. Later items are strategic and shift quarterly or when a significant strategic event occurs. This tiered cadence prevents review fatigue while ensuring no horizon goes unexamined for too long.
Reprioritization also depends on having clear graduation criteria defined in advance. Without criteria, every review becomes a debate about values rather than an evaluation of evidence. With criteria, the conversation becomes diagnostic: "Has this item met the conditions we agreed would justify moving it?" The criteria turn subjective opinion into structured assessment, which is what makes the review scalable across teams and repeatable over time.
Step-by-Step
Step 1: Gather fresh inputs before the review
Before any review meeting, collect the new information that has arrived since the last cycle. This includes customer feedback summaries, analytics dashboards showing usage or engagement changes, notes from sales or support calls, updates from engineering on technical feasibility or blockers, and any strategic communications from leadership. The goal is to have the evidence ready so the review conversation is data-informed, not opinion-driven. Assign one person, typically the product manager or roadmap owner, to prepare a brief summary of the most significant changes.
This summary does not need to be a formal document. A bulleted list of 5-10 notable signals is enough. The key constraint is that this gathering happens before the meeting, not during it, so the review time is spent on decisions rather than information discovery.
Tip: Set up a simple shared doc or Slack channel where team members can drop relevant signals throughout the sprint. By review day, you already have your inputs collected passively instead of scrambling to recall what changed.
Step 2: Review the Now horizon first
Start with Now because it represents your active commitments and has the highest cost of misalignment. For each item in Now, ask three questions: Is this still the highest-priority thing we could be doing? Are we making expected progress, or has something stalled? Has any new information changed the value or feasibility of this item?
Items that are progressing well and still strategically aligned stay in Now with no action needed. Items where progress has stalled due to external dependencies, scope changes, or resource conflicts should be evaluated for demotion back to Next. Items that have been completed or shipped should be removed and archived with a completion note. Be ruthless about Now.
This horizon should contain only work that the team is actively executing or will begin within the current sprint cycle. If an item has been in Now for more than two sprints without meaningful progress and no clear path to unblocking, it needs to move.
Tip: Count the items in Now before and after every review. If the count is growing sprint over sprint, you have a prioritization problem. A healthy Now column stays roughly constant in size, matching the team's actual throughput capacity.
Step 3: Review the Next horizon for promotion and demotion candidates
Next is your staging area, so the primary question here is: has any item earned promotion to Now, or has any item lost its justification for being this close to execution? Walk through each item and check it against your graduation criteria. An item ready for Now typically has validated demand, a clear scope, available resources, and no unresolved blockers. An item that should demote to Later might have lost its strategic urgency, had its supporting data invalidated, or been overtaken by a newer, higher-priority initiative.
Also look for items that entered Next prematurely, often because a stakeholder pushed for them without sufficient evidence. These items should be moved back to Later with a clear note about what evidence would justify revisiting them. For items staying in Next, update their status notes to reflect any new information so the next review cycle starts from an accurate baseline.
Tip: When promoting from Next to Now, always pair the promotion with a capacity check. If your Now column is already full, something else in Now must be demoted or completed first. Promotion without capacity discipline leads to overcommitment.
Step 4: Review the Later horizon for emerging priorities and dead items
Later reviews happen less frequently, often monthly or quarterly, because these items are exploratory and strategic. The review should focus on two actions: identifying items that have accumulated enough evidence to promote to Next, and pruning items that are no longer relevant. For potential promotions, check whether any Later item has gained new supporting data since the last review, such as a customer segment requesting the capability, a competitor launching something similar, or a technical enabler becoming available. For pruning, look for items that have been in Later for more than two or three review cycles without any new supporting evidence.
These are likely ideas that sounded good at the time but have not attracted any gravitational pull. Remove them. A bloated Later column makes it harder to spot the items that actually matter. Archive removed items rather than deleting them so you can revisit if circumstances change, but get them off the active roadmap.
Tip: Before each Later review, sort items by date added. Anything older than 6 months with no new evidence attached is a strong candidate for removal. Age without evidence is a reliable signal of low actual priority.
Step 5: Apply graduation criteria consistently
For every item you consider moving, evaluate it against the predefined graduation criteria your team established. These criteria typically include dimensions like customer demand evidence, strategic alignment, technical feasibility, resource availability, and business impact potential. Score or assess each dimension explicitly rather than relying on gut feeling. The goal is to create a brief, documented justification for the move.
This does not need to be elaborate. A sentence or two per dimension is sufficient. For example: "Customer demand: 3 enterprise accounts requested this in Q2. Technical feasibility: spike completed, estimated at 2 sprints.
" If an item does not meet the criteria threshold, it stays where it is regardless of how enthusiastic a stakeholder might be. The criteria exist precisely to prevent enthusiasm from substituting for evidence.
Tip: Keep a lightweight scorecard template that you fill in for every promotion decision. Over time, these scorecards become a decision log that helps calibrate your criteria. If items that scored high on your criteria consistently succeed after promotion, your criteria are well-tuned.
Step 6: Document every move with rationale
For every item that changes horizons or gets removed, record three things: what moved, where it moved (from and to), and why. The "why" is the most important part. It captures the reasoning and evidence behind the decision, which serves multiple purposes. It creates accountability, so stakeholders can understand the logic even if they disagree.
It builds institutional memory, so future reviews can reference past decisions. And it enables pattern recognition, so the team can identify recurring themes like a particular customer segment consistently driving promotions, or a particular type of initiative consistently getting demoted. Store these changelogs alongside the roadmap itself, whether that is in a dedicated section of your roadmap tool, a linked document, or a simple version history. The format matters less than the habit.
A team that documents its reprioritization decisions for six months will have a rich dataset about what actually drives their product direction.
Tip: Use a simple format: "[Date] Moved [Item] from [Origin] to [Destination]. Reason: [1-2 sentences]." This takes under a minute per item and pays dividends when a stakeholder asks "Why did we drop Feature X?" three months later.
Step 7: Communicate changes to stakeholders immediately
Once the review is complete and items have been moved, communicate the changes to all stakeholders who care about the affected items. Do not wait for the next scheduled roadmap share. Delays create information asymmetry where the team is working from an updated roadmap but stakeholders are making decisions based on the old one. The communication should be brief and specific: what changed, why, and what it means for their priorities.
For promotions, frame them positively, as the team advancing work that has earned its place. For demotions, be direct about the reasoning without being defensive. For removals, explain what would need to change for the item to return. Use the stakeholder communication practices you have established to deliver this in the right format for your audience, whether that is a Slack message, an email summary, or an update in your roadmap tool.
Tip: Create a template for post-review communications that includes: items promoted (with rationale), items demoted (with rationale), items removed (with conditions for return), and items staying put that stakeholders frequently ask about. Proactively addressing the "what about X?" questions prevents a round of follow-up conversations.
Step 8: Set the cadence for the next review
At the end of each review, confirm the date and scope of the next review. For Now items, this is typically every two weeks, aligned with sprint boundaries. For Next items, monthly reviews are common. For Later, quarterly or triggered by strategic events.
If you are early in adopting the now next later agile framework, consider running all three reviews together in a single session until the team builds the muscle. As the team matures, separate the cadences so each review can be appropriately deep. Add the next review to shared calendars with a pre-meeting reminder for the input-gathering step. The single biggest risk to a review cadence is letting one review slip, which makes the next one harder because more has changed, which makes it more likely to slip again.
Protect the cadence like you protect sprint ceremonies.
Tip: If your team is remote or distributed, time-box the review tightly: 30 minutes for Now, 30 minutes for Next, and 20 minutes for Later (when applicable). Without a time constraint, reviews expand to fill available time and become dreaded rather than useful.
Examples
Example: Early-stage SaaS startup with a 6-person team
A B2B SaaS startup has 12 items on their roadmap: 3 in Now, 4 in Next, and 5 in Later. The team ships biweekly. They recently received feedback from their top 3 paying customers all requesting the same integration that currently sits in Later. Meanwhile, one of the Now items (a dashboard redesign) has stalled for two sprints because the designer left the company.
During the biweekly review, the PM starts with Now. The dashboard redesign has been blocked for two sprints with no design resource available for at least 4 more weeks. This item is demoted to Next with the note: "Blocked on design hire. " This opens a Now slot.
Moving to Next, the PM checks which items meet graduation criteria. The integration requested by 3 top customers is examined. It was in Later, but the PM pulls it into the discussion because of the strong new evidence. It scores well: validated demand from paying customers representing 40% of MRR, technical spike completed last month (2 sprint estimate), and direct alignment with the retention strategy.
The team promotes it to Now, filling the slot freed by the dashboard demotion. The PM also identifies a Next item (email notification preferences) that has been sitting there for 10 weeks with no new supporting evidence. It is demoted to Later. The changelog is posted to the team Slack channel within the hour, and the customer success manager is alerted that the integration is now in active development so she can update the requesting customers.
Example: Mid-size B2B company with multiple product teams
A company with 4 product squads runs a combined roadmap with approximately 50 items across horizons. Each squad manages their own Now (3-5 items each), but Next and Later are shared. The company just completed annual planning, which shifted the strategic priority from growth to retention. Several Now items were approved under the old growth-first strategy.
The head of product calls a special triggered review (outside the normal cadence) because the strategy shift is a significant event. The review starts with a re-evaluation of all Now items against the new retention-first strategy. Three items across two squads were growth-focused: a new onboarding flow for trial users, a freemium tier expansion, and a viral sharing feature. The onboarding flow still has retention value (better onboarding reduces churn), so it stays in Now with an updated rationale.
The freemium expansion is demoted to Later because it directly contradicts the focus on converting existing users. The viral feature is demoted to Next because it has partial retention value through network effects, but it is not the highest priority under the new strategy. These three moves free up capacity for retention-focused items. Two items are promoted from Next to Now: a customer health scoring system (strong engineering readiness, directly supports retention) and an in-app feedback widget (customer demand from 12 support tickets in the last month).
The review produces a detailed changelog that the head of product presents at the all-hands, framing the changes as a natural consequence of the strategic shift rather than a repudiation of past decisions.
Example: Consumer mobile app with fast iteration cycles
A consumer app ships weekly and has a roadmap with about 25 items. The team runs weekly Now reviews and monthly Next/Later reviews. Usage analytics from the latest release show that a feature shipped two weeks ago (dark mode) drove a 15% increase in evening session length, validating a hypothesis about user engagement patterns. Meanwhile, a planned performance optimization in Now is showing diminishing returns after 3 weeks of work.
In the weekly Now review, the team evaluates the performance optimization. The first two weeks of work captured the easy wins, reducing load time by 40%. The remaining work targets an additional 10% improvement but requires significant architectural changes. The team decides to demote the remaining optimization scope to Next, as the law of diminishing returns makes it a poor use of the Now slot compared to alternatives.
The dark mode success triggers a promotion discussion about a related Later item: customizable themes. The dark mode data provides direct evidence that visual personalization drives engagement. The PM pulls the themes item into the monthly Next/Later review agenda, where it is promoted from Later to Next with the supporting data attached. Additionally, the team notices that a social sharing feature has been in Next for 6 weeks with zero new evidence since it was placed there.
The team demotes it to Later. The changelog is brief: 3 items moved, each with one sentence of rationale, shared in the team's standup the next morning.
Example: Enterprise platform with quarterly stakeholder commitments
An enterprise platform team has external commitments to key accounts. A Later item (SSO support) was on the roadmap as a future consideration. Two enterprise prospects worth a combined $800K ARR have now made SSO a requirement for signing. The sales team is pressuring the PM to put it in Now immediately. The current Now column is fully staffed with 4 items, all with committed delivery dates communicated to existing customers.
The PM resists the pressure to simply add SSO to Now without displacing anything. Instead, she runs an expedited review focused on this specific item. First, she evaluates SSO against graduation criteria: customer demand is strong ($800K ARR at stake), technical feasibility is moderate (estimated 3 sprints, requires identity provider research), and strategic alignment is high (enterprise expansion is a key OKR). SSO clearly meets the criteria for promotion.
The question is what it displaces. She reviews the 4 Now items: two have committed delivery dates to existing customers (cannot move without relationship damage), one is a compliance requirement with a regulatory deadline (cannot move), and one is a reporting feature requested by a single account worth $200K ARR. The reporting feature is the displacement candidate. The PM contacts the account manager for the reporting customer, explains the delay, and offers a workaround using CSV exports.
The reporting feature is demoted to Next with a target re-promotion in 6 weeks. SSO is promoted to Now. The full rationale, including the ARR comparison and the workaround offered, is documented in the changelog and shared with the sales VP and the affected account managers within 2 hours of the decision.
Best Practices
Separate the review from the grooming. Reprioritization reviews evaluate whether items are in the right horizon. Backlog grooming refines the details of items already committed. Mixing the two leads to a meeting that is half strategic and half tactical, and does neither well. Run the horizon review first, then groom the items that survived in Now during a separate session.
Enforce a "one in, one out" discipline for the Now column. Every time an item is promoted to Now, ask what it displaces. If nothing can be displaced, the promotion should wait. Teams that skip this step end up with 15 items in Now and a team that is context-switching across all of them, making meaningful progress on none. The constraint forces genuinely hard prioritization decisions.
Review items you are NOT moving, not just the ones you are. It is easy to focus the review on the items with obvious momentum. But the most dangerous items are the ones sitting quietly in Next or Now, consuming attention and commitment without anyone actively questioning them. At least once per review, explicitly affirm or challenge 2-3 items that have not moved recently.
Rotate the review facilitator across team members every 4-6 cycles. When the same person always runs the review, they develop blind spots and biases. Rotating brings fresh eyes that catch stale items the regular facilitator has normalized. It also builds shared ownership of the roadmap, reducing single-point-of-failure risk on the product manager.
Track the velocity of items through horizons as a health metric. Measure how long items spend in each horizon on average. If the average time in Next exceeds 8-10 weeks, items are stagnating rather than being actively developed or deprioritized. If items move from Later to Now in under 2 weeks, your team may be bypassing the staging process and reacting to urgency rather than evidence.
Keep a "graveyard" list of removed items with their removal rationale. This serves two purposes: it prevents removed items from being re-proposed without new evidence ("We removed this in March because X. What has changed since then?"), and it provides a useful record of ideas the team considered and deliberately rejected, which is as valuable as the list of ideas the team pursued.
Bias toward smaller, more frequent reviews rather than larger, less frequent ones. A 30-minute review every two weeks is dramatically more effective than a 3-hour review every quarter. The small review catches drift early, while the quarterly review discovers that half the roadmap is stale and requires a full day of re-sorting. Frequency reduces the magnitude of each individual change, which makes changes easier to communicate and absorb.
Common Mistakes
Only promoting items and never demoting or removing them
Correction
This is the most common failure mode and it stems from the psychological asymmetry between promotion and demotion. Promotion feels like progress, while demotion feels like failure or conflict. The result is a Now column that grows every cycle and a team that is spread across too many commitments. You can catch this early by tracking the net movement in each review: count promotions, demotions, and removals.
If your demotion count is consistently zero across three or more reviews, you are almost certainly avoiding hard decisions. Fix this by adding a structural requirement: every review must include at least one demotion or removal, even if it is a Later item that has aged out. The habit of removing normalizes the practice.
Treating the review as a debate instead of an evidence evaluation
Correction
Without predefined graduation criteria, reviews devolve into opinion contests where the most persuasive or senior person wins. You will notice this pattern when the same items get discussed for 10+ minutes without resolution, or when decisions reverse the following week when a different stakeholder is in the room. The fix is to anchor every movement decision to specific, observable evidence checked against your criteria. " If the answer is a feeling or a stakeholder request without supporting data, the item stays.
Over time, this trains the team to bring evidence to the review rather than opinions.
Running reviews on an inconsistent or ad-hoc schedule
Correction
Teams often start with good intentions on review cadence but let it slip when things get busy. Ironically, the busiest periods are when reviews are most valuable, because priorities are shifting fastest. A skipped review means the roadmap diverges from reality, which means people are working on the wrong things, which creates more urgency, which causes the next review to be skipped. You can detect this pattern if your last review was more than 3 weeks ago and no one noticed.
Prevent it by treating the review as a recurring calendar event with the same protection as a sprint demo or standup. If you must skip, immediately reschedule within the same week.
Moving items without updating dependent teams or stakeholders
Correction
A product manager might demote an item from Now to Next and update the roadmap tool, but forget to tell the engineering lead who was about to staff it, or the sales team who had been promising it to a prospect. This creates a trust gap that compounds over time. Stakeholders start ignoring the roadmap because they have been burned by silent changes, and instead rely on direct conversations with the PM, which does not scale. The fix is simple: build the communication step into the review process itself, not as a follow-up task.
The review is not complete until the changes have been communicated. Even a brief Slack message with the changelog is sufficient.
Using the review to add brand new items directly to Now
Correction
When a new idea or request surfaces during a review, there is a temptation to drop it straight into Now because it feels urgent. This bypasses the entire purpose of the horizon framework, which is to let items earn their way forward through accumulating evidence. New items should enter at Later or Next, depending on their maturity, and then be evaluated for promotion at the next review cycle. The only exception is a genuine emergency, like a critical production issue or a regulatory deadline, and even then, the emergency should displace something currently in Now, not simply be added on top.
If everything is an emergency, nothing is.
Reviewing all three horizons with equal depth every cycle
Correction
Teams that review Now, Next, and Later with equal rigor every two weeks experience review fatigue within a month. Later items change slowly and do not need biweekly examination. Treating them as if they do wastes time and dilutes attention from the Now and Next decisions that have immediate execution impact. Match review depth to horizon velocity: full review of Now every sprint, full review of Next monthly, full review of Later quarterly.
Between full reviews, only revisit a horizon if a significant event triggers it, such as a strategy pivot, a major customer win or loss, or a competitor launch.
Other Skills in This Method
Comparing Now-Next-Later to Quarterly and Timeline Roadmaps
When to choose a Now-Next-Later approach over traditional date-based or quarterly roadmaps, and how to transition between them.
Defining Graduation Criteria Between Horizons
How to establish clear criteria and confidence thresholds that determine when an initiative is ready to move from Later to Next, or from Next to Now.
Categorizing Items into Now, Next, and Later Horizons
How to evaluate and sort initiatives into the three time horizons based on certainty, urgency, and strategic alignment.
Building Now-Next-Later Roadmap Templates
How to set up visual roadmap templates in tools like Miro, Notion, ProductBoard, or spreadsheets to represent the three horizons effectively.
Applying Now-Next-Later Roadmaps to SaaS Products
How to adapt the Now-Next-Later framework for SaaS environments, including continuous delivery cycles, feature requests, and customer-driven prioritization.
Communicating Now-Next-Later Roadmaps to Stakeholders
How to present a timeline-free, horizon-based roadmap to executives, customers, and cross-functional teams without creating false deadline expectations.
Related Skills from Other Methods
Frequently Asked Questions
How often should I review each horizon in a now next later agile roadmap?
Review Now every sprint or every two weeks because these are your active execution commitments and misalignment here has immediate cost. Review Next monthly because these items change at a moderate pace as evidence accumulates. Review Later quarterly or when a significant strategic event occurs, such as a pivot, a major customer win or loss, or annual planning. If you are just starting out, review all three together in a single session every two weeks until the team builds confidence with the process, then separate the cadences.
What should I do when a stakeholder demands an item be promoted to Now without evidence?
Redirect the conversation to your graduation criteria. Ask the stakeholder to help you evaluate the item against the criteria dimensions: customer demand evidence, strategic alignment, technical feasibility, and resource availability. If the item does not meet the criteria, explain what evidence would need to exist for it to earn promotion. "). Document the conversation so it does not repeat at the next review.
Should I reprioritize across horizons before or after defining graduation criteria?
Define [graduation criteria](/skills/defining-graduation-criteria-between-horizons) first, even if the definitions are rough and preliminary. Without criteria, your reprioritization review becomes a subjective debate that resolves based on whoever argues most persuasively. Having even imperfect criteria gives the team a shared reference point. You can refine the criteria after 2-3 review cycles based on what you learn about which criteria actually predict success after promotion.
How do I handle items that keep bouncing between horizons?
An item that has been promoted and demoted more than twice is a signal that either the graduation criteria are poorly calibrated, the item's scope is unclear, or there is unresolved disagreement about its strategic value. Pull the item out of the regular review and run a dedicated 15-minute discussion focused exclusively on it. Clarify what would need to be true for this item to stay in Now permanently. If you cannot articulate clear conditions, the item likely belongs in Later until the strategic picture clarifies, or it should be removed entirely.
How do I keep the Later horizon from becoming a dumping ground for ideas nobody will ever build?
Apply a maximum age rule. Any item that has been in Later for more than two quarterly reviews (roughly 6 months) without accumulating new supporting evidence should be archived. This is not the same as rejecting the idea. Archiving preserves the item in your decision log so it can be retrieved if circumstances change. But it removes it from the active roadmap, which keeps Later focused on ideas with genuine strategic potential rather than aspirational clutter. A healthy Later column contains 8-15 items, not 50.
Can I use this reprioritization process with a Kanban board instead of a dedicated roadmap tool?
Yes. Map the three horizons to three columns or swimlanes on your board. The review process is identical regardless of tooling: walk through each column, evaluate items against criteria, move cards between columns, and document the rationale. Some teams use labels or tags instead of separate columns, which works as long as you can filter the view to see one horizon at a time during the review. The process is tool-agnostic. What matters is the cadence, the criteria, and the documentation habit.
Why does my roadmap keep drifting back to looking like a fixed timeline even after adopting now next later agile?
This usually happens when stakeholders or leadership pressure the team for delivery dates on Next and Later items. The team responds by attaching implicit timelines to horizons ("Next means next quarter"), which defeats the purpose of the framework. Combat this by reinforcing that horizons represent certainty and readiness, not calendar dates. " for Next and Later items. " The [stakeholder communication](/skills/communicating-roadmaps-to-stakeholders) skill covers techniques for setting these expectations.