Strategy

Outcome roadmap

Quarters expressed as measurable outcomes, each with a target metric, current baseline and a confidence rating.

What it is

An outcome roadmap plans in changes to customer behaviour rather than in features. Each row names an outcome, the metric that shows it moving, where that metric stands today and where you want it, so the sheet reads as a set of intentions rather than a delivery schedule.

The shape exists because a feature roadmap answers the wrong question. It tells stakeholders when something will arrive, which they reasonably treat as a commitment, and it tells the team nothing about why. When the feature ships and the number does not move, there is no way to tell whether the work failed or was aimed at the wrong thing.

Bets stay visible without being promised. A bet is what you might try, and you delete one the moment it is disproved without touching the outcome it sat under.

When to use it

  • Leadership has asked for a roadmap and you want to answer without promising dates for work nobody has started.
  • The current roadmap is a list of features and the team cannot say what any of them is meant to change.
  • You are planning a quarter and want every item to carry a baseline and a target rather than a size.
  • Several teams share a goal and you need one page showing how their work adds up.

The columns

  • Quarter
  • Outcome
  • Metric
  • Baseline
  • Target
  • Gap
  • Confidence
  • Owner
  • Bets under way

The template

QuarterOutcomeMetricBaselineTargetGapConfidenceOwnerBets under way
Q1 2026New admins reach a working integration without helpShare of new workspaces with one live integration by day 722%40%18 ptsMediumR. AdeyemiGuided setup, template gallery
Q2 2026Teams keep their data current after the first monthShare of workspaces syncing weekly at day 6051%65%14 ptsLowJ. WhitakerSync health email, one click reconnect
Q3 2026Billing questions stop reaching supportInvoice contacts per 100 accounts per month94Minus 5MediumR. AdeyemiSelf serve invoice history, clearer proration note

Gap is Target minus Baseline, so a metric you are trying to bring down shows a negative gap. That is the point of the column, and it saves an argument later about which direction counts as progress.

Confidence bands

Pick one of three, and write the reason in a comment on the cell.

  1. High. A comparable change has already moved this metric on this product, and you have the before and after.
  2. Medium. The evidence is real but indirect, from another segment, another product or a published study.
  3. Low. The outcome rests on an assumption nobody has tested yet.

A quarter with three Low outcomes is not a roadmap, it is a research plan, and it is better to say so in the review than to discover it in month three.

How to keep the sheet honest

  • Three outcomes a quarter at most. Anything beyond that is a wish list.
  • One row per outcome. If you need two metrics to describe it, it is two outcomes.
  • Bets are what you might try, not what you have promised. Delete a bet the moment it is disproved and leave the outcome alone.
  • Read the baseline column again at the start of every quarter. A stale baseline makes a finished outcome look unfinished.

Questions people ask

Does this replace a release plan?
No. A release plan says when something reaches customers and a roadmap says what you are trying to change. Teams that need both keep them apart, because merging them turns every outcome back into a date.
What if leadership wants dates?
Give them the quarter column and the bets. A quarter is honest about the precision you actually have, and the bets show what is under way without turning an idea into a promise.
How many outcomes belong in a quarter?
Three at most. Beyond that the sheet becomes a wish list, and nothing in it gets the attention that moves a number.
What if a metric moves the wrong way?
Leave the row and write what you learned beside it. A roadmap that records only the outcomes that worked teaches nobody anything.