Decide what goes on the roadmap and keep the reasons
Group possible work into themes, branch each into features, ask what has to ship first, and keep a record of what you cut and why.
See it in action
A product roadmap for a project management tool trying to reduce churn, with the cuts the team made and the follow-ups that tested each one.
How it works
Start with your product, the time horizon and the goals the roadmap has to serve. Group the possible work into themes, each its own branch, and decide inside each theme before you put anything on a timeline.
-
Start with themes. Ask for roadmap themes for the next two quarters. Add a branch for each theme you want to consider.
-
Fill each theme with features. Under a theme, ask what it would include. “What would a collaboration suite include?” might return comments, permissions and notifications, each a branch you can size.
-
Ask what blocks what. Under any feature, ask “What has to ship before this?” and “What does this unlock?” The answers show which work has to come first.
-
Cut to fit. Put your constraints, such as team size and deadlines, in the map’s AI instructions so every answer takes them into account. Then collapse what does not fit. The collapsed branches are your “not now” list, with the reasoning still underneath.
Why a map before a timeline
A timeline asks you to order features before you know what each one costs you. The map holds the options first: what you could build, why, and what building it means you will not build. When someone asks why their feature is not on the roadmap, you can open the branch where you looked at it.
Example
Say you are planning the small-business tier of a CRM. The map branches into retention, onboarding and gaps against competitors. Under onboarding, a follow-up on a guided setup wizard shows it needs a reworked settings page first. Your team has put that refactor off for months, so it moves to the front of the plan, and you bring the branch to the quarterly planning review.