itsual UX Writing
Overview
UX writing is design with words. Every label, error, and empty state either reduces friction or adds it.
When to Use
- Writing or rewriting UI microcopy
- Designing empty states, errors, and success messages
- Creating onboarding or in-product guidance text
- Establishing product voice and tone guidelines
Core Practices
- Lead with the user’s goal and next action
- Use plain language; avoid jargon unless the audience expects it
- Make buttons describe the action (“Save draft,” not “OK”)
- Write errors that explain what happened and how to fix it
- Keep consistency in terminology across the product
- Design copy for scanning — short lines, front-loaded meaning
Principles
- Clarity first, brand voice second (they should reinforce, not fight)
- Be helpful without being verbose
- Respect the user’s attention and emotional state (especially in errors)
- Inclusive language is part of quality
Verification
- A new user can understand key actions without help
- Error messages enable recovery
- Terminology is consistent across surfaces