For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to choose between a journey map and a hierarchy map

Decide whether to keep a set of linked journey maps in a dedicated hierarchy space, or link them from a regular journey map instead.

A hierarchy map and a journey map are the same kind of map. You build both the same way, and both can hold linked journey cards that point to other maps. The real difference is where a hierarchy map lives and what it is for: it sits in the dedicated Hierarchies space, which is built to hold and manage a map of maps.

So the choice is mostly about convenience. If you want a separate, managed home for an overview that links out to other journeys, create a hierarchy map. If you only want to link a related map or two from a journey you are already working in, stay on the journey map.

Plan availability

Linked journey cards, and the hierarchy maps built from them, are available on the Repository plan and above. On the Free plan you can still build standard journey maps.

Linking is flexible, not a fixed tree

Linked journey cards connect maps in any direction, so a hierarchy takes whatever shape your experience does:

  • Zoom vertically - link a high-level lifecycle map down into a detailed micro-journey, and that into the steps beneath it.

  • Connect horizontally - link related journeys side by side, like the same stage across different channels or teams.

A hierarchy map is not a rigid top-down tree. It is a canvas you arrange to match how your journeys actually relate.

When to use a hierarchy map

  • You want a map of maps - a high-level overview or management map that links out to the detailed journeys around it, kept in its own space so it does not get lost among your regular journey maps.

  • You are managing a portfolio of connected journeys - keep the overview clean and let each linked map carry the granular detail, instead of cramming everything onto one map.

  • Different people own different journeys - link maps that separate teams maintain, while keeping them connected in one view.

A hierarchy map in the editor. A high-level journey sits in the top Linked maps lane, with two more detailed journeys linked in the lane below it. Each shows a map thumbnail, its name, and a Performance Indicator.
A hierarchy map: a high-level journey linked to the detailed journeys around it

When a single journey map is enough

  • You only need to link one or two related maps from a journey you are already building. Any journey map can hold linked journey cards, so you do not need a hierarchy map for the occasional link.

  • The work fits on one map without becoming hard to read.

To build a hierarchy map, see How to create a hierarchy map. For how the linking card works on any map, see How to use linked journey map cards.

Last updated