The Principles of UX Writing (That Nobody Tells You About)
UX writing is one of those disciplines that sounds simple until you actually do it. How hard can it be to write a button label? Turns out, very. Because behind every two-word CTA is a decision about what the user needs to know, what they are feeling, what the business needs them to do, and how the brand sounds while asking. Getting all of that right, in four characters, is a craft.
This post walks through the core principles I keep coming back to. Some come from the books on my desk. Some come from making mistakes in front of real users. All of them are worth talking about.
Start with clarity, not cleverness
The most common mistake in UX writing is reaching for wit before you have earned it. Clarity is not a consolation prize for writers who lack personality. Clarity is the personality. As Torrey Podmoresky puts it in Strategic Writing for UX, the words in a product are not decoration. They are part of the experience itself. When the words fail, the experience fails, regardless of how beautiful the interface looks.
Sarah Winters makes a similar point in Content Design: writing for digital products is not about filling space. Every word has to earn its place. If you can remove it without losing meaning, remove it.
But here is the nuance that gets lost in the “fewer words” conversation: conciseness is not the goal. Clarity is. Sometimes clarity takes more words. A curt error message that leaves users confused is worse than a slightly longer one that tells them what went wrong and what to do next. Brevity in the service of clarity is a virtue. Brevity at the expense of clarity is just unhelpful.
Give users exactly what they need at that moment
Microcopy is not a feature. It is infrastructure. And like good infrastructure, the best microcopy is invisible because it works so well that users never have to think about it.
Kinneret Yifrah, in Microcopy: The Complete Guide, describes microcopy as the small bits of text that guide users through moments of uncertainty, friction, or decision. A form field hint. An error message. A tooltip. A confirmation dialog. These touchpoints seem minor in isolation, but they are often exactly where users abandon a task or lose trust in a product entirely.
The key is matching the amount of information to the moment. Early in a journey, when a user is exploring, they need orientation. Later, when they are mid-task and committed, they need precision. Dumping all your information at the wrong step does not help users; it overloads them. Cognitive load is not just a UX research concept. It is something you can add or reduce with every sentence you write.
A useful question to ask at every touchpoint: what does this person know right now, and what do they need to know to take the next step? Nothing more, nothing less.
Write for pull, not push
This one reframes how you think about the whole discipline. UX content is pull, not push. Users are not a passive audience waiting to receive your message. They are people trying to complete something. They are scanning, skipping, and filtering. They will read what they need and ignore the rest.
This means you cannot write for users the way you write a press release or a marketing campaign. You are not broadcasting. You are answering questions users already have, at the moment they have them. The content has to be there when they look for it, and it has to answer the right question in the right language.
It also means that if users are ignoring your content, the problem might not be the words. It might be the placement, the timing, or the format. Sometimes, the most powerful UX writing decision is to say nothing at this step and say everything at the next.
Tone is not a nice-to-have
Every product has a personality. If you do not define it deliberately, users will define it for you, and you may not love the result. The classic example is Google in its early years: brilliant, useful, and widely perceived as cold and overly technical. Not because anyone decided that. Because no one decided otherwise.
Brand voice in UX writing is not about being fun or adding exclamation points. It is about making consistent choices. Are you formal or conversational? Do you use humor, and if so, where? How do you sound when something goes wrong? Those choices, made consistently across every screen and every state, are what personality actually is.
The test I find most useful comes from Content Design: can you read this aloud so everyone in the room understands it? Not just developers. Not just your team. Everyone. If the answer is no, the language is probably working against you. Jargon, passive voice, and abstract nouns are the usual culprits.
Tone also has to flex. A confirmation screen for a bank transfer should not sound the same as an onboarding welcome message. The brand voice stays consistent, but the register shifts to match what the user is going through.
Write with empathy, and lead with the benefit
Users do not want to complete your forms. They do not want to verify their email or set up two-factor authentication. They want the thing those actions unlock. So write toward the thing they want, not the action you need them to take.
“Verify your email to continue” tells users what you need them to do. “Confirm your email, and you are ready to go,” tells users what they get. The second version is not just warmer. It is more motivating because it connects effort to reward.
This extends to how you handle errors and friction. Never make users feel stupid, guilty, or inadequate. Not in error messages. Not in empty states. Not in permission requests. The language of shame and blame (“invalid password,” “you must,” “you failed”) creates anxiety and erodes trust. The language of guidance (“that password does not match, try again,” or “we need your location to find stores near you”) keeps users in motion and maintains the relationship.
Scott Kubie and Michael Metts make this point well in Writing is Designing: designers and writers are making decisions together about how users experience a product. That experience includes how it makes them feel. Empathy is not a soft skill in this context. It is a design requirement.
Accessibility is not an edge case
Writing accessible UX content means writing for a much wider range of human experience than most briefs account for. Neurodivergent users may process language differently. Users who have experienced trauma may have strong reactions to certain phrasings. Users with cognitive or reading differences need plain language, consistent structure, and clear hierarchy. Users whose first language is not yours need to be able to run your content through a translation tool without losing meaning.
Plain language is the foundation. Short sentences. Active voice. Concrete nouns. Verbs that describe what actually happens. This is not dumbing it down. It is widening the door.
Beyond language, think about what your content assumes. Forms that assume a user has a middle name, a fixed address, or a binary gender are not neutral. They exclude people before a word has been read. UX writers are not always the ones who make those structural decisions, but they are well-placed to flag them. Diverse content is not about adding a disclaimer. It is about building a product that does not accidentally tell whole groups of people they do not belong here.
Words are not always the answer
This is perhaps the most liberating principle, and the one most worth repeating in a blog post about writing: sometimes the best UX writing is less writing.
If a screen is confusing and you are reaching for a tooltip, stop and ask whether the screen itself could be redesigned. If an error message is getting long, ask whether the form could be structured to prevent the error in the first place. If users keep missing a piece of information, ask whether a visual, an icon, or a diagram might communicate it more effectively than another sentence.
Writing is Designing is explicit about this: content and design are not separate tracks that merge at the end. They are the same conversation, happening at the same time. The best products are built that way from the start.
UX writers who understand this are much more useful than UX writers who see their job as filling in the text boxes after the screens are built. The question is never “what should this say?” The question is “what does this person need here, and what is the best way to give it to them?”
Sometimes that is eight words. Sometimes it is a picture. Sometimes it is removing a step entirely.
The line between UX writing and content design
If you have been in this field for more than a few months, you have probably encountered the debate about what to call all of this. UX writing, content design, and content strategy: the terms overlap, compete, and mean different things to different organizations. I wrote a longer piece on exactly this distinction if you want to go deeper.
The short version: UX writing is the craft of writing for interfaces. Content design, as Winters defines it, is broader. It is about deciding what content should exist at all, in what format, and where, before a single word is written. Both matter. In practice, the best practitioners do both.
A note on the books
Most of what is written above has been shaped by a handful of books I genuinely recommend:
Content Design by Sarah Winters is the clearest articulation of what it means to design with content rather than add content to a design. Practical, opinionated, and direct.
Writing is Designing, by Michael Metts and Andy Welfle, makes the case that writers and designers do the same work and should be at the table together from day one.
Strategic Writing for UX by Torrey Podmoresky is the most practical of the three for people working inside product teams. It covers voice, tone, patterns, and the politics of getting good content through an organization.
Microcopy: The Complete Guide by Kinneret Yifrah is the closest thing the field has to a reference manual for the small moments that make or break an experience. The examples alone are worth the read.
Beyond these, Nielsen Norman Group publishes consistently strong research on UX writing and content strategy. Erika Hall’s Just Enough Research is not a UX writing book, but it is an essential read for understanding users well enough to write for them. And if you want to go deep on plain language, the U.S. government’s plainlanguage.gov is a surprisingly rich and well-maintained resource.
UX writing done well is invisible. Users do not notice the copy when it is working. They feel like the product understands them, like it is guiding them without getting in the way, like it is on their side.
That is the whole job.
