Now, Soon, Later: The Roadmap Rhythm That Keeps Journey Work Moving

Roadmaps are a perennial problem in product development. They tend to be too detailed to be honest, too high-level to be useful, and constantly undermined by the gap between what gets planned and what gets built. Journey management inherits this problem and, if left unaddressed, reproduces it: a set of Big Solutions with milestones that slide, dependencies that weren't mapped, and a growing distance between the map's version of progress and the organization's actual delivery.

The Now–Soon–Later rhythm is a deliberate response to this gap. It applies equally to Big Solutions in development and to the emerging ideas that precede them — providing a shared language for sequencing work that is flexible enough to survive contact with organizational reality.

What the Three Horizons Mean

Now is the minimum viable expression of a Big Solution — the smallest version that can be tested with real customers and produce meaningful evidence. In practice, this means a prototype, a limited rollout, a single feature that embodies the solution's core value proposition before the full system is built. The Now horizon is governed by the test plan: what hypothesis is being tested, what evidence will confirm or challenge it, and what decisions depend on the results.

Soon is the enhanced version — the one that delivers the gains the customer research identified, not just the minimum viable proof of concept. Soon assumes the Now has produced positive signals. It is the roadmap for building on confirmed value: expanding access, deepening the feature set, and integrating with adjacent systems. The experience score at this stage should begin to show meaningful improvement.

Later is general availability — the mature, fully integrated version of the solution that is running at scale and is ready for transition to steady-state ownership. Later is also where the solution's OKRs should reflect the original customer experience goals: the experience score for the relevant journey stages should have moved, and the improvement should be attributable to the work.

"Now–Soon–Later is not a wishful three-step. It's a structure that forces teams to distinguish between testing an idea, building on evidence, and scaling what works."

Why This Framing Works Organizationally

The Now–Soon–Later rhythm solves a political problem as well as a planning one. When teams present solutions, leadership often responds in one of two ways: either they demand immediate full-scale implementation (which skips the learning that the test plan is designed to generate) or they delay indefinitely pending more certainty (which prevents the learning from ever being produced).

The three-horizon framing provides a middle path. The Now investment is modest — a test, a prototype, a small cohort. The commitment is to learning, not to deployment. This makes the Now easier to approve. The Soon and Later horizons are conditional on the Now producing positive evidence, which makes the full investment contingent on results rather than assumptions. Leadership can approve Now without pre-committing to Later.

This structure also makes progress visible. A Big Solution that has moved from Now to Soon has passed a real test. A solution still in Now after two cycles has not yet confirmed its value, which surfaces the question of whether the test design is working or whether the hypothesis should be revised. The rhythm creates natural decision points without requiring a formal review process to generate them.

Connecting Horizons to Experience Scores

Each horizon should have a corresponding experience score target. The Now implementation produces a baseline — the score at the relevant journey stages before the solution has had meaningful effect. The Soon implementation should show early movement. The Later implementation should close the gap between the baseline score and the target that the OKR specified.

This connection prevents a common failure mode: Big Solutions that are "delivered" in the sense that they shipped, but whose impact on the customer experience was never measured. The Now–Soon–Later rhythm, tied to experience scores at each stage, makes the connection between delivery and outcome explicit and non-negotiable. You do not graduate from Now to Soon until the evidence tells you what you need to know about the hypothesis. You do not graduate from Soon to Later until the experience score shows meaningful movement.

The rhythm is patient by design. And patience, in journey management, is a competitive advantage.