Guidelines for defining user journeys
-
Name user journeys after business capabilities, not technical components.
-
A user journey should represent something an end user does (for example, "Check balance," not "Database reads").
-
Start with your most critical user journeys and add more over time.
-
A service can belong to multiple user journeys – shared platform services often do.
The following table shows examples of systems and their corresponding user journeys:
| System | User journeys |
|---|---|
| E-commerce platform | Path to purchase, Product discovery, Order fulfillment, Returns |
| Trading system | Execute trade, Check portfolio, Transfer funds |
| Failover orchestration | Manage plans, Execute failover, Run reports |
