Journey Action

Origin & evolution

Actions are the base layer of the journey-mapping method that grew out of service design and customer-experience practice. The Nielsen Norman Group describes building a map by first compiling a person's actions into a timeline, then layering thoughts, emotions, and touchpoints👆TouchpointCustomer SuccessA customer interaction touchpointView reference → on top. Actions come first because they are observable; everything else is interpretation hung on them.

The discipline that sharpened over time is resisting the urge to round actions up into steps. "Onboards" is not an action, it is a step made of actions: opens the email, clicks the link, sets a password, lands on the dashboard🎛️DashboardData & AnalyticsAn analytics dashboardView reference →. Keeping the action layer granular is what lets a map locate friction at the resolution where a designer can actually intervene.

How it works in practice

A team maps the checkout step of a mobile store and lists its actions in order: tap "Buy", select a saved card, enter the CVV, tap "Confirm", wait for the spinner. Session data shows a 22 percent drop at "enter the CVV". Because the action is named at this grain, the cause is findable: the keyboard covers the field on smaller screens, so users cannot see what they are typing. The fix is one input's scroll behaviour. Had the map only recorded "user pays", the drop would have looked like a checkout problem and invited a redesign of the whole step.

Journey Action vs. its neighbours

• Journey step🪜Journey StepExperience DesignA single step in a user journeyView reference → is the container one level up. A step is a unit of progress ("complete payment"); an action is a single move inside it ("enter the CVV"). A step groups actions toward a sub-goal; an action is indivisible.
• Journey phase🔖Journey PhaseExperience DesignA named phase in a user journey that groups a sequence of actions the user performs to reach a milestone.View reference → is two levels up, the chapter of the whole arc. An action belongs to a step, which belongs to a phase. The phase tells you where in the journey you are; the action tells you exactly what the user's hands are doing.
• Touchpoint is where the action happens, the channel or surface the user interacts with (an app screen, an email, a call). An action is the verb; a touchpoint is the place. The same action can occur across different touchpoints, and one touchpoint can host many actions.

In the graph

In the Unified Product Graph, a journey action sits in the Experience, Design & Brand region as a leaf, the terminal node of the journey hierarchy. A single journey_step_has_actionJourney Stephas actionJourney Actionhierarchy edge attaches it to its parent step, and from there the chain runs upward through phase to the user_journey🛤️User JourneyExperience DesignAn end-to-end map of a user experienceView reference → anchor. Modelling actions as leaves keeps the granular layer where friction is actually measured, so a drop in completion can be traced to the exact move that caused it rather than blamed on the step that contains it.