UX writing is the words inside the product: buttons, labels, errors, empty states. It is the cheapest place to improve conversion and the most common place products feel unfinished, because the words get written last, by whoever is nearby. Here are the practices that make interface copy do its job.
Buttons say what happens
The rule: a button describes the outcome of pressing it. “Save changes”, “Send invoice”, “Start free trial”, never “Submit”, “OK”, or “Continue” when something concrete is about to happen. And the name stays consistent through the flow: a button that says “Publish” leads to a message that says “Published”, not “Success!”. This is signposting, and cohesion is how people learn an interface.
Errors explain and instruct, in that order
A good error message answers three questions without drama: what happened, is my stuff safe, what do I do now. “Card declined. Your order is saved; try another card or contact your bank.” beats “Payment error (code 402)”. Errors never apologize theatrically and never blame the user, and in money products they carry extra weight: ambiguity about whether a transfer went through is how trust dies.
Empty states are invitations
“No projects yet” is a shrug. “Create your first project to see analytics here” is a direction. Every empty screen should say what belongs there and offer the action that fills it, which is why empty-state copy is the backbone of onboarding that activates.
Labels name what users control, not how you built it
People manage “notifications”, not “webhook config”. Menus and settings should use the vocabulary of the user’s world; the system’s internals stay internal. When a term needs learning (every product has a few), define it once, in place, and use it identically everywhere.
The register: plain, specific, calm
Active voice, sentence case, short verbs. Specific beats clever every time: “Export as CSV” not “Liberate your data”. Personality lives in the brand layer, the marketing site can charm; the interface should mostly get out of the way, because users are mid-task and cleverness reads as friction the third time.
Why this affects conversion and search
Hesitation compounds: a vague button here, a scary error there, and completion rates sag without a single complaint. Clear microcopy also makes products more accessible (screen readers read your labels aloud) and pages more quotable for AI search, which favors interfaces and docs that name things plainly.
The audit you can run today
Read every button on your critical path aloud. If any answer to “what happens when I press this?” is unclear, rewrite it. Then read your errors and ask “would a stressed person know what to do next?” An afternoon of this routinely beats a quarter of redesign.
Copy is design. We write it as part of every product we build: hello@beconfidency.agency, or see finished interfaces in our works.
This is the discipline behind our product design service, where these patterns ship in real software.
