Learn the language for writing clear, evidence-based user personas: demographics, goals, pain points, and behaviours.
0 / 20 completed
1 / 20
A well-written persona is based on:
Effective personas are data-driven — synthesised from research patterns, not invented stereotypes. This makes them useful for decision-making rather than decoration.
2 / 20
Which section of a persona describes what users are trying to achieve?
The goals and motivations section captures what users are fundamentally trying to accomplish — the underlying needs that drive their behaviour.
3 / 20
In persona writing, 'pain points' refers to:
Pain points are the friction, obstacles, and unmet needs that make users' current experience difficult — the problems the product should solve.
4 / 20
Which phrase most effectively describes a persona's technology comfort level?
Specific, behavioural descriptions of technology comfort (tools used, behaviours avoided) are more actionable for design decisions than vague labels.
5 / 20
A 'quote' included in a persona card should:
Persona quotes grounded in real participant words create empathy and convey the persona's perspective authentically — fabricated quotes undermine this.
6 / 20
Code Review Comment: Sarah, regarding this `validate_user()` function, you've used a regex to match email addresses. While functional, it's overly complex and might not handle all valid email formats. Considering our 'Data Analyst' persona – who often deals with importing data from various sources – do we need such strict validation here, or should we opt for a simpler approach? validate_user()
This question tests understanding of persona needs within a code review scenario. The 'Data Analyst' persona's complexity tolerance is key. The incorrect options assume all regex are inherently good or that simplicity *always* wins; the correct answer highlights the specific persona's likely technical comfort level and the need for tailored validation.
7 / 20
PR Description: 'Fix: Added error handling for invalid user input. This prevents crashes when users enter non-numeric values in the age field. The updated code now uses a try-catch block to gracefully handle these errors and displays an informative message to the user.'
This tests relating a PR description back to specific persona needs. The UX Designer persona prioritizes a smooth and intuitive user experience, and preventing crashes aligns with that priority. The other options represent different technical roles but don't directly address the UX impact.
8 / 20
Standup Update: 'I'm working on integrating the new payment gateway. I've been focusing on the API integration and testing different transaction flows. It's proving more complex than initially anticipated – particularly around handling refunds.'
This tests applying a persona to a common standup update. The 'Senior Developer' is expected to handle technical complexities and proactively identify potential roadblocks – aligning with their role. The other options misinterpret the statement by assigning roles based on superficial aspects of the task.
9 / 20
Code Snippet (in a persona card): 'To ensure data consistency across all systems, we should always validate user input against predefined rules.'
This question focuses on the appropriate tone and context of a quote within a persona card. The 'System Administrator' persona is responsible for enforcing rules and standards – making this quote most relevant to their role and understanding. The other options misinterpret the purpose or target audience of the quote.
10 / 20
David from the QA team just sent this Slack message: 'Hey @john, can you take a look at the new user onboarding flow? Seems like people are getting stuck on step 3 – entering their address. It's taking ages!' Which UX persona characteristic does this situation *primarily* highlight?
This scenario focuses on a specific problem – the delay at step 3. It's most directly related to John's role as a developer debugging and troubleshooting, aligning with a persona that prioritizes technical efficiency and problem-solving. Options A & B are secondary concerns; option C represents a potential issue, but this Slack message doesn't explicitly detail it. Option D is too broad.
11 / 20
During a code review, Maria comments: 'This API endpoint, /users/{user_id}, consistently returns 200 OK status codes even when the user doesn't exist. We should add more robust error handling to reflect the expected behavior.' What does Maria *most* likely mean in this context regarding the persona?
Maria is emphasizing the importance of aligning the system's behavior with a 'happy path' – the ideal scenario where everything works as expected. This reflects a persona that values reliability and predictable outcomes. Options A & B are incorrect because the API *does* return an error; option C misinterprets the expectation, and D is a related task, but not the core point of her comment.
12 / 20
'The developer has used a complex regular expression to validate user email addresses. While functional, this approach could lead to performance issues and might not cover all valid email formats. Consider using a more lightweight library or simplifying the regex for improved efficiency.' – Mark, Senior Developer. Which of the following best describes Mark's feedback regarding the email validation in this code review comment?
Mark isn't advocating a complete overhaul but highlighting a potential problem. He's suggesting simplification for efficiency – a common concern in performance-critical code. The other options misinterpret his feedback; he doesn't believe the regex is 'incorrect' and doesn't want a rewrite.
13 / 20
'@alice, we're seeing a high drop-off rate on step 4 of the signup process – users are abandoning their accounts after entering their shipping address. Initial data suggests it's primarily mobile users. Can you investigate and provide insights?' – Ben, Product Manager. Which UX persona principle does Ben's message most directly relate to?
Ben's message focuses directly on 'pain points' – a key element of UX persona development. He's identifying a specific area where users are struggling (step 4, shipping address) and linking it to user behavior data (mobile users). The other options represent broader UX activities.
14 / 20
'Refactor: Improved error handling for failed API calls. Now includes more detailed logging and retry mechanisms to enhance reliability. This addresses a reported issue where users were intermittently losing data when the external service was unavailable.' – Emily, Backend Engineer. Which of the following best encapsulates Emily's primary goal in this PR description?
Emily's PR description focuses on 'reliability' – a core concern when dealing with external services. The improvements (logging, retries) are designed to mitigate failures and protect data integrity. While performance is a related benefit, the primary goal isn't simply to 'improve performance.'
15 / 20
'I'm currently troubleshooting an issue with the new recommendation engine. We've seen a significant drop in click-through rates since deploying the updated algorithm. I'm investigating potential biases in the data and exploring alternative weighting strategies.' – David, Data Scientist. Which aspect of persona development does David's update most clearly address?
David is investigating *why* users aren't clicking on recommendations – a direct reflection of user behavior. He's considering biases and weighting strategies, which are all ways of understanding and catering to user preferences. The other options represent technical or compliance concerns.
16 / 20
Sarah, regarding this code review comment: 'The user profile page consistently displays incorrect data for users with a 'premium' subscription. The data is pulled from the legacy database and doesn't integrate with the new CRM system.' Which of the following best describes how to address this persona's needs in your response? validate_user(user_id)
The correct answer focuses on acknowledging the core problem – a mismatch between data sources. The persona's primary need is accurate profile information, so the response should directly address this discrepancy and propose integration of systems. Options A and C misdiagnose or deflect from the actual issue; option D shifts focus to UI performance which isn't the root cause.
17 / 20
@bob, we've noticed a spike in support tickets related to users struggling to reset their passwords. The current flow involves clicking a 'Forgot Password' link, entering their email address, and receiving a password reset email – but many users are reporting that the emails aren't arriving. Considering this, which statement best reflects the persona's frustration? user_reset_password()
The key here is understanding the persona's frustration—a wasted effort dealing with a broken process. Option B accurately captures this feeling of inefficiency and the need for improvement. The other options reflect different, less relevant concerns (system failure, training needs, or UI clarity).
18 / 20
'Refactor: Improved error handling for user account creation. Now includes validation of required fields and attempts to prevent duplicate accounts. This addresses a reported issue where new users were intermittently failing to register due to missing data or conflicting usernames.' Which of the following best describes the persona's primary concern addressed by this change? create_user(username, email)
This PR focuses on preventing errors and ensuring successful registration. The persona's core need is a smooth and reliable account creation experience – avoiding frustration caused by data validation failures or duplicate accounts. Option A addresses performance; option C focuses on security which isn't the primary problem here; and option D concerns documentation, not the process itself.
19 / 20
'I'm working on implementing a new feature that allows users to schedule recurring payments. I've been focusing on designing the UI and integrating with the payment processor. It's proving more complex than initially anticipated – particularly around handling different currencies and tax calculations.' Which of the following best reflects the persona's likely technical comfort level? schedule_recurring_payment(user_id, amount, currency, frequency)
The persona acknowledges complexity but emphasizes the need for support and clear documentation. This indicates a realistic assessment of their skills – they're capable but recognize the limitations of unfamiliar systems. Option A suggests overconfidence; option C is too simplistic; and option D reflects a preference for easier tasks.
20 / 20
'The developer has implemented a new feature that allows users to upload images directly from their devices. While this provides convenience, the system is currently slow and unreliable, particularly when handling large image files.' Which statement best describes what this quote reveals about the persona's priorities? upload_image(user_id, file)
The quote explicitly prioritizes reliability and performance over aesthetics or feature additions. The persona's concern is directly related to the core functionality – a smooth and dependable image upload experience. Options A focuses on engagement; option C shifts the focus to UI design; and option D disregards performance considerations.
This exercise, "Writing UX Personas", tests your understanding of ux research vocabulary and phrasing through 20 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 20 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.