Mind map template · Planning

Product roadmap template, as a mind map

Lay out a year of product work on one map: a theme for each quarter, the features behind it, how you will know it worked, and the milestones in between.

Shiko is in closed beta: this takes you to the wishlist first.

The template as it opens. Every prompt is a node you answer under or replace.

What's inside

Product vision

  • Quarter 1: Foundation
    • Theme: the problem we solve first
    • Features (a task list)
    • Success metric
  • Quarter 2: Growth
    • Theme: what makes people come back
    • Features (a task list)
    • Success metric
  • Quarter 3: Scale
    • Theme: what lets us serve many more people
    • Features (a task list)
    • Success metric
  • Quarter 4: Polish
    • Theme: what makes it a joy to use
    • Features (a task list)
    • Success metric
  • Milestones
    • Beta launch
    • Public launch
    • First 1000 users
  • Risks and dependencies
    • What could delay us?
    • What do we depend on other teams for?
  • Ideas backlog
    • Good ideas that did not make the cut

How to run it with your team

  1. Start from the product visionWrite the vision in the middle. Every quarter on the map should move you closer to it.
  2. Give each quarter a themeFoundation, Growth, Scale, Polish: each quarter has the problem it solves, a feature list and one success metric.
  3. Mark the milestonesBeta launch, public launch, first 1,000 users: the moments the whole team plans around.
  4. Park the restRisks and dependencies get their own branch, and good ideas that did not make the cut go into the backlog instead of being lost.

What is a product roadmap?

A product roadmap is a plan of where a product is going over the next months or year, and why. It links the product vision to the work: which problems the team will solve, roughly in what order, and how it will know each step worked. Product managers own it, but engineering, design, sales and leadership all read it.

A good product roadmap is about outcomes, not a list of dates. The common product roadmap format groups work into themes per quarter or release, each with a few features and a success metric, plus milestones the whole company plans around. It names the risks and what the team depends on, and it says what is not being done, so people stop asking.

Roadmaps change every quarter, so they need to be easy to edit and easy to read. On a mind map the vision sits in the middle, each quarter is a branch with its theme, features and metric, and moving a feature to another quarter means moving it to another branch.

When to use it

When you plan the next few quarters, and whenever you need to explain the plan to people outside the team. Unlike a roadmap template in a spreadsheet, a map shows the year at a glance; the detail sits one level down.

Review it at the start of each quarter: move features between quarters, check the success metrics, and pull from the backlog.

Questions

Can my whole team edit it at once?

Yes. Everyone you invite works on the same map live, and you see who is typing where.

What does a sample product roadmap look like?

For a recipe app: Quarter 1, Foundation, theme "people can save recipes", features search and saving, metric 40% of new users save one. Quarter 2, Growth, theme "people cook again", meal plans and a shopping list, metric weekly return rate. Milestones: beta in March, public launch in June.

Can I change the quarters?

Yes. Rename them to months, releases or anything else; the template becomes your own map.

Can I share it with people who only read?

Yes. When you share a map you choose whether each person can edit or only view.