How to Use Now Next Later Framework: Categorizing Items into Horizons
This skill teaches you how to evaluate product initiatives against certainty, urgency, and strategic alignment, then sort them into the three Now-Next-Later horizons so your roadmap reflects what your team should actually work on and in what sequence.
Evaluate each initiative against three dimensions: certainty (how well you understand the problem and solution), urgency (how time-sensitive the work is), and strategic alignment (how directly it supports current goals). Items scoring high on all three go into Now. Items with moderate certainty but clear strategic value go into Next. Items with low certainty or distant relevance go into Later. Reassess placement whenever new information arrives.
Outcome: A clearly categorized roadmap where every initiative sits in the right horizon, your team has immediate clarity on what to build first, and stakeholders can see the logical sequence of work without needing fixed delivery dates.
Prerequisites
- A backlog of product initiatives, features, or projects to categorize
- Understanding of your current product strategy and business objectives
- Familiarity with the Now-Next-Later Framework concepts (three horizons, sequence over deadlines)
- Access to stakeholder input or customer research that informs priority decisions
Overview
Categorizing items into Now, Next, and Later horizons is the core execution skill of the Now-Next-Later Framework. While the framework itself provides the structure, the real challenge is making the judgment calls that place each initiative in the right bucket. This skill teaches you how to evaluate initiatives systematically so your categorization decisions are defensible, consistent, and useful to everyone reading the roadmap.
The specific problem this skill solves is the paralysis that teams face when staring at a flat backlog of 30, 50, or 100 items and trying to figure out what matters most. Traditional prioritization frameworks like RICE or MoSCoW produce ranked lists, but ranked lists do not communicate time horizons, discovery status, or sequencing logic. Categorizing into Now, Next, and Later adds a dimension that pure ranking misses: the readiness of the work. An initiative might be critically important but poorly understood. It does not belong in Now. It belongs in Next or Later, where it can mature until it is ready. This readiness dimension is what separates horizon categorization from simple priority scoring.
The concrete artifact you produce is a categorized backlog where each item has a horizon assignment (Now, Next, or Later) and a brief rationale capturing why it landed there. This artifact feeds directly into your roadmap template (see Building Now-Next-Later Roadmap Templates) and becomes the foundation for stakeholder communication. When done well, the categorized backlog should feel obvious. Anyone reading it should nod and say, "Yes, that makes sense." When people disagree with the placement of an item, the rationale gives you a starting point for productive debate rather than circular arguments about what is "more important."
How It Works
The mental model behind horizon categorization rests on three evaluation dimensions that interact with each other: certainty, urgency, and strategic alignment. Understanding how these three dimensions combine is more important than memorizing rules for each horizon.
Certainty measures how well you understand the problem, the solution, and the expected outcome. High certainty means the team could start executing tomorrow with minimal ambiguity. You know what to build, you know why users need it, and you have reasonable confidence the solution will work. Low certainty means the problem is still fuzzy, the solution is speculative, or you lack the data to predict outcomes. Certainty is the dimension most teams underweight. They place speculative bets in Now because the idea feels exciting, then burn cycles on discovery mid-sprint. The framework corrects for this by making certainty an explicit input.
Urgency captures time sensitivity. Some items have external deadlines (regulatory compliance, contractual commitments, competitive threats). Others are important but not time-bound. Urgency is the easiest dimension to assess but also the most prone to inflation. Stakeholders routinely describe everything as urgent. Your job is to separate genuine time pressure from preference intensity. A helpful test: "What happens if we ship this three months from now instead of this month?" If the answer involves measurable damage (lost revenue, contractual penalties, customer churn), urgency is real. If the answer is "it would be annoying," urgency is low.
Strategic alignment measures how directly the initiative supports your current product strategy and business objectives. A feature might be certain and urgent but strategically misaligned, such as a one-off customization for a single enterprise client that pulls you away from your platform direction. High strategic alignment means the initiative moves the whole product forward. Low alignment means it serves a narrow need.
The three dimensions combine into horizon placement through a simple heuristic. Now items score high on all three: you know what to build, it needs to happen soon, and it directly serves your strategy. Next items typically have high strategic alignment and moderate-to-high certainty, but lower urgency, or high urgency and alignment but lower certainty that requires a discovery phase first. Later items have low certainty, low urgency, or unclear strategic alignment. They are not rejected. They are parked for future evaluation when new information arrives.
This model works because it matches how real product work flows. High-certainty, high-urgency, strategically aligned work is what your team can actually execute on right now. Everything else needs either more time, more research, or a strategic shift before it becomes actionable. The Now-Next-Later Framework simply makes this natural flow visible and explicit.
One important nuance: the three dimensions are not equally weighted, and the right weighting depends on your context. Early-stage startups should weight strategic alignment heavily because every initiative needs to advance the core value proposition. Mature products in competitive markets might weight urgency more heavily because competitive response matters. There is no universal formula, and that is by design. The framework gives you the structure. You supply the judgment.
Step-by-Step
Step 1: Gather and Clean Your Backlog
Start by assembling every initiative, feature, project, and request that could appear on your roadmap into a single list. Pull from your issue tracker, feature request logs, stakeholder wish lists, customer feedback databases, and your own strategic plans. Do not filter at this stage. Include everything, even items you suspect are low priority or poorly defined.
Each item needs a short description (1-2 sentences) that someone outside your team could understand. Remove exact duplicates but keep near-duplicates for now, because they often represent different angles on the same problem and collapsing them too early hides important nuance. The output of this step is a flat list of 20-100 items, each with a clear, jargon-free description.
Tip: If your backlog has more than 60 items, group them into rough themes first (e.g., onboarding, performance, billing, integrations). Categorizing theme by theme prevents decision fatigue and produces more consistent judgments than working through a random sequence.
Step 2: Define Your Current Strategic Context
Before evaluating any individual item, write down the strategic context that will anchor your decisions. This includes your top 2-3 business objectives for the current period, your product vision statement, any hard constraints (budget, team size, technical dependencies), and any external deadlines you already know about. Be specific. "Grow revenue" is not helpful.
"Increase annual contract value for mid-market accounts by 20% this year" is useful because it gives you a concrete yardstick for strategic alignment. If you are doing this exercise with a group, align on the strategic context before you start evaluating items. Disagreements about individual item placement often stem from unstated disagreements about strategy, and surfacing those early saves hours of circular debate.
Tip: Write the strategic context on a shared document or whiteboard where it stays visible throughout the session. When debate arises about a specific item, point back to the context. This simple physical reference resolves more arguments than any scoring formula.
Step 3: Score Each Item on Certainty
Work through your backlog and assign each item a certainty score: High, Medium, or Low. High certainty means the problem is validated (you have data from user research, analytics, or customer conversations), the solution is understood (you have designs, technical scoping, or a proven pattern), and the expected outcome is predictable. Medium certainty means you understand the problem well but the solution needs refinement, or you have a strong hypothesis but limited validation. Low certainty means the problem itself is ambiguous, the solution is speculative, or you are working from assumptions rather than evidence.
Score each item independently before discussing with your team. " The rationale is more valuable than the score itself because it makes your reasoning auditable.
Tip: Teams consistently overestimate certainty on items they are emotionally attached to. A useful corrective question: "Could an engineer start building this on Monday with the information we have right now?" If the answer is no, certainty is not High, regardless of how well you think you understand the problem.
Step 4: Score Each Item on Urgency
Assign each item an urgency score: High, Medium, or Low. High urgency means there is a concrete, external reason to act within the current planning cycle. This includes contractual deadlines, regulatory compliance dates, competitive launches that threaten your position, or a measurable cost of delay (such as a known rate of churn tied to the missing feature). Medium urgency means the initiative is important and the sooner the better, but there is no catastrophic consequence to a 2-3 month delay.
Low urgency means the initiative is valuable but not time-sensitive. It could ship next quarter or next year without meaningful negative impact. Be disciplined about separating urgency from importance. A strategically critical initiative can still have low urgency if there is no time pressure forcing action now.
Again, write a one-sentence rationale for each score.
Tip: When a stakeholder insists something is urgent, ask for the cost of delay in specific terms: lost revenue, contractual penalty, competitive displacement. If they cannot quantify or describe the cost, the urgency is likely Medium or Low, even if the stakeholder feels strongly.
Step 5: Score Each Item on Strategic Alignment
Assign each item a strategic alignment score: High, Medium, or Low. Reference the strategic context you established in Step 2. High alignment means the initiative directly advances one of your top 2-3 business objectives. You can draw a straight line from the initiative to a measurable strategic outcome.
Medium alignment means the initiative supports your broader product direction but is not directly tied to a current objective. It might become highly aligned if strategy shifts. Low alignment means the initiative is tangential to your current strategy. It might serve a niche segment, address a one-off request, or solve a real problem that is simply not a priority right now.
" Again, write a rationale for each score.
Tip: Watch for "strategy creep" where teams justify weak alignment by chaining multiple logical steps: "If we build this, then users will do X, which enables Y, which supports our goal Z." The longer the chain, the weaker the alignment. Direct support of a strategic goal requires one clear connection, not a Rube Goldberg machine of assumptions.
Step 6: Map Scores to Horizons
Now translate your three scores into horizon placement using this heuristic. Items with High certainty, High or Medium urgency, and High strategic alignment go into Now. These are the initiatives your team should be actively working on or about to start. Items with Medium or High certainty, any urgency level, and Medium or High strategic alignment go into Next.
These are candidates for the near-term once Now items clear, or once remaining discovery work completes. Everything else goes into Later, including items with Low certainty regardless of urgency or alignment, because they need more research before they are actionable. There will be edge cases where the scores are ambiguous (Medium on all three, for example). " If yes, it can be Now.
If no, it belongs in Next or Later.
Tip: Resist the temptation to put too many items in Now. A healthy Now horizon contains 3-6 initiatives for a team of 5-10 people. If your Now has 15 items, you have not actually prioritized. You have just renamed your backlog.
Step 7: Validate the Shape of Each Horizon
Step back and look at the overall distribution across horizons. A healthy categorization typically has 3-6 items in Now, 5-10 items in Next, and the remainder in Later. If Now is overloaded, you need to be more selective, probably by raising the bar on certainty or urgency. If Later is empty, you are likely not capturing enough early-stage ideas and your pipeline will dry up.
" Also check for internal consistency. Are all the Now items genuinely more certain and urgent than all the Next items? If you spot an item in Next that feels more ready than something in Now, swap them and update the rationales. This validation step catches the drift that accumulates when you evaluate items one at a time.
Tip: Read the Now column as if it were a sprint commitment. Ask: "Can we realistically deliver all of these in the current cycle?" If not, some items need to move to Next. The Now column must represent actual capacity, not wishful thinking.
Step 8: Write Horizon Rationales for Each Item
For every item, write a concise rationale (2-3 sentences) explaining why it sits in its assigned horizon. This is not optional. The rationale is what makes the categorization useful over time. Without it, items drift between horizons based on whoever argues loudest in the next meeting.
A good rationale references the three evaluation dimensions and connects to strategic context. " Store these rationales alongside the items in your roadmap tool or document.
Tip: Rationales serve double duty. They explain the current placement, and they also capture the conditions that would trigger a move. A Later item with a rationale of "waiting on user research results" naturally graduates to Next once that research completes. This makes reprioritization (see [Reprioritizing and Moving Items Across Horizons](/skills/reprioritizing-across-horizons)) much faster.
Step 9: Share and Pressure-Test with Stakeholders
Share the categorized backlog with key stakeholders for feedback before treating it as final. Present each horizon with its items and rationales. Invite challenges, but ground the conversation in the evaluation dimensions, not in personal preferences. When a stakeholder disagrees with a placement, ask which dimension they see differently: "Do you think certainty is higher than we assessed?
Do you see urgency we missed? " This frames disagreements as evidence-based discussions rather than opinion battles. Incorporate feedback that changes your assessment of the underlying dimensions, but do not move items just because someone pushes hard. Document any changes and the reasoning behind them.
The output of this step is a finalized, stakeholder-reviewed categorized roadmap ready for communication.
Tip: If stakeholders push back on many placements, the problem is usually misalignment on strategic context (Step 2), not on individual item assessments. Revisit the strategic context first before re-evaluating individual items.
Examples
Example: Early-stage B2B SaaS with 3-person product team
A seed-stage project management tool has 15 items in its backlog, a 3-person engineering team, and a 2-week sprint cycle. The company's strategic focus is landing its first 10 paying customers in the SMB segment. The product has a working MVP but significant gaps in onboarding and reporting.
" Strategic context: acquire first 10 SMB customers, reduce onboarding drop-off (currently 60% abandon during setup). Scoring reveals 4 items with high certainty (billing integration, onboarding wizard, CSV import, email notifications) because the team has customer feedback and clear specs for all four. Urgency analysis shows billing and onboarding wizard are blocking revenue: no billing means no paying customers, and the 60% drop-off rate means even interested users leave. Both score high on urgency and alignment.
CSV import and email notifications score medium on urgency. The AI task suggestions score low on certainty (no user research, speculative solution) and low on urgency. Final categorization: Now contains billing integration and onboarding wizard (2 items, matching team capacity for 2 weeks). Next contains CSV import, email notifications, and a mobile-responsive redesign (3 items with clear specs, ready for the following sprint).
Later contains AI suggestions, a Slack integration concept, and 8 other items needing research. The PM writes rationales such as: "Now: Billing integration. High certainty (Stripe docs reviewed, technical spike complete). High urgency (cannot collect revenue without it).
" This categorization gives the team a clear two-week focus and a visible pipeline for what comes after.
Example: Mid-market SaaS with 20-person product org
A customer data platform has 45 items across 4 product teams. The company's annual strategy focuses on two objectives: expand into the healthcare vertical and reduce time-to-value for new customers from 6 weeks to 2 weeks. The product org runs monthly planning cycles.
The VP of Product runs the categorization in a 90-minute session with the 4 team leads. They start by aligning on strategic context: healthcare expansion (objective 1) and onboarding speed (objective 2). Each team lead pre-scores their items independently before the session. Scoring surfaces interesting tensions.
A HIPAA compliance module scores high on all three dimensions for the healthcare-focused team, going straight into Now. But a requested analytics dashboard overhaul scores high on certainty and urgency (enterprise customers are complaining) yet medium on strategic alignment (it serves existing segments, not the healthcare push). After discussion, the group places the analytics overhaul in Next with a rationale: "Important for retention, but current customers are not churning over this. " A machine learning pipeline for predictive customer scoring scores low on certainty (the data science team has only a proof of concept) despite high strategic alignment with both objectives.
It goes into Later with the rationale: "High potential but needs a 4-week technical spike before we can commit. " The team puts the technical spike itself into Now for one of the teams. Final distribution: 8 items in Now (2 per team), 14 in Next, 23 in Later. The session ends with each team lead owning their rationale documentation.
Example: Consumer mobile app with a rapid release cycle
A fitness tracking app with 500,000 users ships updates every two weeks. The product team of 8 engineers has a backlog of 30 feature requests, bug fixes, and performance improvements. Strategic focus: increase 30-day retention from 35% to 50% and launch social features to drive viral growth.
The PM categorizes items in a solo session (small team, fast cycle). Certainty scoring immediately splits the backlog. Bug fixes and performance improvements are high certainty by nature, with well-defined problems and known solutions. Social features like "workout sharing" and "friend challenges" are medium certainty (user survey data supports demand, but the specific implementation is unproven).
A "gamification system" concept is low certainty (inspired by a competitor, no internal research). Urgency analysis reveals that a crash-causing bug affecting 12% of iOS users is the only genuinely high-urgency item, with measurable impact on ratings and churn. Social features have no external deadline. Strategic alignment scoring is where the interesting decisions emerge.
The iOS crash fix aligns with retention (objective 1) because crashes directly cause churn. Workout sharing aligns with both retention and viral growth. A requested dark mode, while highly requested by users, has low alignment with either strategic objective. Final categorization: Now contains the iOS crash fix, a push notification optimization (validated A/B test ready to ship, directly targets retention), and a workout sharing MVP (medium certainty, but the PM scopes it to a known-good pattern).
Next contains friend challenges, a redesigned onboarding flow, and two performance improvements. Later contains dark mode, gamification, and 15 other items. The rationale for dark mode's Later placement is telling: "Highly requested but no evidence it impacts retention or growth. " This keeps the team focused on the two metrics that matter without dismissing the user request.
Example: Enterprise platform with quarterly planning
A B2B analytics platform serves Fortune 500 clients. The product team of 40 engineers plans quarterly with 80+ items in the backlog. Strategic objectives: reduce enterprise onboarding time from 12 weeks to 4 weeks, and build a self-serve tier to capture the mid-market. Two large clients have contractual feature commitments with Q3 deadlines.
The Director of Product runs a two-session categorization process. Session 1 (async, 3 days): each of the 5 team leads independently scores their 15-20 items using a shared spreadsheet. Session 2 (live, 2 hours): cross-team review focusing on items where scoring disagreements exist or where dependencies span teams. The contractual commitments (a custom SSO implementation and an audit log enhancement) immediately go into Now.
Both have high certainty (detailed specs from client contracts), high urgency (Q3 contractual deadline with financial penalties), and high strategic alignment (enterprise retention). The self-serve tier work splits across horizons: the pricing page and Stripe integration (high certainty, high alignment) go into Now. A usage-based billing model (medium certainty, requires pricing research) goes into Next. A product-led onboarding experiment (low certainty, requires a fundamentally different UX approach) goes into Later.
The dependency check in Session 2 surfaces a critical issue. Three Now items depend on a database migration that was sitting in Next. The team moves the migration into Now, which forces a lower-priority Now item into Next. Final distribution: 12 items in Now (distributed across 5 teams), 25 in Next, 43+ in Later.
Each team leaves with a clear 90-day scope and documented criteria for what would trigger items moving from Next to Now mid-quarter.
Best Practices
Score each dimension independently in writing before discussing with the group. When teams discuss items aloud before individual assessment, the first opinion anchors the conversation and compresses the range of scores. Silent individual scoring followed by comparison reveals genuine disagreement and produces more accurate assessments.
Limit your Now horizon to what your team can realistically deliver in the current planning cycle. A Now column with 15 items signals that you have not actually made hard trade-offs. For most teams of 5-10 people, 3-6 Now items is the right range. Overloading Now undermines trust in the roadmap because stakeholders learn that "Now" does not actually mean "now."
Use consistent, specific language in your rationales rather than vague qualifiers. "High certainty based on 200 user interviews and a validated prototype" is useful. "We feel pretty confident about this one" is not. Specific rationales make future re-evaluation faster because you can check whether the underlying evidence has changed.
Revisit your categorization at a regular cadence, typically every 2-4 weeks for early-stage products or monthly for mature products. The world changes, new data arrives, and strategy evolves. A categorization that was perfect four weeks ago may have items in the wrong horizons today. Schedule the review rather than waiting for someone to notice drift.
Separate the categorization session from the brainstorming session. If people are generating new ideas and evaluating existing ones at the same time, both activities suffer. New ideas get prematurely judged, and existing items get re-debated instead of evaluated. Collect ideas continuously, then batch the categorization exercise.
Treat Later as a valued holding space, not a rejection pile. Teams that stigmatize Later lose ideas because contributors stop submitting them. Later items are the raw material of future innovation. Frame Later as "not yet, pending more information" rather than "not important." Periodically review Later to see if conditions have changed.
When two items seem tied in priority, ask which one unblocks the other. Dependencies often break ties naturally. The item that enables other work to proceed has higher effective urgency even if its standalone urgency score is the same.
Common Mistakes
Using Now, Next, and Later as priority tiers instead of time horizons
Correction
" This misses the key insight of the framework. Now is not about importance. It is about readiness and sequencing. A Later item might be critically important to your long-term strategy, but if certainty is low, it belongs in Later until discovery work matures it.
You can catch this mistake by checking: are there items in Now with low certainty? If so, you are sorting by importance, not by horizon readiness. Move those items to Next or Later and put the discovery work into Now instead.
Letting urgency override certainty for Now placement
Correction
Teams frequently place items in Now because a stakeholder declared them urgent, even when certainty is low. This leads to sprints derailed by mid-cycle discovery work, scope changes, and wasted effort. The signal to watch for is a Now item where the team cannot clearly articulate what they would build and how they would measure success. When you encounter high urgency but low certainty, put a time-boxed discovery or scoping task in Now and keep the actual build in Next.
This lets you respond to the urgency without committing to build something you do not yet understand.
Overloading the Now horizon with more items than the team can handle
Correction
This happens because saying "not now" feels like saying "not important," and product managers want to show stakeholders that their requests are being addressed. The result is a Now column with 15-20 items that functions as a re-labeled backlog. Nobody trusts it, and the team cherry-picks what to actually work on, defeating the purpose of the framework. The fix is simple: establish a hard cap on Now items based on team capacity.
If you have 6 engineers and a 4-week cycle, you can realistically deliver 3-5 significant initiatives. Set that as the maximum and enforce it. Every item added to Now must displace another item to Next.
Skipping the rationale and relying on group memory
Correction
Teams often assign horizons in a meeting, nod in agreement, and then forget why items were placed where they were within a week. When reprioritization happens, the conversation restarts from scratch because nobody remembers the original reasoning. This compounds over multiple cycles and makes the roadmap feel arbitrary. The fix is to require a 2-3 sentence written rationale for every item before the categorization is finalized.
This takes 15-20 extra minutes in the session but saves hours in future debates. If writing the rationale feels difficult, it usually means the evaluation was not rigorous enough. That difficulty is a useful signal.
Evaluating items in isolation without considering dependencies
Correction
An initiative might score well on certainty, urgency, and alignment, but if it depends on infrastructure work that has not started, it cannot actually be in Now. Teams that evaluate items in isolation end up with a Now column full of initiatives that are blocked from day one. After your initial scoring, do a dependency check across all Now and Next items. For each Now item, ask: "What must be true or done before this can start?" If the dependency is not also in Now, either move the dependency into Now or move the dependent item into Next.
Treating the categorization as permanent instead of a living snapshot
Correction
Some teams invest heavily in their initial categorization and then resist changing it, even when new information arrives. They treat the horizon assignment as a commitment rather than a current-best-judgment. This rigidity defeats the purpose of the Now-Next-Later Framework, which is designed for flexibility. Set an explicit review cadence (every 2-4 weeks) and normalize movement between horizons.
Items graduating from Later to Next is a sign of healthy discovery work, not a sign that the original categorization was wrong.
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.
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.
Reprioritizing and Moving Items Across Horizons
How to run regular reviews that promote, demote, or remove items between Now, Next, and Later as new information and priorities emerge.
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.
Frequently Asked Questions
How many items should be in each horizon?
There is no universal ratio, but a healthy pattern for most teams is 3-6 items in Now, 5-15 in Next, and an uncapped Later. The Now horizon must match your team's actual delivery capacity for the current planning cycle. If Now has more items than your team can realistically complete, you have not made hard enough trade-offs. Later can be as large as you want because it functions as a curated idea backlog, not a commitment.
How do I categorize items when certainty and urgency conflict?
When an item is urgent but uncertain (for example, a competitor just launched a threatening feature and you need to respond but have no solution designed), do not put the full initiative in Now. Instead, put a time-boxed discovery task in Now ("2-week spike to evaluate response options") and keep the actual build in Next pending the results. This acknowledges the urgency without committing to build something you do not understand. The discovery task itself has high certainty (you know exactly what you are doing: researching), high urgency (the competitive threat is real), and high alignment.
Should I do this categorization alone or with the team?
Both. The most effective approach is a two-phase process. Phase 1: score items independently in writing before any group discussion. This prevents anchoring bias and surfaces genuine disagreement. Phase 2: review scores as a group, focusing discussion on items where individual scores diverged significantly. Solo categorization is fine for small teams (fewer than 5 people) or fast cycles (weekly), but any categorization that affects multiple teams or stakeholders benefits from collaborative review.
How often should I re-categorize items across horizons?
Match your re-categorization cadence to your planning cycle. If you plan in 2-week sprints, review horizon placement every 2 weeks. If you plan quarterly, do a full review monthly and a light check bi-weekly. The goal is to catch items that have changed readiness. A Later item might gain certainty because user research completed. A Now item might lose urgency because a client extended their deadline. See [Reprioritizing and Moving Items Across Horizons](/skills/reprioritizing-across-horizons) for the full process.
What is the difference between categorizing items and defining graduation criteria?
Categorizing items is the act of evaluating your current backlog and placing each item in a horizon based on today's assessment. Defining graduation criteria (see [Defining Graduation Criteria Between Horizons](/skills/defining-graduation-criteria-between-horizons)) is about establishing the conditions that must be true for an item to move from one horizon to the next. Think of categorization as the snapshot and graduation criteria as the rules that govern how the snapshot evolves. You need both: initial categorization gets you started, and graduation criteria keep the system running over time.
How do I handle items that stakeholders insist must be in Now even when the evaluation says otherwise?
Ground the conversation in the three dimensions rather than arguing about priority. Ask the stakeholder to identify which dimension they assess differently: "Do you believe certainty is higher than we scored? Is there urgency we missed? " If they can change your assessment of a dimension with new evidence, move the item. If they cannot, explain that placing an uncertain item in Now risks wasted cycles and delays to the items that are ready. Offering to put a discovery task in Now often satisfies the stakeholder's need to see action without committing to a premature build.
Can an item skip Next and go directly from Later to Now?
Yes, though it is uncommon. This happens when external circumstances change rapidly, such as a regulatory deadline being announced or a major customer threatening to churn over a missing feature. If an item suddenly has high certainty, high urgency, and high strategic alignment, it can jump straight to Now regardless of where it was before. The key requirement is that certainty must be genuinely high. If the item jumped from Later because urgency spiked but certainty is still low, you are setting your team up for a painful sprint. In that case, put discovery in Now and the build in Next.