# Anatomy of a product roadmap: five components and an example

> The five parts every useful roadmap needs (product vision, business objectives, themes, timeframes and a disclaimer), what each one does, and a product roadmap example: Sofia's first one-page roadmap for CatChow, plus a fill-in template.

- Course: [Outcome-Based Product Roadmaps](https://productovi.com/courses/outcome-based-roadmaps.md)
- Module: Why roadmaps need a rethink
- Lesson 3/15, ~41 min
- Source: https://productovi.com/courses/outcome-based-roadmaps/roadmap-components

## What to include in a product roadmap

**Alex Tutor:** Back at CatChow, the roadmap page for Ian is still yours to draft.

**Sofia:** It's Thursday. I have outcomes, I have Brandon's clinics, I have Ian's churn problem. But I still don't know what the page itself should look like.

**Alex Tutor:** There's no single template, but every useful roadmap tells the same short story: where we're going, how we'll know we're getting closer, what has to be true, in what order, and a reminder that it will change.

**Alex Tutor:** Each part of that story is a component. Five of them are essential: **product vision**, **business objectives**, **themes**, **timeframes** and a **disclaimer**. Leave one out and the story has a hole. At the end you'll get a one-page example and a template.

![A poster in five stacked layers: a distant star, a target, a row of signposts, three columns of decreasing sharpness and a small folded card.](https://productovi.com/courses/outcome-based-roadmaps/inline/roadmap-components-illustration-2.webp)

*Where we're going, how we'll know, what has to be true, roughly when, and how firm it is.*

**Alex Tutor:** Before we go through them one by one, match each component to the reader's question it answers.

> **Exercise:** Match each essential component to the question it answers.

**Sofia:** Five. That fits on one page.

**Alex Tutor:** It should. We'll go from top to bottom, starting with the vision. **Product vision** is the future the product is working towards: who benefits and how their life is different. Every other item traces back to it.

**Sofia:** For CatChow… “Cat owners never have to think about running out of the right food”?

**Alex Tutor:** A good draft; we'll polish it in module 2. Next come **business objectives**: the measurable results the company expects from the product. They explain why the roadmap is worth funding.

**Ian:** For next year I care about two things: subscription revenue, which means fixing churn, and the vet clinic channel. Everything else is secondary.

> **Exercise:** Which of these is a **business objective**, rather than a vision, a theme or a feature?

## Themes: what has to be true

**Alex Tutor:** So there are your objectives: grow subscription revenue by keeping subscribers longer, and grow the vet clinic channel. Two or three is plenty; ten objectives means no priorities.

**Sofia:** And where do my outcomes from yesterday go?

**Alex Tutor:** Into **themes**. A theme answers: what would have to be true for us to reach the vision and hit the objectives? It's a customer need or problem, phrased as a result, not as a solution.

**Alex Tutor:** “Subscribers never run out between deliveries.” “Clinics restock prescription diets without phoning us.” “New owners pick the right food on their first order.” Each one gathers many possible features under one need.

**Sofia:** And the features from the spreadsheet?

**Dataset (CSV):** [CatChow's request spreadsheet](https://productovi.com/datasets/outcome-based-roadmaps/roadmap-components/catchow-requests.csv)

The 40 feature requests from sales, support and the founders that the product team starts the course with, in the order they sit in the spreadsheet. Synthetic data made for this course.

- `id`: Row ID
- `request`: The request as written in the spreadsheet
- `source`: Who asked: sales, support or the founders

**Alex Tutor:** They become candidate solutions under a theme, if they appear at all. Reminders, one-click reorder and flexible delivery dates all sit under “never run out”. The team chooses among them later.

**Alex Tutor:** One rule: every theme should support at least one business objective. A theme that serves none is a hobby.

> **Exercise:** Which of these are well-phrased **themes** for CatChow's roadmap? Select all that apply.

## Timeframes instead of dates

**Lucy:** Before you put these in columns: please don't give me a month for each one. Now I can talk about. Next I can guess. Later is fog.

**Alex Tutor:** Lucy has just described **timeframes** perfectly. Instead of dates, use broad buckets: quarters, halves, or **Now / Next / Later**. The order alone tells people what matters first.

**Alex Tutor:** The buckets get wider and fuzzier with distance: Now is detailed and fairly certain, Later is a direction. That's honest, because it matches what the team actually knows.

![A road runs toward the horizon with a blue delivery van in front; near the viewer every stone is sharp, further away the road widens and fades into mist.](https://productovi.com/courses/outcome-based-roadmaps/inline/roadmap-components-illustration-3.webp)

*Now is detailed and fairly certain; Later is a direction.*

**Sofia:** Ian will ask what Now means in calendar terms.

**Alex Tutor:** Then say it on the page: for example, Now is this quarter, Next is the following one or two, Later is beyond that. Exact dates go only on hard external events, like a conference where you're launching.

![Now is this quarter, detailed and fairly certain; Next is the following one or two quarters, a guess; Later is beyond that, only a direction.](https://productovi.com/courses/outcome-based-roadmaps/diagrams/m1-l3-now-next-later.png)

*Broad buckets that match what the team actually knows.*

> **Exercise:** Which item on CatChow's roadmap can reasonably carry an exact date?

## The disclaimer

**Sofia:** And the fifth one, the disclaimer. Isn't that just legal small print?

**Alex Tutor:** It's more than that. A **disclaimer** says plainly that this is the current plan and that it will change as we learn. It protects the team from “but you promised”, and it warns readers not to bet their own plans on Later.

**Alex Tutor:** For an internal roadmap, a date and one honest sentence are enough. A version for clients like PurrPoint needs firmer wording, and a public company would check it with its lawyers.

**Brandon:** Wait, so I can show this roadmap to PurrPoint?

**Alex Tutor:** Not this version. We'll get to external roadmaps in module 5. For now, it's for CatChow's own people.

> **Exercise:** A disclaimer is only needed on roadmaps that customers will see.

**Alex Tutor:** Two disclaimers for the same page. Which one will people actually read?

> **Exercise:** Which disclaimer does its job on CatChow's internal roadmap?

## What's optional

**Sofia:** What about features, statuses, confidence levels? Lucy will want those.

**Alex Tutor:** Those are optional extras: likely features, stage of development, confidence, target customers, product areas. Add them only when a particular audience needs them. We'll cover them in module 3.

**Alex Tutor:** And some information isn't part of the roadmap at all: project schedules, budgets, architecture. People will expect you to know it, but it lives in other documents.

**Sofia:** So: five essential parts, extras on demand.

**Alex Tutor:** Right. A roadmap overloaded with extras starts to read like a project plan again, and you've only just escaped one.

**Alex Tutor:** Lucy has a request about the extras. What do you tell her?

> **Exercise:** Lucy asks Sofia to add task owners, sprint numbers and each team's budget to the roadmap page for Ian. What is the best response?

## Checking the chain

**Alex Tutor:** Before you write it down, one check. Take any item and walk up: which theme is it under, which objective does that theme serve, and how does that lead to the vision?

**Sofia:** Reminders: under “never run out”, which serves subscription revenue, which gets us to “owners never think about running out”. It works!

**Alex Tutor:** And dark mode?

**Sofia:** …Under nothing. It can stay in the spreadsheet.

**Alex Tutor:** Exactly. The check takes a minute per item, and it's the fastest way to clear a spreadsheet of wishes.

![A chain of linked rings hangs from a star; one small card hooks onto the lowest ring, another dangles beside it with nothing to hook onto.](https://productovi.com/courses/outcome-based-roadmaps/inline/roadmap-components-illustration-4.webp)

> **Exercise:** Order these CatChow items from the broadest to the most concrete.

## Writing the disclaimer

**Lucy:** One request: make the disclaimer something people actually read, not grey text nobody notices.

**Alex Tutor:** Good point. Put it where everyone sees it, keep it human, add the date of the last update and say how often the roadmap is reviewed.

**Sofia:** Something like “We'll get things wrong and fix them”?

**Alex Tutor:** Close. Say what it is, what it isn't, and when it changes.

**Sofia:** Should I also say how often we review it?

**Alex Tutor:** Yes. A monthly review tells readers the roadmap is alive, and when to come back for news.

> **Exercise:** Write the disclaimer for the internal version of CatChow's roadmap (1–3 sentences).

## A theme for the clinics

**Brandon:** Where are my clinics on this page? If PurrPoint isn't on it, I'm in trouble.

**Sofia:** They're there as a theme, not a feature. Let me phrase it properly.

**Alex Tutor:** Remember the rules: a customer need phrased as a result, no solution named, linked to one of Ian's objectives.

**Brandon:** And please make it sound like something I can explain to a clinic director.

**Alex Tutor:** Fair request. If a clinic director wouldn't recognize the problem, the theme is written from our side, not theirs.

> **Exercise:** Write one theme for CatChow's vet clinic customers. Give the theme itself, the business objective it supports, its timeframe (Now, Next or Later) and one signal that would show progress.

## Sofia's first roadmap

**Alex Tutor:** Now put it all together. This is the first version of CatChow's roadmap; we'll keep improving it until the end of the course.

**Sofia:** One page, five components, no Gantt chart.

**Alex Tutor:** And no 40 features. Use what you've learned this week: Ian's objectives, Brandon's clinics, Lucy's Now / Next / Later and the outcomes from the spreadsheet.

**Sofia:** And the rows that don't fit anywhere, I just leave off?

**Alex Tutor:** Leave them off and say why in one line. When someone asks where their idea went, you'll have an answer that isn't “I forgot”.

> **Exercise:** Sketch the first version of CatChow's roadmap with all five essential components.

## A product roadmap example and a one-page template

**Alex Tutor:** Here's a product roadmap example to compare with your sketch: one version of CatChow's page, built from the same facts. Your targets can differ. What matters is that every row climbs to an objective.

> **CatChow's product roadmap, version 1**
>
> **Product vision (draft):** cat owners and vet clinics never have to worry about running out of the right food.
>
> **Business objectives:** (1) monthly subscriber churn from 9% to 6%; (2) partner clinics from 54 to 80, with all 14 PurrPoint clinics kept.
>
> **Timeframes:** Now = this quarter; Next = the following one or two quarters; Later = beyond that, direction only.
>
> | When | Theme (objective) | Signal | Candidate features |
> |---|---|---|---|
> | Now | Subscribers never run out between deliveries (1) | Cancellations citing running out: 30% → 15% | Reorder reminders, flexible delivery dates |
> | Now | Clinics restock prescription diets without phoning us (2) | Stock-outs: 6 a month → 1 | Clinic ordering portal or automatic reorders; needs the new warehouse system |
> | Next | New owners pick the right food on their first order (1) | “Which food?” calls: 250 a month → 100 | Food-picker quiz |
> | Later | Long-term subscribers have reasons to stay beyond price (1) | Set when it moves to Next | Loyalty points, if churn is still high |
>
> **Left off:** dark mode and birthday greetings serve no objective; the mobile app is a solution still looking for a problem.
>
> **Disclaimer:** Updated 2 October. This is our current plan, not a commitment to features or dates. We review it every month; Next and Later will change.

**Sofia:** Can I reuse the layout for another product, like the bookstore?

**Alex Tutor:** Yes. Here it is as a blank product roadmap template. Fill it from the top: vision, then objectives, then themes. Features come last, and only as examples.

> **One-page product roadmap template**
>
> **Product vision:** [who benefits] can [what is different in their life].
>
> **Business objectives (2–3):**
> 1. [Objective]. Signal: [metric] from [baseline] to [target]
> 2. [Objective]. Signal: [metric] from [baseline] to [target]
>
> **Timeframes:** Now = [this quarter]; Next = [the following one or two]; Later = [beyond, direction only].
>
> | When | Theme: a customer need phrased as a result | Objective | Signal | Candidate features (examples) |
> |---|---|---|---|---|
> | Now | | | | |
> | Now | | | | |
> | Next | | | | |
> | Later | | | | |
>
> **Left off, and why:** [row]: [serves no objective / no problem behind it yet]
>
> **Disclaimer:** Updated [date]. This is our current plan, not a commitment to features or dates. We review it every [month]; Next and Later will change.

## What to remember

**Sofia:** I think Ian will actually like this more than 40 dates. He can see what we're aiming at and why.

**Alex Tutor:** And everyone else can see where they fit. That's the job of the five components.

> **Key ideas**
>
> - A useful roadmap has five essential components: **product vision**, **business objectives**, **themes**, **timeframes** and a **disclaimer**.
> - Themes are customer needs phrased as results; each supports at least one business objective, and features appear only as candidate solutions under them.
> - Timeframes are broad buckets such as Now / Next / Later, wider and fuzzier with distance; exact dates only for fixed external events.
> - A short, dated disclaimer keeps everyone reading the roadmap as a plan that will change.
> - Optional extras (features, stage of development, confidence, target customers, product areas) are added only when an audience needs them.

**Alex Tutor:** That wraps up module 1. In module 2 we'll dig into the “why” behind the roadmap: inputs, the product vision and objectives with key results.

- Previous lesson: [Outcomes over outputs](https://productovi.com/courses/outcome-based-roadmaps/outcomes-over-outputs.md)
- Next lesson: [Gathering inputs: life cycle, market, customers, stakeholders](https://productovi.com/courses/outcome-based-roadmaps/gathering-inputs.md)

---
Productovi Learning. Free, no sign-up needed to read.