Journey Hierarchies: When Your Map Contains Other Maps

Customer journeys are not flat. Every end-to-end journey contains major stages. Each major stage contains sub-journeys. Each sub-journey contains specific interactions. These levels exist simultaneously, and the most useful maps know which level they are operating at — and why.

Ignoring this hierarchy is how teams produce maps that try to show everything and end up showing nothing useful at any level.

The Russian Doll Problem

Consider a retail business with an online store. The end-to-end customer journey runs from first brand awareness through purchase, delivery, use, return, and eventual loyalty or churn. Within that journey, the delivery experience is a significant stage — from order confirmation to arrival and first use.

Within the delivery experience, there is a sub-journey: the return process. A customer who needs to return a product goes through a distinct arc — discovering how to initiate the return, packaging the item, dropping it off, waiting for confirmation, receiving the refund.

Each of these is a legitimate customer journey. Each requires its own mapping if it is to be improved. But they operate at different altitudes, serve different purposes, and should not be mixed on the same map.

"Journeys exist inside one another like Russian dolls: the end-to-end shopping journey contains the delivery journey, which contains the return journey. All valid, but different altitudes."

What Happens When You Mix Altitudes

The most common symptom of altitude confusion is a map that is simultaneously too vague in some areas and too detailed in others. The lifecycle stages are high-level and strategic. But one of them — say, the onboarding stage — expands into seven sub-steps with detailed interaction notes, while the others remain as placeholders.

The resulting map cannot be used for strategic decisions about the whole experience because the detail is uneven — leadership cannot compare the onboarding stage to the retention stage when one is mapped to the screen level and the other is a single box. And it cannot be used for operational decisions about the onboarding stage because the surrounding context is too vague to establish priorities.

Uneven altitude is worse than consistent altitude. A map that is consistently strategic across all stages — with experience scores, prioritized opportunities, and emerging solutions at each — is more useful than one that dives deep in one area and stays abstract in all others.

How to Handle Hierarchies in Practice

The solution is a deliberate hierarchy of maps rather than a single map that attempts multiple altitudes.

Map 1: The lifecycle map. This is the strategic overview — all six lifecycle stages, experience scores, the top two or three opportunities per stage, emerging and Big Solutions. It exists to support quarterly planning and cross-team alignment. It is the map that leadership uses.

Map 2: The stage map. When a specific stage has been identified as a priority and resources have been allocated to address it, a more detailed map of that stage is built. This map shows the specific steps within the stage, the pains and gains at each step, the operational details that affect delivery. It exists to support UX design and product roadmapping.

Map 3: The sub-journey map. For specific high-stakes interactions — the return experience, the support escalation process, the renewal moment — a sub-journey map can be built that operates at the interaction level. This is the territory of UX designers and product owners, built in their tools and following their processes.

These three maps form a linked hierarchy. Each points to the ones below it. The lifecycle map references the stage maps for the priority areas. The stage maps reference the sub-journey maps for specific high-stakes moments. At no point does one map try to include the content of the others.

This hierarchy respects the different needs of different audiences and prevents the altitude confusion that makes comprehensive single maps so consistently underused.