The short answer
UX writing is the craft of writing the text inside a product: button labels, form hints, error messages, empty states and confirmations, sometimes called microcopy. Good UX writing is short, specific and in the user’s language. Lead with the important words, say what will happen when a button is pressed, and write errors that explain what went wrong and how to fix it. Words are part of the design, so test them with users like any other part.
Key points
- Buttons say what they do: "Create invoice", not "Submit".
- Lead with the words that matter most.
- Errors explain what happened and how to fix it, without blame.
- Use the words your users use, not internal names.
- Be consistent: one name for one thing, everywhere.
Principles
- Concise: cut every word that does not help the user act.
- Front-loaded: put the key word first, because people scan.
- Plain: write so it is understood on first reading.
- Specific: say what will happen, with real nouns and verbs.
- Consistent: the same term for the same thing across the product.
The Nielsen Norman Group describes plain language as content that can be understood the first time it is read, and notes that it benefits all users, not only those with less time or expertise.
Before and after
| Where | Before | After |
|---|---|---|
| Button | Submit | Send request |
| Error | Invalid input | Enter a date after today |
| Empty state | No data | No projects yet. Create your first one. |
| Delete dialog | Are you sure? | Delete this project? Its files will be removed too. |
| Field hint | Format: DD/MM/YYYY | For example, 15 March 2027 |
| Success | Operation completed successfully | Invite sent to priya@example.com |
Error messages
- Show the message next to the problem, not only at the top of the page.
- Say what went wrong in plain words, without codes or blame.
- Say how to fix it.
- Keep what the user typed, so they do not start again.
Working with words
- Write real copy in wireframes, not placeholder text, so flows are judged with their words.
- Keep a short word list: the agreed terms for key things in the product.
- Listen in user interviews and support tickets for the words customers use.
- Test key screens with users, and watch whether they understand the labels.
Words are part of testing a design. See Usability testing. Interface copy is designed with the screens in our UI/UX design work.
Sources
Checked when this guide was written.