UX Strategy Roadmap: How to Build One Leadership Will Fund

How do you turn user problems into roadmap themes?

On a UX roadmap, the prioritized themes are user problems, not features: group the evidence into five to eight themes, each naming a person and an unmet need.

Sort the evidence by person and struggle, not by screen; clusters that recur across sources become roadmap themes. Write each user problem in Jobs to be Done form, which describes the progress a person is trying to make: "When I add a new hire, I want to invite them in a minute, so they start work the same day."

Our running example is an invented business-to-business (B2B) software as a service (SaaS) invoicing product. The rewrite turns four of its feature rows into themes, each with its evidence.

Design debt, the inconsistent patterns that pile up when features outpace shared components, earns a theme only when it causes a user problem. Here, mismatched invoice tables slow task success for users finding past invoices, so that becomes the fifth theme. Five to eight themes is our working rule, a number leadership can hold in one meeting. Rewrite your own feature rows before you score anything.

How do you score a UX strategy roadmap with RICE?

Score each of the prioritized themes on a UX roadmap with RICE: reach times impact times confidence, divided by effort, with confidence set by the evidence level.

RICE prioritization comes from Intercom, where Sean McBride defined the RICE scoring scales: reach as people affected per period, impact per user from 3 (massive) to 0.25 (minimal), and confidence as 100%, 80% or 50%. He set the effort estimate in person-months; for UX themes we count reach as users per quarter and effort in person-weeks of design and engineering.

We tie confidence to the evidence ledger: usability testing or analytics earns 100%, mixed evidence such as a few support mentions with no test earns 80%, and stakeholder opinion alone earns 50%. That mapping is our practice, not Intercom's. The highest RICE score goes first unless a dependency blocks it, as the card shows for the five example themes.

Mobile approval has the largest reach times impact on the card, yet at 50% confidence and 10 person-weeks it ranks last. A must-have sort or a value-versus-effort grid is faster, but neither gives the product team one shared number.

Effort agreed by engineering is what in-house roadmaps usually skip. Our maturity scoring and strategy step turns findings into RICE-scored initiatives in 2–4 days. Score your top five themes with engineering in the room.

Which success metric proves each theme worked?

Each of the prioritized themes on a UX roadmap gets one success metric from the Google HEART framework, with a baseline and target set before work starts.

The Google HEART framework comes from a 2010 paper by Google's Kerry Rodden, Hilary Hutchinson and Xin Fu, presented at the Conference on Human Factors in Computing Systems (CHI); it names five categories of user-centered metrics. Happiness is attitude, such as a survey score.

Engagement is how often, how intensely or how deeply people use the product, such as invoices sent per user per week. Adoption is new users of a product or feature, such as activation rate, the share of new users who reach the first key action. Retention is who comes back, and task success covers efficiency, effectiveness and errors, such as the share of admins finishing an invite without help.

The paper's Goals-Signals-Metrics process picks the number: state the theme's goal, name the user behavior or attitude that would show success, then turn that signal into a metric you track in GA4 or a survey. The grid applies it to three example themes.

Each theme metric then becomes a key result the product team reports under its objectives and key results (OKRs). Write the baseline from the last full quarter of data before a theme enters now.

How do you place themes on now, next and later horizons?

A UX roadmap puts a theme in now only with high confidence, a named owner and product team capacity this quarter; next waits on capacity, later on research.

Nielsen Norman Group splits roadmap time into now, next and future; we call the last column later and set each roadmap horizon in quarters. Three rules place themes on a now, next, later board:

• Now (this quarter): 100% confidence from evidence, a theme owner, a baseline and effort that fits capacity, because a theme missing one of them stalls mid-quarter.
• Next (the following quarter): scored themes waiting on capacity or a dependency, plus research tasks that lift a low score, so the queue is ready.
• Later (two or more quarters out): themes at 50% confidence (opinion only), because their first task is research, not design.

A later theme does not wait idle: its usability testing round or interview study sits in next, and once confidence rises, the theme is re-scored. Beyond now, keep time horizons in quarters, not dates. Sort your scored list into the three columns before the roadmap workshop.

Who owns the roadmap, and what does the workshop decide?

One roadmap owner, usually the head of product or design, keeps the UX roadmap; each of the prioritized themes has one theme owner, agreed on in a 2-hour roadmap workshop.

The roadmap owner keeps the document current and runs the reviews; a theme owner is one named person who answers for a theme's metric. Write down three decision rights:

• Add a theme: anyone, with evidence attached, because an opinion-only idea enters at 50% confidence.
• Move a theme between horizons: the roadmap owner, at a review, so priorities do not shift in hallway conversations.
• Retire a theme: both owners together, when the metric hits target or new evidence removes the problem.

The roadmap workshop is a working session with stakeholders, not a UX strategy training course. On our engagements, the roadmap is presented in a 2-hour workshop where owners and dates are agreed on; a FigJam board or one slide is enough. A five-block agenda:

1. Evidence recap: the ledger and the top user problems.
2. Scores: the RICE table, with engineering's effort estimate.
3. Objections: each leader challenges one score with evidence.
4. Owners and horizons: one theme owner and a now, next or later slot per theme.
5. The next review date, set before anyone leaves.

In the Mass Media Co. discovery workshop, we brought the client's stakeholders and users together to align the product revamp strategy with the business goals, covering product definition, information architecture and user flows. That was a product revamp, not a roadmap engagement, but the order carries over: goals first, screens later. Send the scored table a day ahead so objections arrive with evidence.

UX strategy roadmap example: one page, five themes

This UX strategy roadmap example fits on one page: a UX strategy statement on top, then five prioritized themes across now, next and later, each with score, metric and owner.

The one-page plan below is a UX strategy example built for the invented B2B SaaS invoicing product, so every number is illustrative. Its top band is the UX strategy document:

Goal: more new accounts send their first invoice without help this year. Users and problem: admins and finance managers at small firms who need support to get set up. Success measures: activation rate and invite task success.

The product team has 10 person-weeks this quarter, enough for the invite (4) and first-invoice (6) themes, so export waits despite its 100% confidence. The board shows each theme's horizon, score, metric and owner.

Copy two habits. The mobile research task sits in next, so a 50% theme earns its way up with evidence instead of argument. Every theme in now carries a baseline, so the quarterly review can say whether it worked. Write your own top band before you fill the lanes.

When do you review a UX strategy roadmap or get help?

Review the UX strategy roadmap with the product team every quarter, check it monthly, and get outside help when leaders disagree on the prioritized themes.

The review cadence has two parts:

• Monthly check: 30 minutes (our practice) on the themes in now and anything blocked, so problems surface before the quarter ends.
• Quarterly review: re-score themes with new evidence, move them between horizons, retire themes that hit target and re-check the UX maturity stage. In ongoing advisory, quarterly roadmap reviews develop a company's UX maturity one stage at a time on the Nielsen Norman Group model.

Six mistakes undo a UX design roadmap:

• Features instead of problems, because a feature row cannot be measured or challenged.
• No baseline, so nobody can tell whether a theme worked.
• Every theme in now, which spreads capacity thin and finishes nothing.
• Scores set by the loudest stakeholder, because confidence then reflects rank, not evidence.
• No theme owner, so the metric belongs to no one.
• A roadmap never revisited, because scores go stale as new evidence arrives.

Outside help earns its fee when leaders disagree on priorities, nobody has time to collect evidence or the backlog has no shared scoring method. Our engagement delivers the interviews, the RICE and HEART work and the roadmap workshop at an engagement price of $5,000–$15,000 and an engagement duration of 2–3 weeks; our breakdown of what a UX strategy engagement costs shows the four factors that move the price. Ongoing advisory adds weekly sessions and quarterly roadmap reviews, and interface design work is quoted separately.

Before you book anything, run the intro's test on your own plan: count the rows that name a user, a problem, evidence, a metric and an owner. Every project begins with a free consultation and a fixed-scope proposal, so send us your current roadmap or backlog with that count; in the consultation we point out which rows are still features and what evidence is missing.

FAQs