Journey Phase

Origin & evolution

Journey mapping grew out of service design and customer-experience practice, where the recurring move is to lay a person's interactions on a timeline and read the emotion and friction along it. The Nielsen Norman Group defines a journey map as a visualisation of the process a person goes through to reach a goal, built by compiling actions into a timeline and then layering thoughts and emotions on top. Phases are the top band of that timeline, with steps and actions nested beneath.

The phase vocabulary settled around familiar arcs (awareness, consideration, purchase, retention, advocacy) borrowed from marketing-funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → thinking, though product teams now write phases specific to their own product rather than the generic five. The useful discipline is keeping phases few; a map with twenty phases has just renamed its steps.

How it works in practice

A team mapping a project-management tool settles on four phases: Evaluate, Set Up, Adopt, Expand. The Set Up phase holds the steps a new admin walks through, create a workspace, invite the team, import existing projects. Reading the emotional line across phases, confidence sits high at Evaluate, drops sharply through Set Up, and recovers only at Adopt. That single observation👁️ObservationUser ResearchA specific behaviour or statement observedView reference → reframes the roadmap: the product does not have an adoption problem, it has a setup problem, and the fix belongs to three steps inside one phase.

Journey Phase vs. its neighbours

• Journey step🪜Journey StepExperience DesignA single step in a user journeyView reference → is the unit below the phase. A phase is a chapter ("Set Up"); a step is a scene within it ("invite the team"). A phase groups steps so the arc stays legible; a step is where actual interaction detail accrues.
• Customer journey stage🚏Customer Journey StageCustomer SuccessA stage in the post-sale customer journeyView reference → is the same altitude as a phase but framed from the business and funnel side (acquisition, conversion, retention) rather than the lived-experience side. Phases describe what the user is doing; stages describe where the relationship sits commercially. Teams often align the two, one stage spanning one or more phases.
• User journey🛤️User JourneyExperience DesignAn end-to-end map of a user experienceView reference → is the whole arc the phases divide. A phase is meaningless alone; it exists as one band of a specific journey for a specific persona🎭PersonaUserAn archetype representing a user segmentView reference →. The journey is the sequence; the phase is its segmentation.

In the graph

In the Unified Product Graph, a journey phase sits in the Experience, Design & Brand region as a container, one rung below the user_journey🛤️User JourneyExperience DesignAn end-to-end map of a user experienceView reference → anchor. A user_journey_passes_through_journey_phaseUser Journeypasses throughJourney Phasehierarchy edge places it within its arc, and a journey_phase_has_stepJourney Phasehas stepJourney Stephierarchy edge nests the steps beneath it. That two-level containment keeps the map navigable: a team can read the experience at chapter resolution across the phases, then drill into the steps and actions of the one phase where the emotional line dips, without flattening a long journey into an undifferentiated list of moments.