Goal-oriented roadmap template — editable, free
A goal-oriented roadmap hangs each item under the goal it is meant to move, with the target and the date attached to the goal rather than to the work. Three goals here, nine items under them, and the view most goal roadmaps leave out: the work that rolls up to nothing.
| View | Groups by | Visible fields |
|---|---|---|
By goal | Goal | Name, health, owner |
Leadership | Goal | Name, goal, health, quarter — owner and status hidden |
At risk | Goal | Name, health, owner, end date, notes — On track hidden |
Supports no goal | Nothing — one flat list | Name, status, owner, dates — only items with the goal field empty |
What makes a goal usable on a roadmap?
A measure, a target and a date. Cutting median time to first value from four days to one by the end of Q2 is something a roadmap can report against. Becoming the default tool for onboarding is a slogan, and a roadmap organised under slogans reports nothing back.
Three or four goals is the working number. Past that, items start rolling up to whichever goal is nearest rather than the one they serve, and the grouping stops carrying information.
What is in this template?
Nine items across three goals. Each item carries health — on track, at risk or off track — alongside its status, and the two are kept apart deliberately. Status says where the work sits. Health says whether the goal lands. A goal that’s off track with every item in progress is the ordinary case, and a roadmap showing only status can’t show it.
The leadership timeline groups by goal, shows health, and hides owner and status. That substitution is the point of the view: a director is there to decide whether a goal is worth continuing to fund, and ticket state doesn’t help them decide it.
The fourth view is the one most goal roadmaps leave out — the items that roll up to no goal at all. It’s also what makes a quarterly review survive contact with the numbers, which roadmap for QBR goes into field by field.
When is this the wrong frame?
When the goals are rewritten every quarter. The roadmap then becomes scaffolding that comes down twice a year, and the item history goes with it. Keeping one document current across those rewrites is the subject of how to keep a roadmap up to date, and the meeting where the health values actually get set is the roadmap review meeting.
It’s also the wrong frame when nobody has agreed the targets. A goal field with three labels in it and no numbers behind them adds a grouping and no information, and the roadmap reads as though it reports on something it doesn’t. Where the number exists but the goal around it doesn’t, an outcome-based roadmap template is the same shape with the measure on top, and it’s the easier of the two to start from.
Common mistakes
Goals with no number in them. "Become the default tool for onboarding" is a slogan; a goal a roadmap can report against carries a measure, a target and a date.
Hiding the work that supports no goal. The migration, the compliance item and keeping the lights on are real, and a roadmap showing only goal-linked work is describing a team nobody has.
Rebuilding the document every time the goals are rewritten. If goals change every quarter, the roadmap becomes scaffolding torn down twice a year, and the item history goes with it.
Reporting status where health is the question. That a ticket is in progress says nothing about whether the goal lands, and a goal that’s off track with everything in progress is the normal case.
Questions
How is this different from an outcome-based roadmap?
A goal carries a target and a date, and the roadmap reports progress against it. An outcome commits to a measure moving with no date attached, and the work under it’s expendable.
Where do the goals come from?
Usually the objectives the company already set for the quarter or the year. The roadmap doesn’t invent them; it shows which work rolls up to each one and which work rolls up to none.
Why show work that supports no goal?
Because it exists. The migration, the compliance item and the upkeep are real, and a roadmap that hides them describes a team with more capacity than yours has.
What is the health field for?
On track, at risk or off track, set per item. It answers whether the goal lands, which is a different question from whether a ticket has been picked up.
Related
- Roadmap for QBRTwo quarters back and two forward, shipped work left in place, and no owner column.
- Roadmap review meetingBring the diff and the decisions, not the board, and cancel the month there is nothing to decide.
- Roadmap for executivesFour fields to show, two to hide, and why each call goes the way it does.
Last updated