clarify

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. For example, replace "Invalid input" with "Email addresses need an @ symbol. Try: name@example.com" and link to help when applicable.

Audit the copy for jargon, ambiguity, passive voice, and missing context, then rewrite each element to state one clear message and the next action. Apply principles like being specific, concise, active, human, helpful, and consistent in terminology.

Good button labels describe the specific action using active voice, such as "Create account" or "Save changes" instead of generic text like "Submit" or "OK". The label should match the user's mental model of what happens next.

Use confirmation dialogs only for risky or destructive actions, stating the specific action and its consequences, such as "Delete 'Project Alpha'? This can't be undone." Overusing confirmations trains users to ignore them.

Common mistakes include unexplained jargon, vague messages like "Something went wrong", blaming users, inconsistent terminology, placeholders used as the only labels, and humor in error states. Each of these reduces comprehension and increases support requests.