In brief: UX writing creates text directly in a user interface so that a person understands the options, state, consequences, and next step.
How I use UX writing in practice
With UX writing, I start with the visitor's task, not the designer's idea. I go through the journey on a small mobile screen, with a keyboard, and on a slow connection, then watch where a person hesitates or makes mistakes. Every change should have a reason, a measurable signal, and the smallest possible intervention, so that its impact can be identified.
What to watch out for
The most common mistake is changing several things at once without a baseline. It then becomes impossible to tell whether UX writing actually helped. A metric alone, without observation, also cannot explain why people hesitate or leave.
Questions for the decision
- What task does a person want to complete on the page?
- Where might they hesitate, make a mistake, or lose context?
- Does the solution work on mobile, with a keyboard, and on a slow network?
- Which signal will show that the change genuinely helped?