UX writing best practices

UX writing is the practice of crafting the text that appears inside a digital product: buttons, form labels, tooltips, notifications, status messages and every piece of microcopy that guides a user through their journey.

Unlike advertising copywriting, the goal is not to sell but to orient. A button that reads "Save draft" is more useful than one that says "Submit". An error message that explains how to fix the problem is more valuable than one that simply says "Error". The core premise is that words are part of the design, not an afterthought.

Effective microcopy rests on three pillars: clarity, brevity and context. Clarity means using vocabulary the user understands, not internal jargon. Brevity means cutting every word that adds no meaning. Context means the text must fit the exact moment in the flow where it appears.

Google changed its main button from "Submit" to "Google Search", reflecting exactly what the user expects to happen. Booking.com shows "Only 2 rooms left" instead of a generic "Book now" — contextualised copy outperforms generic copy because it speaks to the user’s actual situation.

An effective call to action communicates the benefit of clicking, not just the mechanical action. "Start free" works better than "Sign up" because it telegraphs what the user gets. "See pricing" creates less perceived commitment than "Request a quote" and, in many contexts, earns more clicks precisely because of that.

Position and visual contrast matter, but the text is what removes the final barrier. Dropbox switched from "Sign up for free" to "Try Dropbox Business free" and boosted enterprise plan conversions because the CTA specified what users would be trying. The same principle applies to contact forms, checkout and onboarding.

Error messages are the most critical moment for microcopy. A user hitting an error is already frustrated; the text can either make things worse or resolve the situation. The optimal structure has three parts: what happened, why, and how to fix it.

Stripe shows "Your card number is incomplete" rather than "Invalid card number". The difference is subtle but decisive: the first pinpoints the cause and implies the fix (add the remaining digits), the second merely declares a failure. Mailchimp says "This email address already has an account. Want to log in?" with a direct link, turning an error into an alternative path.

Onboarding is the product’s first impression. A welcome flow with good copy reduces drop-off and accelerates time-to-value — the moment the user first perceives the benefit. Empty states, screens with no data because the user hasn't created anything yet, are another underused opportunity.

Notion displays "Start with a blank page or pick a template" in its empty state, steering the user toward two clear actions. Slack’s onboarding says "This is where your team communicates" with a single step before letting users loose in the tool. Fewer steps, more context and clear actions — that is the formula.

Tone of voice is the product’s personality expressed in words. It is not about being funny or formal — it is about being consistent. Mailchimp defined their tone as "informal but not sloppy, confident but not cocky" and documented clear rules: use contractions, avoid jargon, don't shout in all caps.

A UX writing tone-of-voice guide should include at least: general principles (three or four adjectives that define the voice), do-and-don't examples for each message type, and specific grammar rules such as whether to use second person, how casual to be, and the level of formality in different contexts.

UX writing is not prose — it can be measured. A/B tests let you compare variations of a CTA, a heading or an error message and observe the impact on concrete metrics. A HubSpot experiment showed that changing "Start your free trial" to "Get started free" lifted sign-ups by 17 % without touching any visual element.

Beyond A/B tests, think-aloud usability sessions reveal whether users understand the copy or pause to re-read it. Task clarity surveys measure whether participants grasp what is being asked of them. And support ticket analysis pinpoints the screens where microcopy is failing.