Write the Interface

Words are part of the interface.

UX writing is writing for the user experience. It covers every word that helps someone understand and use a product: buttons, labels, onboarding, empty states, notifications, tooltips, errors, and more.

The goal is not to decorate a screen. It is to put the right words in the right place, at the right time, with the right tone—so the product feels clear, confident, and easy to use.

That makes it different from marketing copy, which attracts attention, and editorial content, which informs. UX writing supports a task. A content designer works at the wider system level: planning, structuring, governing, and connecting content across the entire experience.

The discipline grew from content strategy and the earliest conversational interfaces. Today it extends beyond screens into smart devices, kiosks, voice products, and any experience where language helps a person make a decision.

UX writing lives where people act.

Marketing copy earns attention. Editorial content informs. UX writing supports an interaction. It appears in small, contextual pieces of language often called microcopy.

The interface may be a website, an app, a smart device, a chatbot, a kiosk, or a voice assistant. The surface changes; the responsibility does not. The words must help someone know what is happening and what they can do next.

Do not wait for the final screen.

UX writers work closely with designers, product managers, researchers, developers, support, and marketing. They contribute across the product cycle—not as a final proofreading step.

The writer and designer should work in the same file, inspect the same flow, and make decisions together. Space affects wording; wording affects hierarchy. Collaboration is the work, not a handoff around it.

Clear. Concise. Useful.

These three principles are the fastest way to assess interface copy. If the words fail one of them, the experience creates friction.

Make the message understandable at first sight.

Put the most important information first. Use short sentences, active voice, and familiar words. If a technical term is essential, explain it where it appears. If it is not essential, replace it.

Every component asks a different question.

A CTA predicts an action. An error helps someone recover. An empty state explains what belongs here. Loading copy manages waiting. Good UX writing begins with the component’s job, not a clever sentence.

Use progressive disclosure: reveal the minimum needed for the current decision, then offer deeper detail close by. A tooltip cannot rescue a vague label, and onboarding cannot compensate for a confusing product.

Treat copy as a product decision.

A UX writing audit reviews a complete journey, not isolated sentences. Capture the screen, component, current copy, user goal, issue, proposed change, and evidence. Repeated problems reveal the system work behind the individual fixes.

Test important language in a prototype with the people who will use it. Watch whether they understand the state, predict the action, and recover from problems. For high-volume decisions, compare variants with an A/B test and measure the product outcome—not which sentence sounds nicer.

Borrow language before you invent it.

Good interface language begins with evidence: interviews, support conversations, search queries, reviews, usability sessions, and the words people already use. Collect repeated phrases and the context in which they appear. That is semantic research.

A useful persona is not a fictional biography. It captures the user’s goal, situation, knowledge, anxieties, and vocabulary. Write for the decisions that person needs to make in the product.

Your voice stays. Your tone moves.

Voice is the product’s consistent personality. Tone adapts that voice to the situation. A celebration can be energetic; a payment problem should be calm. The user’s emotional state decides the volume.

When you try to speak to everyone, you end up speaking to no one.

Define voice with useful dimensions rather than loose adjectives. For example: direct rather than chatty, warm rather than playful, expert without sounding technical. For each dimension, show what “more” and “less” sound like in real components.

Turn good decisions into reusable guidance.

A content design system is the shared source of truth for interface language. It combines principles with examples teams can apply while designing and shipping—not a PDF that is opened once a year.

Keep the system relevant by reviewing support requests, store reviews, social conversations, new devices, and emerging interaction patterns.

Make the system clearer for everyone.

Accessible UX writing uses plain language, descriptive labels, short sentences, and context that does not depend on vision, color, or prior knowledge. Inclusivity is not a tone—it is the removal of barriers.

Do not communicate meaning through color, position, sound, or imagery alone. Write links and buttons that make sense out of context. Name the field with a visible label. Explain errors next to the affected input.

Inclusion goes further than technical access. Avoid assumptions about gender, relationships, ability, culture, or available resources. Ask only for information the task truly needs, and do not encode a “normal” user into labels or defaults.

In a voice or conversational interface, language becomes the interface. Design intents, repair paths, confirmations, and contextual responses. The user needs to know what the system understood and how to correct it.

Use AI to explore. Keep the judgment.

AI can generate alternatives, challenge a tone, simplify complex text, cluster feedback, or help audit a flow. It works best with a precise brief: user, context, goal, component, constraints, desired format, and examples from your content system.

Treat every output as a draft. Verify the product behavior, source claims, accessibility, terminology, tone, and privacy before anything ships. A strong workflow asks for several options, compares them against explicit criteria, and improves the brief from the failures.