Journey Stage

Origin & evolution

The staged view of buying behaviour is old. In 1898 the advertising pioneer Elias St. Elmo Lewis sketched what later became the AIDA model): attention, interest, desire, action. It was a linear funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference →, drawn from selling life insurance, and for most of a century it framed how marketers pictured a prospect's progress.

Two later movements reshaped it. Service design and the experience economy moved the focus from the seller's funnel to the customer's lived experience. B. Joseph Pine II and James H. Gilmore's The Experience Economy (1999) argued that businesses stage experiences, which pushed practitioners to map the whole arc a customer travels, including the parts that happen after purchase. Customer journey mapping grew out of this lineage as a way to chart stages, the emotions inside them, and the moments that make or break each one.

Then McKinsey broke the straight line. Its 2009 Consumer Decision Journey, based on the purchase decisions⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → of nearly 20,000 consumers, replaced the funnel with a loop, observing that real buyers move iteratively through consideration and evaluation and, once loyal, can skip straight back to repurchase. The field has since landed on a pragmatic position: stages remain a useful organising abstraction, provided the team accepts that customers move through them non-linearly, doubling back and skipping as they go.

How it works in practice

A B2B analytics product maps its post-signup journey into stages: activation, habit formation, expansion, advocacy. The activation stage is defined by a single mindset, "can I get one real answer out of this." Inside that stage sit the concrete units. The journey steps🪜Journey StepExperience DesignA single step in a user journeyView reference → are the actions a user takes (connect a data source🛢️Data SourceData & AnalyticsA data source or integrationView reference →, build a first chart). The touchpoints👆TouchpointCustomer SuccessA customer interaction touchpointView reference → are the surfaces where the product meets them (the onboarding email, the empty-state hint, the support chat).

When the team finds that 40% of signups never reach habit formation, the stage boundary tells them where to look. They instrument the funnel steps🔽Funnel StepGrowthA stage within a conversion funnelView reference → inside activation and discover the drop sits at "connect a data source," a single step. Fixing that one touchpoint, a clearer connector picker, lifts stage-two arrival from 60% to 78%. The stage framed the problem; the smaller units located it.

Customer journey stage vs. its neighbours

• Journey step is a single action the customer performs. A stage spans many steps and is named for a mindset, not an action. "Consideration" is a stage; "compare two pricing pages" is a step inside it.
• Touchpoint is a point of contact between customer and product or brand: an email, a screen, a call. A stage contains touchpoints; the touchpoint is the surface, the stage is the chapter of the relationship it belongs to.
• Funnel step is a measured conversion gate, defined by the metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → it counts (signup to activation). A stage is an experiential phase. They often align, yet a funnel step exists to be quantified, while a stage exists to be designed for.

In the graph

In the Unified Product Graph, a customer journey stage sits in the customer success domain as the organising layer of the experience. It spans its constituent actions through customer_journey_stage_spans_journey_stepCustomer Journey StagespansJourney Stepcross-domain, holds the surfaces of contact through customer_journey_stage_contains_touchpointCustomer Journey StagecontainsTouchpointhierarchy, and holds its measurable gates through customer_journey_stage_contains_funnel_stepCustomer Journey StagecontainsFunnelcross-domain. A broader flow assembles stages in sequence via user_flow_contains_customer_journey_stageUser FlowcontainsCustomer Journey Stagehierarchy, and operational play attaches through playbook_targets_customer_journey_stagePlaybooktargetsCustomer Journey Stagecross-domain. The structure keeps the abstraction layers distinct: mindset (stage), action (step), surface (touchpoint), and metric (funnel step) each have their own home, so a team can move between the chapter and the line without collapsing one into the other.