Outcome-based roadmap template — editable, free
An outcome-based roadmap names the change you want to see and treats the features under it as bets, each carrying a confidence, not a status. The test it applies is whether you can drop a bet without dropping the outcome. Ten bets under four outcomes, including the ones that were dropped.
| View | Groups by | Visible fields |
|---|---|---|
Outcomes | Outcome | Name, confidence, owner |
Leadership | Outcome | Name, outcome, confidence, quarter — owner and status hidden |
Dropped bets | Outcome | Name, outcome, notes — only the bets marked dropped |
All bets | Nothing — one flat list | Name, outcome, confidence, status, owner, dates, notes |
What is an outcome, and what isn’t one?
A number that moves: support contacts per account, time to first value, the share of new teams that come back in week two. If you can ship it, it’s a feature. If you can only influence it, it’s an outcome, and the items underneath are attempts at that influence.
The usual failure is a feature wearing an outcome’s name. Improve onboarding is the work restated. The outcome is whatever changes when onboarding improves, and naming that’s what buys you the right to stop early.
What is in this template?
Ten bets across four outcomes, each with a confidence value, an owner and a quarter. Two are marked dropped and carry a note on what was learned, because a template showing only the bets that survived teaches the wrong habit.
The leadership timeline groups by outcome, shows confidence and hides owner and status. Confidence is the right signal for that audience — it says these are attempts, which is the claim the format makes. Change a bet on the outcome board and the leadership view is already current.
Who is this the wrong format for?
Anyone downstream who needs a named thing on a named date. A rep can’t take a metric into a customer conversation, and roadmap for sales team sets out what that audience needs instead. A team waiting on a dependency from you is in the same position.
It’s also wrong when the outcomes were written after the work was chosen. Outcomes fitted to a list somebody already committed to are labels, and the item test in what to include in a product roadmap catches most of them before anyone else has to.
Where the format earns its place is the meeting: stopping a bet because the measure already moved is a decision, and the roadmap review meeting is where it gets made. If what your leadership group has actually agreed is a goal rather than a measure, a goal-oriented roadmap template is the nearer shape to start from, and the items can move under outcomes once the numbers exist.
Common mistakes
Writing a feature and giving it an outcome-shaped name. "Improve onboarding" is a feature wearing a metric’s clothes; the outcome is the number that moves when onboarding improves.
Keeping the rest of a list after the measure moved. If the first two bets hit the target, the remaining items under that outcome are work you no longer need, and shipping them anyway turns the roadmap back into a feature list.
Deleting the bets you dropped. Those are the evidence that the outcome was the commitment instead of the feature. Keep them in the file with a note saying what you learned.
Handing this format to an audience that needs dates. A sales team or a dependency owner needs a named thing on a named date, and an outcome doesn’t give them one.
Questions
What makes an outcome different from a feature?
An outcome is a number that moves. If you can ship it, it’s a feature; if you can only influence it, it’s an outcome, and the items under it are attempts at that influence.
How many bets should sit under one outcome?
Two or three at a time. Eight under a single outcome usually means the team has committed to all of them, which is a feature list with a metric written above it.
What happens when the measure hits its target?
Stop the remaining bets and say so in the review. Stopping early is the one thing an outcome roadmap can do that a feature roadmap can’t.
Why keep dropped bets in the file?
They’re the record that the outcome was the commitment. The dropped view keeps them with a note on what was learned rather than deleting the evidence.
Related
- What to include in a product roadmapOne test for every item, plus the three things that belong on no roadmap outside the squad.
- Roadmap for sales teamThe only view that hides quarters, because a rep repeats everything on it within the week.
- Now Next Later roadmap templateSequence instead of dates, with a board, two timelines and a table already saved.
Last updated