Practice UX research methods vocabulary: qualitative vs quantitative, moderated vs unmoderated, A/B testing, tree testing, card sorting, and first-click testing.
0 / 10 completed
1 / 10
What is the key difference between qualitative and quantitative UX research?
Qualitative methods (interviews, ethnographic observation, diary studies) generate insights about user motivations, mental models, and pain points. Quantitative methods (surveys, analytics, A/B tests) generate measurable data about behaviour and frequency. Mixed-methods studies combine both — e.g., quantitative analytics identifies the problem ('30% drop-off on step 3'), qualitative interviews explain why ('users don't understand what 'verify' means').
2 / 10
In usability testing, what distinguishes 'moderated' from 'unmoderated' sessions?
Moderated testing allows for deep probing ('what were you expecting to happen there?') but is expensive and introduces facilitator bias. Unmoderated testing (tools: Maze, UserTesting, Lookback) scales well — you can run 50 sessions overnight — but you can't ask follow-up questions. Choose moderated for exploratory research and complex flows; unmoderated for validation and benchmark testing.
3 / 10
A product team runs a tree test. What are they evaluating?
Tree testing (reverse card sort) evaluates navigation structure. Participants are given a task ('Where would you find your billing history?') and navigate a tree of categories — no visual design. Metrics: success rate, directness (did they go straight there?), time. Tool: Optimal Workshop Treejack. Use tree testing before designing a new navigation or after card sorting to validate an IA.
4 / 10
What is 'card sorting' as a UX research method?
Card sorting comes in two forms: Open card sort — participants create and name their own groups, revealing mental models. Closed card sort — participants sort cards into predefined categories, testing whether an existing IA is intuitive. Results inform navigation labels, menu structure, and taxonomy. Common tools: Optimal Workshop OptimalSort, Maze, Miro.
5 / 10
From a UX research perspective, how does A/B testing differ from usability testing?
A/B testing is quantitative and comparative — it tells you that version B had 12% higher conversion, but not why. Usability testing is typically qualitative and diagnostic — it tells you users are confused by the label 'Proceed', but doesn't tell you whether changing it will improve conversion by 5% or 20%. Both are valuable: usability testing generates hypotheses; A/B testing validates them at scale.
6 / 10
Sarah (Product Manager): 'We need to understand why users are abandoning the checkout process. I'm thinking of using a heuristic evaluation – could you explain what that involves and what kind of insights we might gain?'
Heuristic evaluations are expert reviews based on established UX principles. They provide quick initial feedback and identify obvious usability problems. While they don't offer statistical rigor, they're valuable for early-stage validation before more complex research methods like user testing.
7 / 10
Mark (Senior Developer): 'I'm reviewing this PR. The designer mentions conducting a 'diary study'. What is the primary goal of this research method?'
Diary studies are qualitative research methods that rely on participants' self-reported experiences. The aim is to understand *how* users interact with a product over time, capturing context and motivations that might be missed in shorter tasks. This contrasts with quantitative methods like A/B testing which focus on measurable outcomes.
8 / 10
David (UX Researcher): 'We're planning a session to explore user workflows for our new mobile app. We want to see how users naturally approach different tasks.'
Card sorting is a technique used to understand how users categorize information. It's particularly useful for designing navigation systems and content structures. Unlike tree tests which focus on finding specific elements within a defined hierarchy, card sorting explores the *user's* mental model of the product.
9 / 10
Emily (UI Designer): 'I've created some prototypes for a new feature. I want to test different layouts with users before development.'
A/B testing involves presenting two or more variations of a design element (in this case, layouts) to different groups of users and measuring their behavior. This allows for data-driven decisions about which layout performs better based on metrics like click-through rates or task completion times. It's distinct from usability testing where the focus is on *understanding* user experience.
10 / 10
Ben (Lead Developer): 'During our standup, Maria mentioned we should conduct some 'contextual inquiry' to understand how users are currently solving the problem our product is meant to address.' What does this method primarily involve?
Contextual inquiry is a qualitative research method where you observe and interview users *in their natural environment* while they are performing tasks. This provides rich context around how people actually work, helping identify unmet needs and potential opportunities for improvement – it's about understanding the 'why' behind user actions.
This exercise, "UX Research Methods 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.