The Quiet Power of UX Writing: Why Microcopy Decides Whether Your Design Works
Interface copy is a design material, not a finishing touch. How to write microcopy that reduces errors, lowers support load, and makes products feel considered.
Most microcopy gets written last, in the gap between design approval and handoff, by whoever is available. That is why so much of it is vague, and why vague interface copy shows up in support tickets.
Interface writing is not copywriting. Nobody is being persuaded. Your job is to remove ambiguity at the exact moment a person is uncertain, and that is a much narrower and more technical skill than marketing writing.
Write for the moment of uncertainty
Every label, error, and confirmation should answer the question the user actually has at that moment. Not "what do we want to say", but "what is the person trying to find out".
- Buttons describe the action, not the destination. "Save changes" beats "Continue".
- Errors say what failed and what to do. "Card number is incomplete" beats "Invalid input".
- Confirmations confirm the specific thing, with the specifics. "Booking confirmed for 14 March, 6:30pm" beats "Success".
The words you cut are the ones that help
Vague words are usually there to avoid committing to a claim. "Some of your details are invalid" hedges in a way that makes the person read it twice. Specificity is kinder, because it is faster.
Symmetry matters more than people expect. If one button says "Start free trial", no button on the screen should say "Learn more about pricing". Inconsistent vocabulary makes interfaces feel careless even when the user cannot explain why.
Voice is part of the design system
Tone should be defined alongside colour and type, and enforced the same way. Deciding in advance that errors are direct but never harsh, and that empty states suggest a next action, removes a whole class of inconsistent-feeling products.