Symptom: Now is full and nothing finishes.
Cause: Item count was treated as capacity, and the commitment was never reduced.
Fix: Reduce the number of commitments, record what is displaced, or use a count policy you actually believe in.
Technical SEO
Title, meta description, canonical, OG, Twitter, BreadcrumbList, FAQPage, WebApplication schema.
Now / Next / Later Roadmap
Build a living Now/Next/Later roadmap that records why each initiative is in its current horizon, what must change before it moves, and what stakeholders can safely infer. It is a confidence-horizon operating system, not a board of readiness scores and not a dated release plan.
- Horizon Movement Contract per item: why here, what is known versus uncertain, current commitment, movement and reversal conditions, dependencies and opportunity cost.
- Roadmap change and commitment ledger, dependency editor and integrity audit, editable horizon policy, and a descriptive decision audit with no aggregate score.
- Sanitized stakeholder sharing, full internal sharing with a privacy warning, CSV/JSON/Markdown/PNG/PDF export, import review and browser-local persistence.
No login. Autosave in this browser. Shareable in internal and sanitized modes.
Loading your roadmap…
How it works
- Add themes and initiatives. For each item record the outcome it serves, why it is in its current horizon, and the commitment you are actually making.
- Work the Horizon Movement Contract: what is known, what is unknown, what must change before it moves, what could move it back, dependencies, opportunity cost and the decision owner.
- Use the roadmap decision audit to review placement, evidence, focus, dependencies, communication and freshness. Move an item only when the reason is recorded, then share a sanitized stakeholder view.
Now/Next/Later means different things to different teams
Some teams use Now/Next/Later as broad timing buckets. Others use it primarily as confidence horizons. CraftUp defaults to a confidence-horizon interpretation because it is useful for uncertainty-aware product work: Now is an active commitment, Next is active shaping, and Later is a direction worth keeping visible. Because real organisations differ, the horizon policy in the tool is editable, your workspace should define what each horizon means for your team.
Next does not automatically become Now
A horizon is not a queue. Next does not become Now on its own, and Later does not become Next on its own. Movement should be driven by evidence, feasibility, capacity or an explicit decision. An initiative can stay where it is, move backward when a bet is invalidated, or be archived when it is no longer aligned. Later is not a backlog and not a graveyard; it is a horizon for strategic bets that are not being committed to right now.
The Horizon Movement Contract
For every material item the tool keeps one inspectable record: the current horizon, why it is there, the current commitment, what is known, what is unknown, what must change before it moves, what could move it back, material dependencies, opportunity cost and the decision owner. A movement condition describes what must change, not a date. When an item moves, the Roadmap Change Ledger preserves the rationale, the evidence or dependency change and the decision owner, so the roadmap does not silently lose the reasoning behind it.
Default horizon definitions (editable)
Now: actively committed or in motion. Enough uncertainty is reduced for the commitment the team is making, but evidence can still be incomplete and discovery can continue. Next: actively shaping and learning toward a potential commitment; not promised, and it should carry an explicit unknown or movement condition. Later: a strategic area or bet worth keeping visible with lower current confidence, immediacy or capacity commitment. None of these definitions is a universal law; edit the policy so it fits how your team works.
NNL is not always the right view
Now/Next/Later is especially useful when strategic direction is clear, exact dates would imply false precision, and uncertainty differs across bets. A target-quarter, timeline or release view can be better when regulatory or contractual milestones dominate, when release coordination is genuinely date-critical, or when detailed project sequencing is the actual job. This tool does not claim NNL is universally superior, and it does not add release gates to a roadmap.
Dates are context, not evidence
A date can be legitimate when a regulation, contract, migration, event or market window is the governing constraint. The problem is false certainty, not dates themselves. Record a date when it is the real driver of the horizon; do not use a date in place of evidence.
Pro tips
- A horizon communicates the current level and type of commitment under uncertainty. It is not a queue: Next does not automatically become Now, and Later does not automatically become Next.
- Record why each item is in its horizon. A readiness number hides the reason; a one-line rationale keeps the decision reviewable.
- Keep evidence and commitment separate. Strong evidence with low commitment is normal, and a contract can create commitment with thin Product evidence.
- Unknown is an allowed state, but it never counts as satisfied evidence. Say what is unknown and what would change the decision.
- A movement condition describes what must change, not a date. Use a date only when a rule, contract, migration or release window is the governing constraint.
- Record the opportunity cost when something moves into Now. If it is genuinely unknown, say that rather than implying free capacity.
- Use dependencies for decisions: describe how each one changes the horizon call, not just that a link exists.
- Movement can go backward or to archive. Learning that invalidates a bet is a good outcome, not a regression.
- Define what Now, Next and Later mean for your team. CraftUp's default is a confidence-horizon interpretation, not a universal law.
- Share the sanitized stakeholder view externally so exploration never reads as a promise.
Common mistakes
Symptom: Later becomes a wish list of unowned ideas.
Cause: Items are kept visible without a reason and never removed.
Fix: Give each Later item a strategic reason and revisit trigger, or archive it honestly.
Symptom: "Readiness 4" is used as if it were evidence.
Cause: Averaging ordinal scores into one number that hides which dimension is weak.
Fix: Record evidence status, feasibility knowledge and commitment separately; audit the conflicts instead.
Symptom: Every Next item is actually a promised feature.
Cause: Commitment inflation: exploration and delivery read the same way.
Fix: Set an accurate commitment (Exploring / Candidate / Planned / Committed / In motion) and check it against the horizon.
Symptom: A brand-new item passes review immediately.
Cause: A placeholder unknown or open question was stored as if it were real learning.
Fix: Store no placeholder evidence; name the actual unknown or movement condition.
Symptom: "unknown" and "unowned" are treated as requirements met.
Cause: Literal string matching instead of honest state.
Fix: Treat unknown as an explicit open state and unassigned as unassigned, and let the audit reflect it.
Symptom: Dependencies exist but nobody acts on them.
Cause: Free-text links with no described consequence.
Fix: Reference a real item and describe how it affects the movement decision.
Symptom: External stakeholders read exploration as a delivery promise.
Cause: The full internal roadmap was shared.
Fix: Use the sanitized stakeholder share, which omits evidence notes, owners, internal notes and decision rationale.
FAQ
Is this a timeline roadmap with dates?
No. This is a confidence-horizon roadmap. Now, Next and Later express the current level and type of commitment under uncertainty, not fixed dates. A date can still be recorded when a rule, contract, migration or release window is the governing constraint; the tool simply does not treat a date as evidence.
What do Now, Next and Later mean here?
CraftUp defaults to a confidence-horizon interpretation: Now means actively committed or in motion, Next means actively shaping and learning, and Later means a strategic area worth keeping visible without a current commitment. Your workspace policy is editable because real teams use these horizons differently.
Does Next automatically become Now?
No. Next does not become Now on its own, and Later does not become Next on its own. Movement should be driven by evidence, feasibility, capacity or an explicit decision. An item can also stay where it is, move backward, or be archived when learning invalidates it.
What is the Horizon Movement Contract?
It is the inspectable record for one item: the current horizon, why it is there, the current commitment, what is known, what is unknown, what must change before it moves, what could move it back, dependencies, opportunity cost and the decision owner. It is the main 10× asset of the tool.
Is there still a readiness score?
No. Averaging evidence, feasibility and value into one readiness number let two parts of the tool disagree and hid which dimension was weak. The roadmap now uses descriptive evidence status, explicit feasibility knowledge, a strategic basis and a separate commitment state.
How do I keep Later from becoming a junk drawer?
Later is a horizon, not a graveyard. Give each item a reason to stay visible and a revisit trigger, or archive it. You can set a Later count policy, but CraftUp does not treat a fixed cap such as fifteen as universal truth; use a policy only if it reflects how your team works.
Can I record why an item moved?
Yes. Moving an item through a review records a movement decision with rationale, the evidence or dependency change, and the decision owner in a change ledger. Trivial placement corrections can be logged as a correction with no decision event, so small cleanups do not create noise.
What does the sanitized stakeholder view hide?
It includes the item, outcome, horizon, high-level commitment, success signal, stakeholder-safe movement condition and any dependency you explicitly marked share-safe. It omits evidence notes, source references, owners, internal notes, decision rationale and archive rationale.
Can I share a roadmap link?
Yes, in two modes. A full internal link encodes the roadmap data in the URL; compression is not encryption, so anyone with the link can read it. The sanitized stakeholder link strips internal fields. Very large roadmaps exceed a safe URL length and should be exported instead.
Can I import and export my roadmap?
Yes. Versioned JSON is the lossless format, CSV supports spreadsheet editing with a real quoted-CSV parser, Markdown produces internal and sanitized versions, and the board exports to PNG or print/PDF. Unknown themes are never silently mapped; you review them before import.
Where this tool ends and other tools begin
Strategic direction unclear → Product Strategy One-Pager. Too many bets competing for the same capacity → Prioritization. Need a lighter reusable roadmap artifact or a target-quarter view → Product Roadmap Template. One selected bet needs deeper framing → Product Brief Template. Detailed product behaviour → PRD Generator. Release coordination → Product Launch Plan.
Learn more with CraftUp
Courses, blog and glossary for product and roadmap skills.
From roadmap to outcomes
Use CraftUp tools and courses to go from a confidence-horizon roadmap to validation and execution.
Freshness
Last updated: 2026-09-24
- 2026-03-05: Launched the Now/Next/Later roadmap builder with themes, columns and policy checks.
- 2026-09-24: Rebuilt as a confidence-horizon operating system: Horizon Movement Contract, evidence/commitment separation, movement ledger, dependency editor and audit, editable horizon policy, sanitized sharing and v1 migration.