Product Roadmap Mindmap
The code
mindmap
root((Roadmap))
Now
Checkout redesign
Bug backlog
Next
Mobile app beta
Usage-based billing
Later
Public API
Partner marketplace
Risks
Hiring
Compliance review
How this template works
Roadmaps fail when they turn into spreadsheets. This mindmap keeps one at the altitude where decisions actually happen: a root labeled Roadmap, four branches for Now, Next, Later, and Risks, and a handful of concrete items under each. In a planning meeting you can paste the whole thing into the editor, move an item between branches, and watch the picture update instantly.
The syntax is the simplest in the Mermaid family. The first line, mindmap, declares the type. The second line, root((Roadmap)), creates the central node; the double parentheses are what render it as a circle, which visually separates the root from everything else. Every line after that is plain text whose indentation level defines its position in the tree. Now, Next, Later, and Risks sit one level in, so they become the main branches. Items like Checkout redesign and Mobile app beta sit two levels in, so they hang off their parent branch. There are no arrows, no node ids, and no semicolons — the whitespace is the entire grammar.
The gotcha is that indentation is load-bearing. Mix a tab into a file that otherwise uses spaces and the parser will either error out or attach a node to the wrong parent, and the mistake is invisible until you render. Keep the depth shallow, too: three levels, as used here, stays readable, while a fourth level turns the map into a wall of text. Finally, avoid parentheses inside labels, because they are shape syntax and will change how a node renders.
To make it yours, rename the branches to quarter labels, duplicate the file per team, or promote Risks to the first branch if your planning culture leads with threats. The map is short enough to restructure in a minute, which is the point.
Related templates in the same family: the learning path mindmap for curricula, the business model mindmap for strategy canvases, and the project WBS mindmap for breaking work into deliverables. The mindmap diagram guide covers the full syntax.
Variations to try
- Add a quarter branch such as Q3 with its own children when you need time-based grouping instead of Now and Next.
- Duplicate the file and keep one version per team so each squad owns its own slice of the map.
- Promote the Risks branch to the top by moving it directly under the root to change the reading order.
