Roadmap items
A roadmap item is the basic unit of a Roadmap Flow roadmap. Everything on the canvas is an item, or a way of arranging items. This page explains what an item is and how to pick the right size for one.
What an item represents
An item is one meaningful piece of product work — a feature, an initiative, a launch, a piece of discovery. It is the thing a stakeholder would ask about by name.
Each item can carry:
- a title and short description;
- a status — where the work is;
- a priority — P0, P1, or P2;
- a confidence level — how sure you are;
- a type — discovery, delivery, GTM, rollout, marketing, or training;
- a time horizon — Now, Next, Later, or Not Doing;
- start and target periods — months or quarters; the picker opens on months;
- one or more workstreams it belongs to;
- an owner team;
- optional dependencies, external links (Azure DevOps unless you pick another kind), and a decision-needed flag.
You do not have to fill in everything. Title, status, and priority are enough to start; the rest makes the roadmap more honest and more useful in Check.
Add item opens a new item with its name selected, ready to type over. Give it a name, or set anything at all, and it stays. Close it untouched — the X or Esc — and it is gone, as if you had never pressed the button; the button at the bottom says Name it to keep it until then.
Picking the right grain
The most common roadmap mistake is items at the wrong size.
- Too big — "Improve onboarding" as a single item that never moves for a year. Split it into the things that actually ship.
- Too small — "Add a tooltip to the settings page". That is a task, not a roadmap item.
A good test: an item is the right size if a stakeholder would recognize it as a decision you made about where to spend effort.
What an item is not
An item is not an engineering ticket. Roadmap Flow does not track sprints, story points, or individual assignees. If you find yourself wanting those, keep them in your delivery tool and link to it from the item instead.