Key takeaways
  • A roadmap has three altitudes (Now, Next, Later) and is not a delivery schedule.
  • Outcome roadmaps beat output roadmaps.
  • Learn to read someone else's roadmap, and spot the common anti-patterns.

Most teams that say "our roadmap keeps changing" don't have a roadmap problem. They have a strategy problem dressed in roadmap clothing. The same teams almost always treat their roadmap as if it were a delivery schedule, a promise to ship features on dates. That's not what a roadmap is, and treating it like one is why they break every quarter.

A roadmap is the visible output of three upstream decisions: who you're building for, what you're building toward, and which bet you're making next. The artefact itself isn't the value — the thinking behind it is. The artefact's job is to make that thinking legible, defensible, and updatable.

The three altitudes of a roadmap.

A good roadmap operates at three altitudes simultaneously — and the failure mode of every weak roadmap is collapsing them into one. The classic frame, borrowed from product agile practice, is Now / Next / Later. Each altitude has a different temperature of certainty, a different unit of work, and a different ownership.

Diagram · The three altitudes of a roadmap
The three altitudes of a roadmap — Now, Next, Later Three horizontal columns showing the structure of a healthy roadmap. Column one — NOW (0 to 30 days) is fully committed work, owned by the team currently delivering it, with sharp scope. Column two — NEXT (30 to 90 days) is shaped initiatives, owned by the PM, with refined scope but flexible dates. Column three — LATER (90 days to 12 months) is themes and bets, owned by the CPO, with deliberately fuzzy outlines. Certainty decreases and time horizon increases from left to right. A roadmap that pretends Later is as certain as Now is a wish list. A roadmap that won't say what Later contains is a delivery schedule. ALTITUDE 01 Now 0–30 days Unit · committed work Owner · the team shipping it Scope · sharp, story-level Dates · fixed Almost certain. If it's not, you have a flow problem. ALTITUDE 02 Next 30–90 days Unit · shaped initiatives Owner · PM Piece Scope · refined, not stories Dates · flexible Confident shape. Details will move. ALTITUDE 03 Later 90 days–12 months Unit · themes & bets Owner · CPO Piece Scope · deliberately fuzzy Dates · directional A bet on the world. Updated quarterly. ← certainty decreases · time horizon increases →
Now is a commitment. Next is a shape. Later is a bet. Collapse the three and the roadmap becomes either a delivery promise (which it can't keep) or a wish list (which the team won't trust).

Now (0–30 days). Work the team has already started or is about to start. Stories are written, sprints are planned, dates are real. If Now isn't predictable, the problem is sprint flow, not the roadmap. Owned by the team. The roadmap's only job here is to make visible what's in flight.

Next (30–90 days). Initiatives that are shaped, sequenced, and committed-to in direction but not in dates. Each Next initiative has a clear outcome (what this will move) and a confidence-weighted size. Owned by the PM Piece. The roadmap's job here is to make trade-offs visible — what we're choosing to do, and what we're explicitly not.

Later (90 days – 12 months). Themes and bets. The Later band is deliberately fuzzy, a list of named bets at the resolution of "we believe X about the market and we'll respond by Y". No dates. No stories. Owned by the CPO Piece. The roadmap's job here is to make the strategic thesis legible. Board, team and customers all see the same shape.

A roadmap that pretends Later is as certain as Now is a wish list. A roadmap that won't say what Later contains is a delivery schedule.

Outcome roadmaps vs output roadmaps.

The other frame worth knowing: an output roadmap lists what you'll build ("new checkout · referral · payments v2"). An outcome roadmap lists what you're trying to move ("reduce checkout abandonment · grow share of payment volume · open the second market"). Outcome roadmaps survive contact with reality because they don't lock the team into a specific solution. Output roadmaps become wish lists because the moment the team learns something, the listed feature is wrong but already committed.

Senior product practice is overwhelmingly outcome-led at the Next and Later altitudes, with output specifics only at Now. If your roadmap is a list of features named 12 months out, you have an output roadmap. Recovering it doesn't mean tearing it up — it means re-stating each feature as the outcome it's intended to move, and letting the feature itself be revisited.

Roadmap anti-patterns.

  • The wish list. Every stakeholder ask added; nothing taken off. A roadmap that won't say no isn't a roadmap, it's an inbox.
  • The date promise. Every initiative pinned to a calendar quarter at Later altitude. Sets the team up to break trust the moment reality bites.
  • The feature factory. All output, no outcome. The team ships continuously and nobody knows if any of it moved the needle.
  • The single-altitude roadmap. Everything in Next, nothing in Now or Later. No visible commitment to short-term flow OR long-term bet.
  • The roadmap nobody believes. Last published six months ago. Updated never. The artefact is dead but nobody's said so.

How to read someone else's roadmap.

If you're walking into a function and want to diagnose its health in fifteen minutes, the roadmap is the first place to look. Ask: which altitudes are present? Is Now committed and date-real? Is Next outcome-led and trade-off-visible? Is Later a small number of named bets, or empty, or a 30-line feature list pretending to be strategy? The asymmetry tells you which Piece is missing.

  • Strong Now, empty Next and Later. The team is shipping but no one's thinking past the sprint. Almost certainly a CPO Piece gap.
  • Strong Later, broken Now — the strategy exists but execution is leaking. A PM Piece or PO Piece gap.
  • Feature-list at every altitude. The function has confused output with outcome. The PM Piece needs a senior reset.
  • No roadmap, just Jira — the function is reactive. Common in early scale-ups before the first senior PM lands.

Where this lands at Product Pieces.

If your roadmap is broken in a recognisable shape, the Diagnostic will name which Piece is missing. From there: The Roadmap Set Piece (2–3 weeks, fixed scope) builds a real one: three altitudes, outcome-led at Next and Later, defensible to the board and the team.

Next issue: The User Story. Anatomy of one that holds up, plus a worked example in the format we use across our engagements.