UX writing succeeds when nobody notices it. The label is clear, the button does what it says, the error explains how to fix the problem. The person finishes the task without stopping to interpret the words.
That invisibility takes deliberate work.
Write from the user's side#
Interfaces often describe themselves in the language of the system: sync failed, invalid input, entity not found. People think in terms of their goals. Name things the way they would name them, and describe outcomes rather than internal states.
Simple rules for labels and buttons#
- A button says what will happen: Save draft, Place order, Send message
- Avoid vague verbs such as Submit, OK or Continue when a specific one exists
- Keep labels short and consistent across the product
- Use sentence case; it reads faster than title case
Errors should help#
An error message has two jobs: say what went wrong and how to fix it. "Enter a phone number with 10 digits" is better than "Invalid phone number". Put the message next to the field, not in a banner at the top of the page.
Empty states are an opportunity#
An empty cart, an empty search, a new account with no data. These moments are when people are most unsure what to do next. Explain what will appear here and offer the first step.
Good copy answers the question the user was about to ask.
Read it aloud#
Read the whole flow aloud as if you were explaining it to a friend. Anything you would not say out loud probably should not be on the screen.
Keep a word list#
Decide once whether it is a cart or a bag, sign in or log in, delete or remove, and use the same word everywhere. A short shared list prevents small inconsistencies that make an interface feel unfinished.
