Framework · Strategy & vision · 2 min read
Now-Next-Later roadmap
A roadmap organised by problems or themes and three time horizons instead of features and dates, so you can show direction and confidence without promising what you can't deliver.
1Now
This quarter. Committed and staffed, matched to real capacity.
e.g. maturity baseline, listening tour2Next
One to two quarters. Likely, and may still change.
e.g. intake and capacity board3Later
Three or more quarters. Directional, low confidence.
e.g. UX benchmark programmeItems are problems or themes, each with a confidence level · revisit quarterly
Use it when
- Stakeholders ask "what is UX working on next year?" and a feature list with dates would be a promise you can't keep.
- You have a UX strategy and need to show the order in which you will act on it.
- Priorities change often, and a date-based roadmap goes out of date every month.
How to use it
- Start from your strategy, not your backlog. Take the pillars or themes from your strategy kernel and list the problems you need to solve for each. Output: a list of problems grouped by theme.
- Write each item as a problem or theme. Say what you want to change, for example "Expert users can't see orders waiting for a reply", not "Build filter v2". Output: roadmap items phrased as problems.
- Place items in three horizons. Now (this quarter) is committed. Next (one to two quarters) is likely. Later (three or more quarters) is directional. Check that Now matches your real capacity. Output: a three-column roadmap.
- Mark confidence levels. Add a simple confidence label (high, medium, low) to each item, so readers see what might change. Output: a confidence label on every item.
- Revisit it quarterly with stakeholders. Each quarter, move finished items out, pull items forward from Next, and explain what changed and why. Output: an updated roadmap and a short change note.
Worked example
The UX roadmap from the module, for a fictional internal operations platform.
| Now (this quarter) | Next (1–2 quarters) | Later (3+) |
|---|---|---|
| Maturity baseline & listening tour | Cross-domain pattern library v2 | UX benchmark programme |
| Cross-domain critique ritual | Intake & capacity board | Career ladder & mentoring |
| Analytics event taxonomy (pilot in one app) | Roll out analytics to 2 more apps |
Every item in Now is committed and staffed. The items in Later have low confidence: they show direction, and the lead says so when presenting.
Watch out for
- Dates in disguise. If every Next item has a promised month, you have a date roadmap with new labels. Keep horizons, not deadlines.
- A feature list. "Build X, build Y" hides why. Phrase items as problems or themes linked to the strategy.
- More in Now than you can deliver. The roadmap must match capacity. Overloading Now breaks trust faster than an empty Later.
- Set and forget. A roadmap nobody revisits becomes wrong. Review it every quarter with the people who use it.
Template
Copy this into your roadmap page or slide.
UX roadmap, updated:
Theme / pillar Now (committed) Next (likely) Later (directional)
this quarter 1-2 quarters 3+ quarters
-------------------------------------------------------------------------------
Theme 1 Problem [conf: H] Problem [conf: M] Problem [conf: L]
Theme 2
Theme 3
What changed since last quarter, and why:
Next review date:
Saved only on this device.