Practise reading and writing user journey maps: stage/action/touchpoint vocabulary, emotional arc language, and how to phrase friction points and insights with evidence.
0 / 11 completed
1 / 11
Which section of a journey map records what the user is doing at each stage?
The action row of a journey map records the concrete steps the user takes at each stage (e.g. 'searches for the product', 'compares prices'). Other rows capture related but distinct information: emotion (how they feel), touchpoint (where the interaction happens), and opportunity (what the team could improve).
2 / 11
Which sentence correctly narrates a journey map stage using standard journey-map phrasing?
Journey stage narration follows the pattern 'In the [stage] stage, the user [does/discovers/experiences] [specific action]'. This is precise and describes a concrete, evidence-based behaviour rather than a vague guess ('probably') or a description of the map's layout rather than the user's experience.
3 / 11
A 'touchpoint' in journey mapping refers to:
A touchpoint is any interaction between the user and the organisation across channels — a website page, a confirmation email, a customer support call, an app notification. Journey maps track touchpoints stage by stage to reveal where the experience is fragmented across channels.
4 / 11
Which sentence correctly reports a friction point using data?
A well-reported friction point names the exact stage and quantifies the impact: 'the payment step, where 31% of users abandon the flow'. Vague statements ('don't like', 'confusing for everyone', 'struggle at some point') give stakeholders nothing concrete to act on.
5 / 11
Which words best describe an emotional arc moving from a negative to a positive state across a journey?
An emotional arc should show change over the journey, not a flat or purely negative line. 'Confusion → clarification → confidence' tells a story: the user starts unsure, receives help or better design, and ends confident — useful for identifying which stage caused the turnaround and could be reused elsewhere.
6 / 11
Which is the best-written journey map insight?
A strong journey map insight names the stage, the emotion, and the underlying reason: 'Users feel overwhelmed at the account setup stage because they are asked for eight pieces of information before seeing any value.' This format — feeling + stage + cause — gives designers a clear problem to solve, unlike a bare judgement ('is bad') or an unexplained drop-off statistic.
7 / 11
A user reports that the checkout process is taking too long. Which of the following best describes a key element to investigate regarding their 'user journey'?
This scenario focuses on identifying a bottleneck within the user journey. The number of steps is a measurable metric directly impacting the user's experience and therefore critical to understanding their journey. The other options (responsiveness, lack of analytics, or missing feedback) are factors that could contribute but aren't core to defining a 'user journey' itself.
8 / 11
Which statement accurately describes the purpose of creating a user journey map for a new mobile app?
A user journey map's primary function is to visualize *how* a user interacts with your product—their actions, thoughts, and feelings at each step. It's about understanding the complete experience, not just listing features or predicting market trends.
9 / 11
In a Slack message discussing user feedback on a new feature, what does 'drop-off' most likely refer to?
'Drop-off' is a common term in journey mapping that describes a point where users abandon a specific stage or flow. It indicates an inefficiency or frustration within the user's experience that needs to be addressed; it's not about reactions or sentiment.
10 / 11
A code reviewer comments: 'The API response doesn't include a success status code when the request fails.' What journey mapping concept is this addressing?
This comment highlights a problem in the user's *interaction* with the system—specifically, the API. A friction point represents any obstacle or difficulty a user encounters during their journey. The lack of a clear success code indicates an unclear and potentially frustrating experience for the developer using the API.
11 / 11
During a standup meeting, a developer says, 'I'm stuck on integrating with the third-party payment gateway. The documentation is unclear, and I haven't been able to get any support.' What aspect of the user journey is this primarily describing?
This statement describes the *process* a user (in this case, the developer) is going through to achieve a goal – integrating with the payment gateway. It's about the steps taken, the challenges faced, and the support sought, reflecting the entire journey from initiation to attempted resolution.
This exercise, "User Journey Description", tests your understanding of ux research vocabulary and phrasing through 11 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 11 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this UX Research exercise for?
It's designed for IT professionals and learners who want to sound natural discussing ux research topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more UX Research exercises?
Browse the full UX Research exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.