Journey, Behaviour & Usage Analysis

Journey and usage analysis examines the routes customers actually take across channels, products and time. A designed journey shows how the service is meant to work, but it cannot reveal which paths people follow, repeat or abandon. Digital event data now makes these sequences measurable at scale. Marketways connects abandonment, delay and channel movement to customer outcomes and to the part of the service the client can change.

The decision this method supports

We use Journey, Behaviour & Usage Analysis to help clients answer: How do customers actually move, use or respond, and where does behaviour differ from the assumed journey?

How the method works

Journey and usage analysis studies sequences of customer actions across channels and time. The method can reveal abandonment, repeated effort, migration between channels and differences between intended and actual use. Behaviour describes what happened, while research may still be needed to explain why.

A business example

A mobile-service provider may find that customers begin an upgrade online but complete it in a shop after encountering one verification step. The sequence identifies the point of friction and the customers most affected.

How the client uses the result

Journey and usage analysis shows how customers actually move through channels, products and services. It helps leaders find abandonment, repeated effort and unexpected uses that a designed journey or overall conversion rate can hide.

What we deliver

We produce market estimates, customer groups, preference evidence, experience measures or behavioural patterns. A manager should be able to connect the result to an offer, channel, investment or operating decision.

Limits and complementary methods

Behavioural data shows what happened, not necessarily why. Research or experimentation may be needed before changing the journey.

Selected methods and techniques

We select from these established methods according to the decision, evidence and operating conditions.

  • Adoption-funnel analysis: Measure how many people or units progress through the stages of adopting a change, such as awareness, access, first use, repeated use and sustained use, and where they drop out. It specialises funnel analysis for change adoption. It locates where adoption breaks down, which a single adoption rate conceals.
  • Behavioural diagnosis: Specify the target behaviour precisely, who must do it, when and where, and analyse what currently drives or prevents it using a structured behavioural model. The diagnosis links each behaviour to its capability, opportunity and motivation requirements. It precedes intervention design so that interventions address the actual causes.
  • Behavioural pattern analysis: Examine repeated actions, sequences, timing and relationships to identify stable behaviour and meaningful departures from an appropriate peer or historical baseline. Control for context such as role, workload and policy changes before interpreting a difference. The method detects behavioural patterns; motives and wrongdoing require separate evidence.
  • Behavioural testing: Evaluate what an AI system or workflow actually does in specified situations rather than relying on documentation, prompts or stated intent. Define the situation, observable expected behaviour, scoring and severity and include normal, ambiguous and adverse cases. Behavioural tests show performance on those cases; they do not reveal internal reasoning or guarantee behaviour outside coverage.
  • Behavioural-event interviewing: Conduct structured interviews in which a person describes specific past situations in detail: what happened, what they did, why and with what result. Code the accounts against defined capability criteria. It gathers evidence of demonstrated behaviour rather than hypothetical answers or self-description.
  • Behavioural-response analysis: Examine how people's behaviour actually changed in response to goals, measures or incentives, using performance data, timing patterns, process records and interviews. It looks for intended responses and for side effects such as gaming, displacement or neglect of other work. Observed changes need checking against other explanations before being attributed to the incentive.
  • Behaviourally anchored scorecards: Turn service or performance standards into a scoring procedure whose levels are tied to specific observable behaviours. Define when each behaviour has an opportunity to occur, distinguish failure from not observed or not applicable, train assessors and check whether they apply the anchors consistently. Behaviourally Anchored Rating Scales provide the reusable scale format; this method builds and applies a scorecard for a particular setting. Clear anchors improve interpretation but do not by themselves establish validity or reliability.
  • Cohort analysis: Compare groups that share a defined starting event, period or characteristic and follow the same outcome over comparable relationship ages. State the cohort rule, time origin, eligible population, exposure and observation cutoff; align results by tenure when that is the question; show the number still observed and at risk at each time; and separate tenure effects from calendar events, changing acquisition mix and incomplete follow-up. Cohort analysis describes how group histories differ and can reveal when retention changes. It does not by itself identify the cause of the difference, predict an individual's departure or estimate the effect of a retention action.
  • Consequence analysis: Identify the beneficial and harmful outcomes that could follow an action or event, including who bears them, their magnitude, timing, duration and reversibility. Keep consequence separate from probability so a low-probability catastrophic loss is not hidden by an average likelihood score. This method describes what is at stake; risk exposure analysis additionally identifies the assets or activities placed in harm's way.
  • Funnel analysis: Measure progression and drop-off through defined stages, using eligible populations and consistent time windows.
  • Journey mapping: Map how a defined customer group pursues a stated goal from an explicit starting point to an ending point. Identify stages, touchpoints, channels, actions, needs, questions, emotions, frictions, hand-offs and outcomes, and label whether each element comes from observation, customer report, operational data, stakeholder assumption or is still unknown. Include important variation between segments and paths instead of forcing one average journey. Journey mapping is the procedure, the Customer Journey Map is the reusable representation and a Customer Journey Heatmap is one populated analytical output. It follows the customer's goal across the organisation; internal process mapping instead describes how work is performed.
  • Scenario consequence modelling: Estimate operational, financial or other consequences of a specified scenario by tracing its assumptions through explicit relationships and dependencies. Keep scenario inputs, transmission logic and outcome uncertainty visible. The result is conditional on the scenario and does not state its probability or prove that the modelled pathway is causal.

Parent method family

Market, Customer & Behavioural Analytics explains how this method connects to adjacent methods and relevant services.

Related service families

These service families contain business questions supported by this method. Service pages link to the wider method family so readers can understand the complete analytical approach.

Explore all Methods & Technologies

Marketways.ai – The Information Highway to your Market!