UX writing: words are interface
Copy is not decoration added at the end. It's a design decision with the same weight as spacing, color, or hierarchy.
Copy is not decoration
It arrives late in most projects. The design is done, the components are built, and then someone fills in the placeholder text. “Lorem ipsum” becomes real words without anyone really deciding what those words should be.
That’s not a writing problem. It’s a design process problem.
Copy is part of the interface. It guides, clarifies, reassures and directs. It has the same weight as spacing, color, or visual hierarchy. Treating it as decoration — something to fill in at the end — produces interfaces that look finished but feel broken.
The gap between generic and specific
The difference is visible in the smallest moments.
A button that says Submit tells you nothing. A button that says Send message tells you exactly what happens next. One is a placeholder. The other is a decision.
An error message that says Something went wrong leaves the user stuck. An error message that says We couldn’t process your payment — check the card number and try again gives them a path forward.
The generic version is easier to write. The specific version is easier to use. That gap is where UX writing lives.
Four principles worth keeping
Clarity over cleverness. A clever headline that takes a second to parse has already failed. Users don’t read — they scan. If your message requires effort to decode, most people won’t decode it.
Action verbs. Buttons, CTAs, confirmations — start with a verb. Not “New project” but “Create project.” Not “Account” but “Manage your account.” Verbs tell users what happens when they act.
Consistent tone. If your interface is friendly in the onboarding and formal in the error states, it feels like two different products. Tone should be a system decision, not a per-screen decision.
User context first. Write from where the user is, not from where your product is. They’re not “completing the registration flow” — they’re trying to get started. That difference shapes every word.
Copy follows the same rules as components
This is the part that changes how you think about it.
A component has defined behavior, consistent states, and documented usage rules. Copy should too. The way you address the user (you / your vs. the user / their), the capitalization style (sentence case vs. title case), the voice in error states, the length of button labels — these are system decisions, not case-by-case calls.
An interface where copy follows rules feels coherent. An interface where copy was written on the fly feels rough — even if the design is flawless.
The words in your interface are doing work constantly. The question is whether they’re doing the right work, or just filling space.