Choosing the Right Altitude for Your Journey Map

Every journey map is built from a specific vantage point. The choice of altitude — how high the map flies above the operational detail — determines what it can show, who can use it, and what decisions it can support. Getting altitude wrong is the most common structural mistake in journey work, and it rarely announces itself clearly.

The Altitude Spectrum

At one end, a map can operate at the lifecycle level: the full arc of the customer relationship from first awareness to long-term advocacy or churn. This altitude is appropriate for strategic planning — understanding where the experience is performing, where it is failing, and where organizational effort should be concentrated across quarters.

At the other end, a map can operate at the interaction level: the specific steps, screen flows, and decision points within a single touchpoint or feature. This altitude is appropriate for UX and product design — understanding how to improve a specific moment in the experience.

Between these extremes is a range of intermediate altitudes: major journey stages (the discovery experience, the onboarding experience, the return experience), sub-journeys within those stages, and interaction clusters within sub-journeys.

The mistake is not choosing the wrong altitude per se — it is descending below the right altitude before the work calls for it.

Why Designers Descend Too Early

Service designers with strong UX backgrounds tend to drift toward interaction-level detail because that is where their skills are sharpest and the problems are most tractable. The temptation is real: there are always specific flows to improve, specific screens to redesign, specific friction points to eliminate.

But interaction-level work, while valuable, does not serve the strategic purpose of journey mapping. A map that shows screen-by-screen flows for the checkout experience does not help leadership decide whether to invest in the checkout experience at all — or whether the Retention stage is a higher priority, or whether three overlapping initiatives are solving the same problem from different angles.

"Most service designers unintentionally descend too early: mapping processes, dependencies, screens, exception flows. These are valuable, but they are not Cartography. They are engineering diagrams."

The map loses its audience when it loses its altitude. Leadership cannot prioritize from an interaction-level map. It requires interpretation that the map does not provide, and it competes for attention with every other detailed document the organization produces.

Choosing the Right Altitude for Your Context

The right altitude is the highest one that still produces information the relevant audience can act on.

For a first-cycle journey map — the initial pass at understanding an organization's customer experience — the lifecycle level is almost always the right starting point. It establishes the shared picture that all subsequent work builds from. It can be produced in two to four weeks with existing organizational knowledge. And it is specific enough to identify the stages most worth improving.

For a second-cycle or focused initiative, the altitude can descend to a major stage: the specific onboarding experience, or the support resolution journey, or the renewal flow. This level is appropriate once the strategic priorities have been established at the lifecycle level and a specific area has been selected for deeper work.

The interaction level belongs in UX tools, not in the journey map. When a team has identified that the Activation stage needs improvement and has allocated resources to address it, the UX team takes over — in Figma, in user testing sessions, in detailed flow diagrams. The journey map points toward that work. It does not replicate it.

A Practical Altitude Test

Before fixing the altitude of a map, ask: who is the primary audience for this map, and what decision do they need to make?

If the audience is product leadership deciding where to focus the next quarter, the map should show the experience at the lifecycle level — experience scores by stage, prioritized opportunities, emerging solutions. If the audience is a UX team redesigning a specific flow, the map should show interaction-level detail within a specific stage.

If the same map is expected to serve both audiences, it will serve neither well. Two maps at different altitudes — one pointing to the strategic priorities, one supporting the UX work — will be more useful than a single map that tries to do both.