Customer journey
A customer journey is a sequence of interactions and experiences through which a person pursues a goal while engaging with a product, service, or organization.
First-Party Data Activation
A coordinated sequence of interactions and decision steps that guides a prospect or customer toward a marketing objective over time.
- How it is used
- Guides prospects and customers through coordinated marketing interactions toward acquisition, onboarding, growth, retention, or winback objectives.
- How deep it goes
- Defines objectives and explains conditional channel and message sequences, but stops short of tool-level implementation.
- Examples
- Uses a baby registry and parenting support to illustrate retention, and a shoe retailer’s web, app, and connected-TV signals to illustrate measurement.
- What you can do after
- Evaluate/understand it by choosing suitable multistep objectives and conditional channels, then assessing conversion, engagement, or retention results.
Read how First-Party Data Activation explains customer journey →
Collaborative Software Design: How to facilitate domain modeling decisions
A customer journey is the sequence of experiences and interactions a customer has while pursuing an outcome with an organization.
- How it is used
- Frames customer experience for collaborative modeling, requirements discovery, UX work, and architecture discussions.
- How deep it goes
- Defines and distinguishes customer journeys from user journeys, then demonstrates integration with EventStorming without detailing a complete mapping procedure.
- Examples
- Uses BigScreen’s cinema-ticket experience, journey maps, touch points, pain points, and an EventStorming alignment scenario.
- What you can do after
- Apply it via EventStorming to validate journeys, identify pain points and architectural hotspots, and discover opportunities.
BDD in Action, Second Edition
A user journey is the sequence of interactions and experiences through which a user pursues a goal with a product or service.
- How it is used
- Frames high-level business outcomes before teams refine them into rules, examples, executable specifications, and acceptance tests.
- How deep it goes
- Distinguishes broad journey scenarios from granular rules and supports UI or API automation, while deferring detailed rule treatment to separate specifications.
- Examples
- Uses Frequent Flyer registration, email confirmation, account activation, mandatory fields, terms acceptance, valid emails, and duplicate-account prevention.
- What you can do after
- Evaluate/understand whether a feature delivers its intended business outcome and select UI or API acceptance coverage accordingly.
Read how BDD in Action, Second Edition explains customer journey →
Design for Developers
A user journey map is a visual narrative of a user's actions, thoughts, feelings, and opportunities for improvement across connected product touchpoints.
- How it is used
- Uses one persona’s experience to reveal emotional highs, lows, and improvement opportunities across a product journey.
- How deep it goes
- Defines persona, scope, steps, thoughts, feelings, and opportunities, while stopping short of implementation detail.
- Examples
- Uses a train-ticket booking app and a healthcare experience spanning a website and provider visit.
- What you can do after
- Apply it to map a focused persona scenario and identify experience improvements from observed emotional moments.
Automating API Delivery
A user journey is the sequence of stages and actions an actor performs while interacting with a product or service to achieve a goal.
- How it is used
- Uses actor actions and goals to review API usability, shape service design, and measure the developer experience.
- How deep it goes
- Defines personas, goals, stages, actions, and touchpoints, then stops short of prescribing a universal stage model.
- Examples
- Uses user journey maps, developer journey maps, guide documentation, service blueprints, touchpoints, and API product metrics.
- What you can do after
- Evaluate API experience, identify friction across user stages, and select metrics that show product value and performance.
Read how Automating API Delivery explains customer journey →
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A user journey is the sequence of interactions and experiences a user has while pursuing a goal with a product or service.
- How it is used
- Guides domain-boundary analysis, modernization planning, and collaborative mapping of business workflows.
- How deep it goes
- Distinguishes three journey-to-subdomain relationships and explains when complexity or reuse makes full alignment unsuitable.
- Examples
- Uses onboarding, pandemic-era travel refunds, and modernization workshops as concrete journey-analysis examples.
- What you can do after
- Evaluate whether a journey should align with, delegate to, or compose multiple subdomains.
Related concepts
- touchpointhas part · A touchpoint is a point or instance of interaction between a person and a product, service, organization, brand, or system.
- software design EventStormingused by · Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
- business taskhas part · A business task is a cohesive user-oriented activity that contributes to a business goal and can be composed into a user journey.
- personaused by · A persona is a defined identity or representative profile characterized by traits, goals, perspectives, or behavior that guides an agent’s or user group’s representation.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.