Journey view is the best place to understand the customer experience in order. It shows the flow stage by stage and step by step, which makes it the right view for story, sequence, and shared understanding.Documentation Index
Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt
Use this file to discover all available pages before exploring further.
What journey view is best for
Use journey view when you need to:- Review the end-to-end customer path
- Explain the experience to teammates
- See where friction appears in sequence
- Understand how problems in one stage affect later stages
- Run journey reviews, workshops, or planning sessions
How to use it well
Start with the customer path, not the internal team structure.- Review stages from left to right
- Open the steps where friction or confusion happens
- Inspect the attached items, comments, links, and metrics
- Look for repeated problems across multiple steps
- Capture new insights or opportunities directly in the map
What makes it valuable
Journey view keeps context in sequence. That matters because a problem often makes more sense when your team can see:- What happened before it
- What the customer was trying to do
- What evidence supports the issue
- What downstream impact it creates
When to leave journey view
Switch to another view when the question changes.- Move to Table view when you need cleanup, filtering, or metadata review
- Move to Impact vs effort view when the team is deciding what to prioritize first
Practical review habit
A strong weekly journey review usually starts here. Use journey view to ask:- Where are customers getting stuck?
- What changed since the last review?
- Which opportunities now have enough evidence to act on?
- Which steps feel stale or under-documented?