Most interfaces fail users at the small moments: the button that says “Submit,” the error message that reads “Invalid input,” the empty dashboard with no explanation. These are microcopy failures, and they cost more than their word count suggests.
UX writing is the craft of giving every interactive element the right words at the right moment. It sits adjacent to writing website copy but operates at a finer grain: instead of homepage headlines, it handles the labels, states, tooltips, and confirmations that carry users through real tasks.
Why Small Copy Has a Large Effect
An interface can be visually polished and functionally broken if the words are wrong. A button that says “Go” leaves users wondering what happens next. A form that returns “Error” without specifying which field failed creates friction that ends in abandonment. A password field with no guidance breeds wrong guesses and support tickets.
Microcopy matters disproportionately because users encounter it at the moment of action. They are already committed to doing something. Bad copy at that moment doesn’t just confuse them; it erodes trust in the product. If they couldn’t write a clear error message, what else did they rush?
The best microcopy is invisible. Users notice it only when it’s missing.
Buttons: Verbs, Specificity, and Commitment Signals
The weakest button copy is also the most common: Submit, Continue, OK, Go. These words name an action without describing what happens. They put the cognitive load on the user.
Better button copy names the outcome:
- “Create account” rather than “Submit”
- “Send message” rather than “OK”
- “Download the guide” rather than “Get it”
Match the copy to the commitment level. “Start free trial” reads differently than “Buy now,” even if they trigger the same form. The word “trial” reduces perceived risk. And the button copy and its surrounding context need to agree: if the heading says “Try it free for 14 days” but the button says “Purchase,” users feel the dissonance even when they can’t name it.
For destructive actions, copy has to do more work. “Delete” alone gives no signal about reversibility. “Delete forever” or “Remove from list” is more specific, and specificity reduces regret-driven complaints.
Form Labels, Helper Text, and Placeholders
Form microcopy is one of the highest-impact areas in a product, because forms are where users commit: they give data, initiate payments, create things. Friction here drops completion rates in ways that show up quickly.
Label copy should say what the field collects, not what the user already knows. “Email address” is fine for most contexts. “Work email (used for your login)” is better when the distinction matters.
Placeholder text is frequently misused. It should suggest format, not restate the label. A field labeled “Phone number” needs a placeholder like “e.g. +1 555 000 0000,” not “Phone number.” Placeholders should also disappear on focus, since users lose context when they’re mid-entry and the label is gone.
Helper text sits below a field and survives input. Use it when requirements are non-obvious: password rules, character limits, formatting expectations. Put it there from the start, not only after the user has guessed wrong.
Error Messages That Don’t Frustrate
Error copy is where most products lose the user’s benefit of the doubt.
“Invalid input” is the canonical failure. It tells the user something went wrong but not what, not where, and not what to do next. The user is stuck.
Good error messages do three things: they identify the problem, they locate it, and they tell the user how to fix it. “Your email address doesn’t look right. Check for a missing @ or a typo” is more work to write but far more useful than a one-liner.
A few principles that hold across most contexts:
- Be specific. “Password must be at least 8 characters” beats “Password is too short.”
- Don’t blame. “We couldn’t find that email” is softer than “Email not found.” Functionally identical; perceptually different.
- Use plain language. Technical strings like “null value” or “422 Unprocessable Entity” are dev output that leaked into production. Replace them.
Validation timing also matters. Inline validation (checking a field when the user leaves it rather than waiting for submit) catches errors before they feel final. The copy for inline validation needs to be even more concise because it appears mid-flow, when the user’s attention is on the next field.
Empty States and Loading Moments
Two often-ignored microcopy situations: empty states and loading screens.
An empty state is what a user sees before they’ve done anything, or when data returns nothing. “No results” is the lowest-effort response. A better empty state explains the condition and offers a path: “You haven’t added any projects yet. Create your first one to get started.”
The distinction matters most when the empty state might be mistaken for a bug. If a filter returns zero items, say so and offer to clear it. If an inbox is genuinely empty, say that rather than showing a blank panel that users will refresh three times.
Loading states are similar. “Loading…” is passable for sub-second waits. When a load takes two or more seconds, progress copy that signals what’s happening (“Setting up your workspace,” “Fetching your reports”) is better than a spinner in silence.
The Trade-off: Brevity vs. Clarity
The correct default for microcopy is short. Interfaces are not reading environments. But brevity that sacrifices clarity is a false economy.
The test is simple: if removing a word makes the copy less clear, keep the word. “Email” is fine as a label. “Work email” is two words that prevent a question later. Both are short. Only one is specific enough for contexts where it matters.
This same tension shapes compressed copy in every format. Writing a strong tagline presents the same problem: the goal isn’t the fewest possible words, it’s the fewest words that do the full job. In microcopy, that job is guidance, not persuasion.
When you’re genuinely unsure which version is clearer, watch five users read it. That will outperform any amount of internal debate.
How Strynal Approaches UX Writing
UX writing lives at the intersection of product and content. It requires understanding what the user is trying to do at each step, where anxiety or confusion typically appears, and how much reading context the interface actually provides.
Our motion and content work includes content design at the interface level, connected to the broader copy strategy rather than treating button labels and marketing headlines as separate problems. Voice consistency matters here: if your marketing copy sounds confident and direct but your error messages sound like a legal disclaimer, users register the gap.
Good microcopy isn’t a finishing pass on a completed interface. It belongs in the structure from the start. If the words are getting added last, that’s the thing worth changing.