Skip to content
BENIBIX Learn

Product Roadmap Types

Level 4 Β· Choosing what goes first

What a product roadmap is for, and its three common kinds. Feature lists, outcome goals, and three columns in place of dates.

Course contentsLesson 10 of 13

After this lesson you can

  • Say what a roadmap is and is not
  • Tell an outcome item from a feature item
  • Pick a roadmap kind for an audience

13 mincovers 4 glossary entries

Worth reading first: RICE Scoring and Kano Model

What a roadmap shows, and the three ways to draw one

A product roadmap is a shared picture of what a team plans to work on, and roughly when. It turns the strategy into an order of work. It is a plan, not a promise. Most roadmaps show the next 6 to 12 months, and anything further out is a guess that will change.

There are three common kinds. A feature-based roadmap lists things to ship, often with dates. An outcome-based roadmap lists results the team wants. A now-next-later roadmap sorts work into three columns instead of dates. They answer different questions, and many teams mix two of them on one page.

A feature-based roadmap is the oldest kind. It reads: tutorial in March, chat in April, badges in June. It is easy to read and easy to check off. Its weakness is that an item counts as done when it ships, even if it changed nothing. A team can finish every line and still miss its goals.

An outcome-based roadmap lists changes in what users do. It reads: 60% of new users send a first message, or churn under 3% a month. The team then tries ideas to reach each one. If the first idea fails, it tries another, and the roadmap does not change, because the goal did not change.

A now-next-later roadmap drops the dates. Now is what the team is doing this month. Next is what comes after, and is fairly clear. Later holds ideas that matter but are still fuzzy. The further right an item sits, the less detail it carries and the more likely it is to move or vanish.

Exact dates a year out are the classic mistake. They are guesses, and a sales team will promise them to clients anyway. Then a guess has turned into a broken promise. If a date truly matters, such as a law that starts on a set day, mark that one item and keep the rest loose.

Watch the now column too. If now holds twenty items, nothing is really now. Three to five items is a common limit, so the team can finish what it starts before it picks up the next thing.

The three kinds of roadmap

KindEach item isDone when
Feature-basedA thing to ship, with a dateIt ships
Outcome-basedA change in a numberThe number moves
Now-next-laterWork sorted by how sure it isIt leaves the now column

Which one to pick

  1. 1

    Feature-based

    Pick it when a client contract or a law needs a list of what ships, and by when.

  2. 2

    Outcome-based

    Pick it when the team keeps shipping features that change nothing, and the boss wants results.

  3. 3

    Now-next-later

    Pick it when plans change a lot, and dates a year out keep turning into broken promises.

The left side counts what was built. The right side counts what changed for users.

Worked example

Emma moves to three columns

Emma's old roadmap had 14 dated features for the year. By June, 5 had slipped and sales had already promised 3 of them to clients.

Her new roadmap has three columns. Now: faster checkout. Next: saved cards. Later: other currencies. The only date on it is a payment law that starts in October.

The words for this lesson4

Check yourself

Which item belongs on an outcome-based roadmap?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.