5 exercises — Practice writing welcome screens, empty states, permission coaching copy, and milestone confirmations that guide users to their first value moment.
0 / 10 completed
1 / 10
A project management SaaS shows this welcome screen to first-time users: "Welcome to Taskr! We're so excited to have you. Taskr is a powerful project management tool that helps you manage tasks, collaborate with your team, assign work, set deadlines, track progress, and more." What is the main UX writing problem?
Onboarding copy should lead with the user's outcome, not the product's feature list.
The current message structure:
❌ "Taskr is a powerful tool that helps you [feature list]"
Better structure:
✓ "[Your outcome]. Let's set you up in [X minutes]."
Example: "See exactly who's working on what — and ship projects on time. Let's create your first workspace."
Users at the welcome screen already know it's a PM tool — they just signed up. What they need is:
1. Confirmation they made a good choice (outcome reassurance)
2. A clear single next step (activation CTA)
3. A sense of how long it will take
Key vocabulary:
• Onboarding copy — UI text that guides users from signup to their first value moment
• Outcome framing — leading with what the user achieves rather than product capabilities
• Feature-led copy — the anti-pattern of listing features instead of user outcomes
• Activation CTA — the call to action that moves users to their first key action
2 / 10
An analytics tool shows this empty state during onboarding: "No data yet." What should replace it?
Onboarding empty states must explain why it's empty AND provide a direct path to fill it.
The "no data yet" anti-pattern leaves users stranded — they don't know:
• Why it's empty
• What action they should take
• How long it will take
Good onboarding empty state formula:
1. Explain the cause clearly ("when you add your tracking code")
2. Provide one direct CTA that fills the gap
3. Reduce anxiety with time estimate ("5 minutes")
Option A — passive ("will appear once") — no clear action
Option B — developer-speak ("SDK installed correctly") — sounds like debugging, not onboarding
Option C ✓ — explains cause, links to action, time-boxes the effort
Option D — ("Waiting for data...") — implies passive waiting when there's actually an action required
Key vocabulary:
• Onboarding empty state — the first-time view of a dashboard or section before setup
• Cause explanation — copy that explains why the state is empty, not just that it is
• Time-boxing — communicating how long a setup step takes to reduce hesitation
• Activation step — the key action a user must complete to see their first value
3 / 10
A SaaS onboarding flow asks the user to invite teammates after creating their account. The button reads: "Invite Users". What is a better CTA label?
Onboarding CTAs should be action-oriented and emotionally engaging — not generic system language.
Comparison:
• "Invite Users" — product-system language; "users" is an admin term, not how people think of their colleagues
• "Continue" — no information; could be anything
• "Add Team Members" — better, but still formal and transactional
• "Bring Your Team In" ✓ — human, collaborative, mirrors how people think about the action
For the "skip" path, "Skip for now" or "I'll do this later" is appropriate — "Skip For Now" in Option C would be a valid secondary action below the primary CTA, not the primary action itself.
Onboarding CTA language principles:
• Use human language over system language
• Mirror the user's mental model ("bring in" not "add")
• Create forward momentum ("Let's", "Bring", "Start")
Key vocabulary:
• CTA (call to action) — the button or link that drives the primary next step
• System language — vocabulary from the software's internal model (users, records, entities)
• Human language — vocabulary matching how people talk naturally about the action
• Momentum copy — onboarding language that creates a sense of forward progress
4 / 10
A team chat app shows a permission prompt: "Allow Chatflow to send you notifications?" with Allow and Deny buttons. Before this prompt appears, a coaching screen appears. Which coaching message is most effective?
Permission coaching screens must give a specific benefit and address the fear of over-notification.
The OS permission prompt is high-stakes — once denied, it's hard to reverse. The coaching screen's job:
1. Make the value clear and specific ("don't miss important messages")
2. Pre-empt the main concern ("we'll only ping you for direct messages and urgent threads")
3. Build trust before asking
Options A and B — generic value propositions; "function correctly" is threat-based; "stay informed" is vague
Option D — just instruction; no benefit or reassurance
Option C ✓ — specific benefit + fear resolution + implicit commitment
Key vocabulary:
• Permission coaching screen — an in-app screen shown before a native OS permission prompt
• Permission priming — preparing users to accept a permission request with context and benefit
• Notification fatigue concern — users' fear of being spammed; must be directly addressed
• Benefit specificity — naming the exact use case rather than a generic benefit
5 / 10
After an e-commerce merchant completes their first product upload, the platform shows a success screen. Which message best drives continued activation?
Success states in onboarding should celebrate the milestone and immediately direct to the next activation step.
The "product saved" confirmation is a system message — it's not an onboarding moment. At this stage, the user needs:
1. Acknowledgment of the milestone
2. A clear picture of what's left before they get value
3. A direct next step
Option C does all three:
• "Your first product is live" — milestone acknowledged with outcome language
• "2 more steps to your first sale" — quantified remaining work
• Lists exactly what's next (concrete, not vague "set up your store")
Progress-to-value framing ("X steps to your first sale") is one of the most effective activation copy patterns in SaaS onboarding.
Key vocabulary:
• Milestone confirmation — copy that acknowledges the user completed a meaningful step
• Progress-to-value framing — quantifying remaining steps to the user's first valuable outcome
• Activation funnel — the sequence of steps from signup to the user's first value moment
• Next step nudge — a CTA or link that moves the user immediately to the next activation step
6 / 10
Alex, a junior developer, just submitted a PR with the following code review comment: 'This function doesn't handle edge cases.' What's the most effective way to respond as a senior engineer, focusing on clear communication for a non-native English speaker?
The key here isn't simply stating 'good catch,' but prompting Alex for specifics. Asking for elaboration encourages him to articulate his concerns clearly and facilitates a productive discussion. The tag highlights that the question is about the *content* of the comment, not just its presence. Option A is too dismissive; B actively seeks clarification.
7 / 10
Sarah, a product manager, sends this Slack message during onboarding: 'Hey team, let's get everyone up to speed on the new CRM!'. What's the best way to refine this for a more helpful and engaging user experience?
Sarah's message is vague and doesn't address the user's needs. Providing context – like benefits or resources – dramatically improves engagement. The tag emphasizes that the question relates to *adding value* to the initial communication, not just generating enthusiasm. Option A highlights a key issue—lack of benefit; option D is completely unhelpful.
8 / 10
David is writing the description for a PR that adds a new API endpoint. The current draft reads: 'This changes the database schema.' What's the best way to improve this, considering the perspective of a developer unfamiliar with the specific codebase?
The original description is too abstract and lacks crucial context. Providing details about *what* the endpoint does (retrieving user profiles) and its relation to a specific release (v2.0) helps David understand the impact of the change. The tag represents that this question is focused on providing information about the API, not just stating technical facts.
9 / 10
A SaaS application displays a loading state with the text: 'Loading…'. Before this screen appears, the user has just signed up for a new account. What's the most effective way to adjust this message to improve the onboarding experience?
'Loading…' is passive and unhelpful. Adding a reassuring statement – like 'Please wait while we set up your account' – provides context and manages user expectations. This reduces anxiety and improves the overall onboarding experience. The tag indicates the focus here is on calming the user, not just stating that something is happening.
10 / 10
Maria, a UX writer, is crafting copy for a help center article explaining how to reset a password. What's the most user-friendly approach?
Users often find technical instructions confusing. Maria should prioritize clear, step-by-step guidance that's easy to follow. The tag represents the fact this question is about clarity and simplicity in user guidance.
This exercise, "Onboarding Copy", tests your understanding of ux writing 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 Writing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing ux writing 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 Writing exercises?
Browse the full UX Writing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.