A customer journey is the sequence of interactions and experiences through which a user pursues a goal with a product or service. In software delivery, it describes the larger business outcome before the team decomposes that outcome into smaller rules, examples, and acceptance criteria. section 13.0 section 13.2.2
Use customer journeys to move from shared intent to verifiable behavior:
- Capture a concise scenario that expresses the overall business outcome, such as a traveler registering for a new membership. section 13.2.2
- Separate the journey from granular rules, such as confirming email, validating fields, approving terms, or rejecting duplicate accounts. section 13.2.2
- Choose the interaction boundary that fits the behavior: automate the complete journey through the UI, or exercise the relevant sequence through APIs when UI interaction adds no value. section 13.0 section 13.2.2
- Explore variations with concrete examples, tables, Example Mapping, Feature Mapping, or OOPSI before turning the understanding into executable specifications. section 6.7
Membership registration journey
A journey scenario might state: Tracy has no Frequent Flyer account; she registers with valid details and confirms her email; then she has a new Standard-tier account with zero points. Separate specifications can verify pending activation, login restrictions before confirmation, mandatory fields, valid email formats, terms acceptance, and duplicate-account handling. section 13.2.2
Rule: Travelers can register as new members on the Flying High website
Example: Tracy registers as a new Frequent Flyer
Given Tracy does not have a Frequent Flyer account
When she registers for a new Frequent Flyer account with valid details
And she confirms her email address
Then she should have a new Standard tier account with 0 points
Browse the concise Gherkin journey scenario for registering a new Frequent Flyer member. section 13.2.2
