5 exercises — Master the vocabulary for UX writing critiques: prescriptive tone, heavy lifting, voice and tone, personality vs. utility, and passive voice in UI copy.
0 / 12 completed
1 / 12
During a UX writing critique, a reviewer says: "This tooltip feels too prescriptive." What does "prescriptive" mean in this context?
"Prescriptive" in UX writing means the copy dictates users' attitudes or decisions rather than informing them.
Prescriptive example: "You should always enable two-factor authentication for better security."
Non-prescriptive: "Adds a second verification step when you sign in."
Why avoid prescriptive copy:
• It implies users are making poor choices
• It creates a condescending tone
• It can feel like the product is lecturing
Related critique terms:
• Preachy — repeating a recommendation too insistently
• Paternalistic — assuming users can't make informed decisions
• Directive — (positive in CTAs) using action verbs; (negative elsewhere) telling users what to do
Key vocabulary:
• Prescriptive tone — copy that tells users what they should do or think
• Descriptive tone — copy that informs without instructing beyond the necessary
• Condescending copy — text that implies the user lacks judgment
• Neutral framing — presenting information without implicit judgment about user choices
2 / 12
A reviewer says: "The empty state copy is doing too much heavy lifting." What does "heavy lifting" mean here?
"Doing too much heavy lifting" means copy is compensating for product design problems rather than complementing good UX.
Signs that copy is doing too much heavy lifting:
• Empty state has 3+ paragraphs explaining a complex workflow
• Tooltip is doing the job of onboarding documentation
• Error message is explaining a core product concept
• A button label needs a long subtitle to clarify what it does
The principle: if the copy needs to be 200 words to explain a 2-word label, the label (or the feature's design) needs rethinking.
In UX writing critique language:
• "This copy is patching a design problem" = the same as "heavy lifting"
• "The copy is masking a UX debt" = technical UX design debt being covered up with words
Key vocabulary:
• Heavy lifting — copy working harder than it should because design hasn't solved the problem
• Copy patch — using words to cover an unresolved UX problem
• UX debt — unresolved usability problems accumulated over time
• Information architecture — the structural design of information; copy's job is to label, not to replace it
3 / 12
In a content review, a senior writer says: "This microcopy breaks voice and tone guidelines — it's too formal for our brand." What does "voice and tone" refer to?
Voice is stable (brand personality); tone is situational (adapts to the user's emotional state).
Example:
• Brand voice: friendly, clear, direct, occasionally witty
• Tone in an error message: calm and helpful (not witty — this isn't funny for the user)
• Tone in a success message: warm and celebratory
• Tone in a data loss warning: formal and serious
The Mailchimp voice & tone guide is the canonical reference for this concept in the industry.
When a reviewer says "too formal for our brand" they mean:
• The copy uses bureaucratic/corporate language (e.g., "Please be advised")
• The vocabulary is more complex than the brand's established reading level
• The sentences are longer and more complex than the brand norm
Key vocabulary:
• Brand voice — the consistent personality and style of a brand's written language
• Tone — how voice adapts to suit the user's emotional context
• Voice & tone guide — a documentation artifact that defines brand voice with examples
• Formal register — language that is professional and impersonal (often too formal for consumer products)
4 / 12
A UX writer presents an error message that says: "Oops! It looks like something went a little bit wrong on our end. Don't worry — we're on it!" A reviewer responds: "This copy prioritizes personality over utility." What does this mean?
"Prioritizing personality over utility" means copy is entertaining at the expense of being useful.
Analysis of the error message:
• "Oops!" — exclamation of surprise; inappropriate when users' work is at risk
• "a little bit wrong" — minimizing language; dismisses the severity
• "Don't worry" — patronizing; users are already worried
• "we're on it!" — implies recovery is happening; may not be true
What's missing:
• What went wrong
• What the user should do (retry? wait?)
• Any timeframe or expectation setting
Better: "We couldn't save your changes. Please try again."
Personality is appropriate when the situation is light (success states, celebrations). Error messages require utility first.
Key vocabulary:
• Personality over utility — copy that prioritizes brand personality at the cost of usability
• Minimizing language — copy that downplays the severity of an error (e.g., "a little bit")
• Utility-first copy — prioritizing the functional job of the text before brand expression
• Situational appropriateness — matching the emotional weight of copy to the context
5 / 12
After a microcopy review, a lead writer says: "Good catch on the passive voice issue — we need more scannable copy here." Which edit best fixes both passive voice and scannability?
Fixing passive voice AND scannability means using active constructions + ruthless brevity.
Analysis:
• Original: passive ("will be deleted by the system") + wordy (10 words)
• Option A: removes "by the system" but still passive ("are deleted"); slightly better but still verb-only construction
• Option B: longer; active ("will automatically delete") but adds unnecessary words; the opposite of scannable
• Option C ✓: Active structure, verb-noun compound ("auto-delete"), 5 words vs 10
• Option D: "Note:" is a filler word; keeps passive construction
Compound verb-nouns like "auto-delete", "auto-save", "auto-renew" are excellent for UI copy — they're dense, scannable, and precise.
Key vocabulary:
• Passive voice — construction where the subject receives the action ("files are deleted by the system")
• Active voice — construction where the subject performs the action ("the system deletes files")
• Scannability — the ease with which users can extract key information from a glance
• Verb-noun compound — a single-word construction combining action and object (auto-delete, auto-save)
6 / 12
During a code review, Alice comments: 'The button text is ambiguous – it doesn't clearly state what happens when I click it.' What does 'ambiguous' mean in this context regarding UX writing?
'Ambiguous' means unclear or open to multiple interpretations. In UX writing, this refers to copy that doesn't clearly communicate the action a user will take when they interact with an element like a button. The goal is always clarity and reducing user uncertainty – Alice is pointing out the text fails to meet this standard.
7 / 12
A UX writer creates an error message that reads: 'Error 404: Page Not Found. Please contact support.' A reviewer says: 'This copy prioritizes technical details over user empathy.' What does this mean?
This statement highlights the importance of empathy in UX writing. While technically accurate, 'Error 404: Page Not Found' is cold and unhelpful to a user who's just encountered an error. Effective copy should acknowledge the user's frustration and offer guidance or support – prioritizing the user's feelings is key.
8 / 12
David from Product Management says: 'The microcopy on this onboarding flow feels like it's explaining *why* we need users to create an account, instead of just prompting them.' What is David referring to with the term 'explaining'?
David is concerned about providing excessive justification. In microcopy, 'explaining' implies adding unnecessary detail or argument—the copy should simply state the *need* for an account without over-selling it. The goal is clarity and a direct prompt, not a lengthy explanation.
9 / 12
Sarah (a UX writer) sends a Slack message to the team: 'This error message feels overly apologetic. It's softening the impact of a serious system failure.' What does Sarah mean by 'softening the impact'?
Sarah's critique highlights the importance of delivering bad news effectively. 'Softening the impact' means mitigating the negative emotional response caused by an error—avoiding language that downplays the seriousness of the situation and focuses on clear, direct communication about what happened.
10 / 12
Mark (a developer) comments on a PR: 'The copy for this modal window is too verbose. It's taking up valuable screen real estate.' What does 'verbose' mean in the context of UX writing?
'Verbose' describes content that is excessively wordy—it's not about the complexity of language but the amount of text. In UX writing, brevity is key; users scan quickly and need concise messages to understand their options.
11 / 12
Emily, a senior UX writer, reviews a proposed landing page headline and states: 'This headline lacks a clear call to action. It's simply describing the product – it doesn't tell users what to do next.' What is Emily primarily criticizing about this headline?
Emily's feedback centers around the core function of a headline – to drive action. A strong call-to-action (CTA) is essential for guiding users towards conversion. The headline should clearly tell them what you want them to do next, not just describe the product itself.
12 / 12
Ben writes a Slack message in response to a UI design change: 'The new error state copy feels too clinical and lacks empathy. Users are already frustrated; we need to acknowledge that.' What does Ben mean by 'clinical' referring to the error message?
'Clinical' in this context refers to a lack of warmth or human connection—it suggests the message is delivered in a detached, objective manner. Empathy is crucial in error messages; acknowledging the user's frustration demonstrates understanding and builds trust.
This exercise, "Microcopy Review Language", tests your understanding of ux writing vocabulary and phrasing through 12 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 12 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.