Outcome-Based Roadmap vs Feature-Based Roadmap
People think a roadmap has to list features, and it does not. A feature roadmap lists things to ship, often with dates, and is done when they ship. An outcome roadmap lists changes to see, like more users finishing sign-up, and is done when the number moves. The first is easy to read. The second leaves the team free to find the best fix.
Outcome-Based Roadmap
A roadmap that lists results to reach, not features to build.
An outcome-based roadmap lists the results a team wants, not the features it will build. Each item is a change in what users do or in a number, like fewer people quitting at sign-up. The team then tries ideas to reach it. If the first idea fails, they try another. The roadmap stays the same, because the goal did not change.
Feature-Based Roadmap
A roadmap that lists features to ship, often with dates.
A feature-based roadmap lists the features a team plans to build, often with dates. Each item is a thing to ship, like a new search bar. It is easy to read and easy to check off. But it does not say what each feature should change for users. A team can ship every item and still miss its goals.
In one line
- Outcome-Based Roadmap
- A roadmap that lists results to reach, not features to build.
- Feature-Based Roadmap
- A roadmap that lists features to ship, often with dates.