User journeys and flows
A user journey describes the end-to-end experience a person has while trying to accomplish a goal — across touchpoints, channels, and time. Page flows zoom in on the steps, decisions, and states within a product to show how stories are fulfilled screen by screen.
Why it matters
NN/g describes journey maps as tools for understanding and addressing customer needs and pain points. They help teams see beyond isolated screens to moments that cause friction or delight, and they reveal gaps that single-feature design misses.
Key ideas
- One map per persona or user type for clarity (1:1 mapping).
- Include doing, thinking, and feeling — not only clicks and screens.
- Cover states. Loading, empty, error, and success states are part of the real journey.
- Hypothesis vs research. Teams often start with a hypothesis map from existing knowledge, then validate with interviews or diary studies.
- Iterate maps. Journey artefacts should evolve as new research arrives.
- Mermaid or visual narratives help communicate flows to stakeholders who will not read long prose.
How it fits the pipeline
User journeys map end-to-end flows and often inform UI planning and content placement.
Common mistakes
- Mapping only the happy path
- Stopping at a hypothesis map without validation
- Introducing flows that no user story supports
- Omitting emotional context at painful steps
Further reading (NN/g)
- — journey maps vs other mapping types
- — from aspiration through research to narrative
- — common approaches and methods in practice
Educational summaries informed by research published by Nielsen Norman Group.