Practice UX documentation vocabulary: UX specs, interaction specs, personas, journey maps, service blueprints, and experience maps.
0 / 10 completed
1 / 10
What is a 'persona' in UX documentation?
Personas synthesise research findings into a memorable, concrete character. A well-made persona includes: name and photo, demographics (relevant, not decorative), primary goals, frustrations/pain points, technical proficiency, and a quote that captures their mindset. Caution: proto-personas are assumption-based; research-backed personas are grounded in real data. Personas should drive decisions, not gather dust.
2 / 10
What does a 'customer journey map' document?
A journey map is a visualisation tool. Typical rows: phases (Awareness → Consideration → Purchase → Use → Support), actions (what the user does), touchpoints (website, email, app, store), thoughts (what they're thinking), emotions (plotted as a curve — peaks and valleys), pain points, and opportunities. It creates empathy and surfaces where the experience breaks down.
3 / 10
How does a 'service blueprint' differ from a customer journey map?
Service blueprints (Lynn Shostack) add layers below the line of visibility: frontstage actions (what the customer experiences), backstage actions (what staff do that the customer doesn't see), support processes (systems and tools), and physical evidence (receipts, emails, packaging). Essential for service design — revealing operational bottlenecks, handoff failures, and systemic improvement opportunities.
4 / 10
In a design handoff, what is an 'interaction spec' (also called an interaction specification)?
An interaction spec bridges the gap between a static Figma mockup and a fully working feature. It should cover: all component states (default, hover, focus, active, disabled, loading, error, empty), transition behaviour (what triggers state changes), animation details (easing, duration), responsive behaviour, and edge cases ('what if the name is 200 characters?'). Without it, developers make assumptions that often don't match design intent.
5 / 10
What is a 'research repository' in UX practice?
Research repositories (tools: Dovetail, Notion, Airtable, EnjoyHQ) prevent research from being done repeatedly or lost. A good repository tags findings by theme, product area, user segment, and date — enabling new teams to search for existing evidence before commissioning new research. Key challenge: maintaining quality and findability as the repository grows. Related concept: research ops (ResearchOps) — the infrastructure supporting research practice.
6 / 10
Sarah from the design team is reviewing your PR for a new user onboarding flow. She comments: 'This screen needs clearer labeling – we should use the term 'confirmation' instead of 'submit'. What does Sarah likely mean when she suggests using the term 'confirmation'?
Sarah is focusing on the *user experience* aspect of the screen. 'Confirmation' implies that the user has completed a step and received feedback – a crucial element in good UX design. Using 'confirmation' instead of 'submit' provides a more reassuring signal to the user, reducing anxiety about whether their action was registered.
7 / 10
You're drafting a PR description for a new API endpoint designed to retrieve user profile information. You want to clearly communicate the expected response format. Which of the following is the MOST appropriate way to describe the response data using UX documentation terminology?
While all options touch on aspects of the response, 'a structured dataset with fields…' is the clearest and most precise. It leverages UX vocabulary by emphasizing that the data has a defined *structure*, which is critical for developers consuming the API. The other options are either too vague or use terminology less common in formal API documentation.
8 / 10
During a standup meeting, your team lead asks: 'Can you explain how the 'low fidelity' wireframes contribute to our UX documentation strategy?' What is the PRIMARY purpose of low-fidelity wireframes in this context?
Low-fidelity wireframes are about rapid prototyping and exploration. They represent the *core* functionality and structure without focusing on visual aesthetics or detailed interaction specifications – allowing designers to quickly test ideas and gather feedback early in the process. This directly supports documentation by establishing a foundation for more refined designs.
9 / 10
You are documenting a complex user flow for an e-commerce website. You create a 'customer journey map' to visualize the steps a customer takes when purchasing a product. Which of the following is a key element typically included in a customer journey map?
Customer journey maps are fundamentally about understanding *user experience* from a user's perspective. They focus on identifying emotional states (frustration, delight) and pain points at each step of their interaction with the product. The other options represent technical or marketing data, not core UX documentation components.
10 / 10
Your team is preparing a design handoff for a new mobile app feature. You've created an 'interaction spec' which details how the user interacts with a specific component. What is the main purpose of this document?
An 'interaction spec' bridges the gap between design and development by focusing on *how* a user interacts with an element. It's a detailed description of the intended behavior – what happens when the user taps, swipes, or performs other actions. This shared understanding reduces ambiguity and facilitates collaboration.
This exercise, "UX Documentation Vocabulary", tests your understanding of ux research vocabulary and phrasing through 10 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 10 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.