UX Writing: The Small Words That Make or Break Your Product

A button that says 'Submit' and one that says 'Get my free quote' can perform very differently. Here's how UX writing and microcopy quietly decide whether people finish what they started.

Teams spend weeks on layouts, colours, and illustrations, then write the button label in thirty seconds. "Submit." "Click here." "An error occurred." Those tiny bits of text are often the last thing a user reads before they decide to act, or to leave.

UX writing is the craft of making the words inside a product as considered as the design around them. It's one of the cheapest, fastest improvements you can make to a website or app, and it compounds across every screen. This guide covers where microcopy matters most and the rules that make it work.

What is UX writing?

UX writing is the practice of designing the text people interact with in a digital product: button labels, form fields, error messages, empty states, onboarding, tooltips, and confirmations. That small, functional text is called microcopy. Unlike marketing copy, which persuades someone to arrive, UX writing helps them get things done once they're there. Good UX writing is clear, concise, useful, and consistent, and it's designed alongside the interface rather than added at the end.

Buttons: say what happens next

A button is a promise. Generic labels like "Submit" or "Continue" make the user work out what they're agreeing to. Specific labels remove that doubt and remind people why they're clicking.

Forms: reduce doubt at every field

Forms are where conversions quietly die. Good microcopy answers the questions people have before they hesitate:

• Use visible labels, not placeholder-only fields. Placeholders disappear when people type, and are harder to read for many users.
• Explain why you're asking. "We'll only call if there's a problem with your order" makes a phone field feel safe.
• Show format hints upfront. Tell people the password rules before they fail them, not after.
• Mark optional fields. Or better, remove them.
• Reassure near the button. "No card needed" or "Unsubscribe anytime" right beside the call to action.

Error messages: helpful, human, and specific

"Invalid input" tells the user they've failed without telling them how to succeed. A good error message does three things: it explains what went wrong in plain language, tells them how to fix it, and keeps their work intact.

Empty states and confirmations

An empty dashboard that just says "No data" is a dead end. An empty state is the best moment to explain what belongs there and offer the single next step: "No projects yet. Create your first one in under a minute." Confirmations work the same way in reverse: tell people it worked and what happens next, such as "Booked. We've emailed your confirmation and we'll text you the day before."

Good microcopy also matters for accessibility: descriptive link text, clear labels, and specific errors help screen reader users just as much as everyone else.

Consistency: write a tiny voice guide

Products often sound like five different people wrote them, because five different people did. A one-page voice guide fixes most of that. Decide your tone (friendly but direct, for example), your preferred terms ("workspace" or "project", never both), how you address users, and a handful of examples. Keep it next to your design system so words and components evolve together, and it becomes part of your brand identity rather than an afterthought.

Step by step

Frequently asked questions