Governance First Now, Next, Later Roadmap With OKR Triggers
Now-Next-Later is a three-horizon roadmap that sorts work by confidence rather than calendar dates. It fits teams running continuous discovery, SaaS products, and anything where long-range dates would mislead stakeholders. Skip it when contracts, regulations, or hardware cycles require fixed delivery dates instead.
TL;DR:
- The Now-Next-Later framework prioritizes work based on confidence levels rather than fixed dates, making it suitable for teams with continuous discovery cycles.
- Capacity caps are essential for Now and Next to prevent scope creep and backlog bloat, with recommended limits of 3 to 6 items for Now and 5 to 8 for Next.
- Movement between horizons depends on clear evidence and alignment, such as validated hypotheses for Next to Now, and user evidence for Later to Next.
- Regular cadence reviews (weekly for Now, monthly for Next, quarterly for the full roadmap) ensure governance and prevent stagnation or overflow in any horizon.
- Using outcome-based metrics and linking items to measurable success criteria increases trust in the roadmap, while a hybrid approach suits situations requiring fixed deadlines.
Table of Contents
- What the Now-Next-Later format is and why it exists
- Why product teams choose Now-Next-Later
- What belongs in Now, Next, and Later
- Governance and movement rules: triggers, roles, and cadence
- Operationalizing the roadmap: OKR mapping and execution details
- Common pitfalls and fixes
- What I've learned building horizon-based roadmaps
- How Petĩra turns feedback into roadmap signal
- FAQ
- Sources
What the Now-Next-Later format is and why it exists
The format grew out of product management communities looking for a way to communicate direction without pretending to know exact ship dates months out. Instead of a date grid that invites false precision, teams organize work into three confidence horizons. According to the UPG Framework, the format trades calendar precision for directional clarity, with Now holding committed work, Next holding validated priorities, and Later holding directional initiatives that still need discovery.
Each horizon carries a distinct meaning:
- Now: work that is scoped, resourced, and already in delivery.
- Next: priorities backed by evidence but not yet fully committed.
- Later: themes and bets worth exploring, with no promise attached.
Teams move away from date grids because dates break the moment discovery surfaces new information. A horizon board absorbs that uncertainty instead of forcing a false commitment, which is why it has become common in product organizations that run frequent discovery cycles rather than annual planning rounds.
Why product teams choose Now-Next-Later
Stakeholders get alignment without the false comfort of a date that will likely slip. Leadership conversations stay strategic because the board forces a discussion about confidence and evidence rather than about which sprint a feature lands in. Teams also get a built-in focus mechanism: a board with only three horizons cannot hide an unlimited backlog behind the appearance of planning.
- Reduces pressure to commit before evidence exists.
- Keeps executive reviews focused on outcomes, not ticket status.
- Makes it obvious when a team has too much in flight.
- Gives public-facing stakeholders visibility without exposing sprint mechanics.
The format breaks down in a few contexts. Contractual commitments, regulatory submissions, and hardware manufacturing cycles often require dates that cannot flex with discovery, and forcing those into a horizon board creates confusion rather than clarity. In those cases, a hybrid approach or a conventional date-based roadmap communicates more honestly.
Pro Tip: Run a hybrid roadmap when only part of your work is contractual: keep the regulated deliverables on a dated timeline and everything else on Now-Next-Later.
What belongs in Now, Next, and Later
Each horizon has its own entry bar, and mixing them up is the fastest way to turn the board into a glorified task list.
- Now holds items where discovery is finished, scope is locked, and delivery has started. Recommended capacity sits around 3 to 6 items, such as "ship saved filters" or "fix checkout error rate."
- Next holds priorities with partial evidence: a validated hypothesis, early sizing, or a problem confirmed through user research but not yet fully scoped. Recommended capacity runs 5 to 8 items, for example "reduce onboarding drop-off" or "add bulk editing."
- Later holds themes and directional bets rather than committed features, capped at roughly 10 themes such as "explore team permissions" or "investigate mobile offline support."
Keeping Later limited to themes, not fully formed feature requests, prevents it from becoming a graveyard where ideas go to be forgotten. Capacity caps on Now and Next matter just as much: without them, both columns bloat into a backlog with a new coat of paint.
Governance and movement rules: triggers, roles, and cadence
A Now-Next-Later board only works when movement between columns follows explicit rules instead of whoever shouts loudest in a planning meeting. The clearest criteria come from evidence and alignment, not seniority.
- Later to Next: requires validated user evidence and clear alignment to an OKR.
- Next to Now: requires passed assumption tests, a scoped solution, and confirmed team capacity.
- Decision rights: a named PM owner proposes moves, a discovery guild or research function validates evidence, and product leadership signs off on anything touching strategy.
A common cadence reviews Now weekly, Next monthly, and resets the full roadmap quarterly, according to Umbrex's Now-Next-Later guidance, which also ties movement triggers to data on OKRs, discovery, and capacity rather than opinion. That cadence gives delivery teams a fast feedback loop while reserving bigger strategic conversations for a slower rhythm.
A few signals reveal when the board has stopped functioning as intended:
- Now holds far more than 6 items, meaning scope creep has gone unchecked.
- Nothing has moved between columns in over a month, meaning governance has stalled.
- Next keeps growing without items graduating to Now, a sign that validation criteria are too vague or too strict.
When any of these show up, the fix is rarely more process. It is usually enforcing the capacity caps and movement criteria that already exist on paper.
Operationalizing the roadmap: OKR mapping and execution details
A Now-Next-Later board earns trust when every item ties to something measurable. Outcome-based practice recommends keeping roadmaps short, tying each item to a success metric, and resisting the urge to commit to specific solutions or dates, as described in Sense & Respond's guidance on outcome-based roadmaps.
- Map each roadmap item to an OKR or a measurable success metric, and keep that metric visible on the card itself.
- Keep ticket-level detail (Jira issues, engineering tasks) inside private delivery boards, never on the public roadmap.
- Build the board around 3 to 5 prioritized outcomes, each with 1 to 2 candidate features, rather than a long feature list.
- Prune Later every quarter and cap Now so the board never drifts into a disguised task list.
This structure keeps the public view strategic while giving delivery teams the detail they need in a separate system built for ticket tracking.
Common pitfalls and fixes
Most Now-Next-Later boards fail in predictable ways. The SaaS Fractional CPO guide names three recurring failure modes: the ambiguity trap, the graveyard Later, and the relabeling trap.
- Ambiguity trap: Next turns into an overflow backlog. Fix it with written entry criteria and a monthly review that actually enforces them.
- Graveyard Later: items sit untouched for quarters. Require a named owner and a promotion path for every Later item, and prune anything stale each quarter.
- Relabeling trap: teams rename columns without changing how decisions get made. Treat the format as a governance change, not a cosmetic one.
- Overloaded Now: scope creeps past capacity. Enforce the cap and push overflow back into Next until capacity frees up.
Pro Tip: Schedule the quarterly Later pruning on the same calendar invite as your quarterly strategy reset, so it never gets skipped.
What I've learned building horizon-based roadmaps
The biggest shift I have seen when teams move to horizon-based boards is not visual. It is the conversation change: stakeholders stop asking "when" and start asking "how confident are we." That single reframe does more for alignment than any template. Public boards and status tracking give teams a steady stream of validated signal to feed directly into Next.
— Aron
How Petĩra turns feedback into roadmap signal
We built Petĩra around the same problem this guide addresses: turning scattered feedback into roadmap items you can actually trust. The public board lets users post ideas and vote on them, so instead of guessing what belongs in Later, you get a ranked, visible signal.
- Collect ideas publicly instead of across scattered emails and chat threads.
- Let upvotes surface which Later themes deserve a path to Next.
- Export data as CSV or JSON and plug it into a discovery workflow.
Use Petĩra to convert strong Later signals into validated Next candidates, backed by real vote counts instead of internal opinion. Keep public stakeholders informed with status tags like planned or in progress, without ever promising a date. Check our pricing to compare the Free, Pro, and Team plans and start moving real feedback onto your roadmap.
FAQ
Can ChatGPT create a Now-Next-Later roadmap?
A large language model can draft horizon categories and sample items from a prompt, but it cannot validate evidence, confirm team capacity, or make the movement decisions needed to keep the board honest. Treat any AI-drafted version as a starting template, not a finished governance artifact.
Is a Gantt chart the same as a roadmap?
No. A Gantt chart maps tasks to fixed dates and dependencies, while a Now-Next-Later roadmap organizes work by confidence horizon instead of calendar time, according to the UPG Framework. The two serve different purposes: one tracks execution, the other communicates direction.
What is the best software for product roadmapping?
The right tool depends on whether you need a public-facing board, private execution tracking, or both. Petĩra focuses on the public collection and prioritization side, pairing a feedback board with status tracking and exports so validated ideas can feed into whatever horizon board or delivery tool you already use.
What is an example of a Now-Next-Later roadmap?
A simple example puts "fix checkout error rate" in Now, "reduce onboarding drop-off" in Next, and "explore team permissions" in Later. Each item reflects a different confidence level: Now is scoped and in delivery, Next has partial evidence, and Later is a theme still needing discovery.
Sources
These sources cover the framework definition, governance cadence, common failure modes, and outcome-based practice referenced throughout this guide. Reading them in full helps with implementation details beyond what fits here.