Microcopy Review Language

"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

"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

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)

"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

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)