Skip to content
UXE Award

UX writing that scores: the words editors actually notice

Interface copy decides how competent a product feels. The error messages, empty states, button labels and confirmations that raise a UX writing score — and the habits that quietly lower one.

The UXE editors6 min read

Nobody opens a product to read it. But every screen is read — quickly, under mild pressure, usually while trying to do something else — and the words decide whether the product feels like it was made by people who understood the job. In scoring, interface copy touches usability, learnability and interaction all at once, which is why UX Writing & Content Design entries can lift a whole entry or sink one.

Error messages: the highest-leverage words in any product

An error is a moment when someone is already slightly annoyed and entirely focused on your text. That combination makes it the most-read sentence in the product and the one most often written by an engineer at 2am.

A message that scores does three things in order: says what happened, in the user's terms; says what to do next; and — if relevant — preserves what they'd already done.

Five errors, written twice
Compared onScoresCosts
PaymentYour bank declined the card. Try another card, or call them — nothing has been charged.Transaction failed (code 51)
UploadThat file is 24MB — the limit is 10MB. Try a smaller image or a PDF.Invalid file
SaveCouldn't save — you're offline. We've kept your changes and will save them when you reconnect.Something went wrong
PermissionsOnly workspace admins can invite people. Ask Maya or Tom, who are admins here.Forbidden
SessionYou were signed out after 30 minutes. Sign in and we'll take you back to where you were.401 Unauthorized

Empty states: the best teaching opportunity you'll get

The empty state is the only screen you can guarantee a new user will see, and most products waste it on the word "None". A good one names what will appear here, explains how to make it appear, and offers the action — in that order.

It's also the most under-sent screen in award entries. Send it; almost nobody does, and it's a fast way to show craft.

Buttons: name the outcome, not the mechanism

  • Save changes beats Submit. Send invoice beats Confirm. The label should complete the sentence "I want to…".
  • In a confirmation dialog, never Yes / No. Put the outcome on the button: Delete three files / Keep them.
  • The cancel option should say what cancelling does when that isn't obvious: Discard draft rather than Cancel.
  • Avoid the disabled primary button with no explanation. If it can't be pressed, say what's missing.

The voice test: read it aloud to a colleague

Interface copy that sounds strange spoken is copy that will feel strange read. Three habits fail this test immediately:

How copy behaves when things go wrong

Habits that age badly

  • Cheerfulness in a failure state — "Oops! Something's not quite right!"
  • Nouns doing verbs' work — "Initiate the configuration process"
  • Brand voice in a moment of stress
  • Jargon borrowed from the database schema

What reads well under pressure

  • Plain, calm, specific
  • The user's noun, not the system's
  • Short sentences, one idea each
  • Numbers and names instead of "some" and "items"

Some copy isn't only usability. Consent, cancellation, deletion, money and health are places where the words are the ethics — and editors score them under Inclusive & Ethical Design as well as UX writing.

  • Consent: the reject option must be as easy to find and as easy to press as the accept option. Prominence is a design choice, and it is visible.
  • Cancellation: if signing up took two clicks, cancelling should not take a phone call. Editors check this on subscription products.
  • Deletion: say what is deleted, what is kept, and whether it can be recovered. "This can't be undone" is the minimum.
  • Money: never round, never hide, never defer. Show the total, the currency and what's included.

Localisation and plain language

Copy that only works in English at one length is fragile. German and Finnish run long, Japanese runs short, right-to-left languages change the layout's assumptions. Entries that handle this well use sentence-shaped strings rather than concatenated fragments, never bake a number into a translated string, and set plural rules properly.

Plain language is a related discipline: shorter words, active voice, one idea per sentence. It helps everyone, and disproportionately helps people reading in a second language, under stress, or with a cognitive disability. It is not dumbing down; it is respecting a reader's time.

What to send in a content design entry

Four things to include
  1. 01

    The worst moment

    Your hardest error, your most sensitive confirmation.

  2. 02

    The empty screen

    A genuinely new account, before anything exists.

  3. 03

    The decision

    A before-and-after of copy you rewrote, and why.

  4. 04

    The rules

    Your voice guidelines or terminology list, if you have one.

One measured outcome helps enormously here, because content change is unusually easy to measure: support tickets about a specific flow, completion on a form you rewrote, or the drop-off step that stopped dropping off.

If words are where your product's craft lives, enter UX Writing & Content Design alongside your main category — the same entry, one fee, two categories. Start here.

Terminology: choose once, then never drift

The quiet failure in most products is the same concept with three names. The database calls it an organisation, the interface calls it a workspace, the support article calls it a team, and the customer calls it none of those. Every extra name is a small tax on comprehension.

A terminology list — one word per concept, with the rejected alternatives and the reason — is cheap to keep and unusually persuasive in an entry, because it is evidence of a decision rather than a style.

Writing for AI-assisted and agentic surfaces

Products increasingly speak through generated text as well as written text. The same standards apply, plus two more: the interface must be honest about what is generated, and it must say what the system did rather than what it intends.

  • Label generated content where a reader could otherwise mistake it for a human decision.
  • Prefer a stated action to a confident summary: "Removed 4 duplicates" beats "Cleaned up your list".
  • Say what the system could not do, not only what it did.
  • Give a path back: an undo, an edit, or a way to see what was changed.

Reading level, tested rather than calculated

Readability formulas are a blunt proxy. They can't tell that "remittance" is harder than "payment" for your audience, or that a short sentence of jargon is worse than a long plain one. The test that works is watching someone read it and asking them what they think happens next.

Questions we get asked

  • Can UX writing alone win a category?

    Yes — UX Writing & Content Design is judged on the words, and a product with ordinary visual design and exceptional content can win it. The entry needs to show the words doing work, not a tone-of-voice document.

  • What's the single highest-impact thing to rewrite?

    Your error messages, then your empty states. They're the most-read and least-designed text in almost every product.

  • Should error messages apologise?

    Briefly, if the fault is yours, and never at the expense of clarity. "Sorry" before an unexplained failure is worse than a plain statement of what happened and what to do.

  • How do we handle copy in a localised product?

    Write sentence-shaped strings rather than concatenating fragments, never bake numbers or names into a translated string, set plural rules, and test with the longest language you ship.

Assessed work that scores highest on information architecture

Chosen by score from the work the editors have assessed, not by hand.

  • ux writing
  • content design
  • microcopy

Written by

The UXE editors

The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.