UX Writing Glossary

This glossary includes the essential terms and concepts of UX Writing, Content Design, and Strategic Product Writing — from foundational principles like microcopy and plain language to advanced concepts like Content Ops and GEO. Each entry includes an easy-to-understand definition, a real-world example, and practical context for applying the term in professional UX Writing work.

Terms are organized alphabetically and cross-referenced throughout.

New entries are added regularly.

#

  • A 404 error page is the screen a user sees when they navigate to a URL that does not exist — because the page was moved, deleted, or the URL was mistyped. In UX Writing, a 404 page is an opportunity, not just a failure state: good 404 copy acknowledges what happened, avoids technical jargon, reflects brand voice, and gives users a clear path forward.

    Example: "We can't find that page. It may have moved or no longer exists. Head back to the homepage or search for what you need."

    Note: Overly clever 404 copy ("Oops, you broke the internet!") can feel dismissive when a user is genuinely frustrated. Balance brand personality with practical helpfulness.

    See also: Happy Path, User Journey, Microcopy

A

  • A11y is a numeronym for "accessibility" — the 11 letters between the "a" and "y". In UX Writing, accessibility means creating copy that can be understood and used by everyone, including people with visual, cognitive, motor, or auditory impairments. This includes writing descriptive alt text, meaningful link labels, clear error messages, and using plain language throughout.

    Example: Instead of a link that reads "click here", an accessible alternative is "Download the accessibility guidelines (PDF, 2 MB)" — it tells screen reader users exactly what happens and what to expect.

    Note: Accessibility in UX Writing is closely tied to WCAG (Web Content Accessibility Guidelines). ARIA labels, alt text, and plain language are its core tools.

    See also: Alt Text, ARIA Label, Plain Language, Cognitive Load

  • In UX Writing, an affordance is a signal created through copy that tells users how to interact with something. A button labeled "Save changes" affords saving; a link that reads "Learn more about pricing" affords navigation. Good UX Writing makes affordances explicit — users should never have to guess what a label or CTA will do.

    Example: "Delete account" affords a destructive, permanent action. "Archive project" affords a reversible, non-destructive one. The words alone change user behavior.

    Note: The term originates from psychologist James Gibson and was popularized in UX by Don Norman in The Design of Everyday Things.

    See also: CTA, Destructive Action Warning, Microcopy

  • Alt text (alternative text) is a written description of an image used in UX Writing to make visual content accessible to everyone. It is read aloud by screen readers, displayed when an image fails to load, and indexed by search engines. For UX Writers, alt text is not just an accessibility checkbox — it is a content decision that affects both user experience and SEO.

    Example: A bar chart showing Q3 revenue growth: alt text should read "Bar chart showing 40% revenue increase in Q3 2024 compared to Q3 2023" — not "chart" or "image001.png".

    Note: Decorative images should have empty alt attributes (alt="") so screen readers skip them. Alt text should describe function, not just appearance.

    See also: A11y, ARIA Label, SEO

  • An ARIA label (Accessible Rich Internet Applications label) is an HTML attribute that UX Writers use to provide a text description for interactive elements when visible copy alone is insufficient. It is read by assistive technologies such as screen readers and is critical for making products accessible to all users.

    Example: A button showing only a trash icon needs an ARIA label: aria-label="Delete message". Without it, a screen reader announces only "button", leaving the user without context.

    Note: ARIA labels are invisible to sighted users but critical for screen reader users. They should be action-oriented and specific. Work closely with developers to implement them correctly.

    See also: A11y, Alt Text

C

  • In UX Writing, cognitive load refers to the total mental effort a user needs to process copy and complete a task. High cognitive load leads to errors, frustration, and abandonment. UX Writers reduce cognitive load by using plain language, short sentences, progressive disclosure, and clear headings — presenting only the information the user needs at that specific moment.

    Example: "Your session has expired due to prolonged inactivity. Please reauthenticate." vs. "You've been logged out. Sign in again." — the second reduces cognitive load significantly.

    Note: Cognitive load theory was developed by educational psychologist John Sweller. In UX Writing, it is one of the strongest arguments for plain language and chunking content.

    See also: Plain Language, Progressive Disclosure, Information Hierarchy, Scanability

  • In UX Writing, a confirmation is a message or dialog that either verifies a user's intent before executing an action, or acknowledges that an action has been completed. Confirmations come in two types: pre-action ("Are you sure you want to delete this?") and post-action ("Your changes have been saved."). The copy must be specific, clear, and match the emotional weight of the action.

    Example: Post-action: "Message sent." Pre-action: "Delete this conversation? You won't be able to recover it."

    Note: Not every action needs a pre-action confirmation — overuse trains users to dismiss dialogs without reading them. Reserve them for irreversible or high-stakes actions.

    See also: Destructive Action Warning, Friction, Modal

  • Consistency is an important ingredient for success in UX Writing. It means using the same words, labels, and phrasing for the same concepts, actions, and interactive elements throughout a product. If a feature is called "Workspace" on one screen and "Project" on another, users lose trust and orientation.

    Example: If the navigation says "Team Members", the settings page should not say "Collaborators" or "Users" — pick one term and use it everywhere.

    Note: Consistency is the primary reason every product needs a style guide. It reduces cognitive load and builds user trust over time.

    See also: Style Guide, Mental Model, String

  • Content Design is a discipline closely related to UX Writing that uses evidence and user research to create content that helps people get what they need, in the simplest and most effective way. Content designers make structural decisions about what content exists, where it lives, and what format it takes — not just how it is written. The term was popularized by Sarah Richards.

    Example: A content designer working on a government form would not just rewrite the instructions — they would question whether certain fields are necessary at all, and whether a form is even the right format.

    Note: Content design and UX Writing are closely related and often used interchangeably, but content design typically implies a more strategic and research-led scope.

    See also: UX Writing, Content Strategy, Content Ops

  • Content Intelligence is the use of data, analytics, and AI tools to inform UX Writing decisions — understanding what copy performs well, why, and for whom. For UX Writers, it means using A/B test results, heatmaps, and user research to write more effective copy, rather than relying on intuition alone.

    Example: A content intelligence analysis reveals that users drop off at the password reset step because the error message is ambiguous. Rewriting it based on this data is content intelligence in action.

    Note: As AI-generated content becomes more common, content intelligence is increasingly used to differentiate high-quality, human-centered UX Writing from generic output.

    See also: Content Strategy, Content Ops, Copy Audit

  • Content Ops refers to the systems, processes, tools, and workflows that enable UX Writing teams to work efficiently and consistently at scale. It covers how copy is created, reviewed, approved, published, maintained, and retired — and who is responsible for each step.

    Example: A Content Ops process might define who reviews UX Writing before launch, how strings are handed off to developers, where the style guide lives, and how translation requests are submitted.

    Note: As product teams scale, Content Ops becomes critical for preventing inconsistency and communication breakdown between UX Writing, design, engineering, and localization.

    See also: Content Strategy, Style Guide, Localization, String

  • Content Orchestration is the strategic coordination of all communication activities across writing disciplines and content functions — with the goal of aligning the customer experience across every touchpoint to create a coherent, end-to-end product and brand experience.

    Content Orchestration spans the full range of writing disciplines — from UX Writing, Copywriting, Content Writing, and Technical Writing — and includes activities such as voice and tone design, content-related research, conceptualization, brand storytelling, and analytics. Rather than managing these disciplines in isolation, Content Orchestration ensures they work together toward a unified language experience.

    Example: A team practicing Content Orchestration ensures that the brand promise communicated in a marketing campaign is reflected in the product's onboarding flow, its error messages, its help documentation, and its transactional emails — creating a seamless experience from first contact to everyday use.

    Note: Content Orchestration is closely related to Strategic Product Writing, which describes the practitioner-level discipline of thinking and working orchestratively across all product language touchpoints. As AI tools take over more execution-level content tasks, Content Orchestration becomes an increasingly critical human competency.

    See also: Content Strategy, Content Ops, UX Writing, Copywriting, Technical Writing, Voice, Tone, Brand Storytelling

  • Content Strategy Content strategy is the planning, creation, governance, and management of content across all channels and touchpoints. For UX Writers and content designers, it answers: what content does our product need, who creates it, how does it stay up to date, and how does it serve both business and user goals?

    Example: A content strategy for a SaaS onboarding flow defines what messages users see at each step, what format they take, how they adapt for different user types, and how their effectiveness is measured.

    Note: Content strategy is broader than UX Writing but depends on strong UX Writing to execute. Kristina Halvorson's Content Strategy for the Web is a foundational reference.

    See also: Content Design, Content Ops, Content Intelligence

  • Conversation Design is a discipline within UX Writing focused on designing natural, human-centered dialogue flows for conversational products — including chatbots, voice assistants, and AI tools. Conversation designers write the words a system says, but also map out the full flow: what happens when a user deviates, fails, or needs help.

    Example: A conversation designer working on a banking chatbot writes not just the greeting ("Hi, how can I help?") but also the fallback ("Sorry, I didn't catch that — would you like to speak to a person?") and the handoff copy.

    Note: As AI-powered products become mainstream, conversation design is one of the fastest-growing areas within UX Writing.

    See also: UX Writing, Voice, Tone, Microcopy

  • A copy audit is a systematic review of all UX Writing within a product — assessing it for consistency, clarity, tone, accuracy, accessibility, and alignment with brand guidelines. Copy audits reveal where language has drifted, where copy is missing, and where the user experience is being hurt by poor writing.

    Example: During a copy audit, a team discovers that "Delete", "Remove", and "Clear" are used for the same action across different screens — a consistency issue that directly harms the user experience.

    Note: A copy audit is typically the first step before a rebrand, redesign, or style guide update. It is also a useful tool for onboarding new UX Writers onto an existing product.

    See also: Content Strategy, Consistency, Style Guide

  • Copywriting is the practice of writing text — traditionally for advertising, marketing, and sales — with the goal of persuading an audience to take action. In the context of UX Writing, the two disciplines are related but distinct: copywriting prioritizes persuasion and brand narrative, while UX Writing prioritizes clarity, usability, and task completion.

    Example: A landing page headline ("Transform how your team works") is copywriting. The button label that follows ("Start free trial — no credit card required") sits at the intersection of copywriting and UX Writing.

    Note: Many UX Writers come from a copywriting background. The key shift is moving from persuading users to buy something, to helping users achieve their goals once they're inside a product.

    See also: UX Writing, Content Design, CTA, Microcopy

  • CTA (Call to Action) In UX Writing, a CTA is a word, phrase, or button label that prompts users to take a specific action. Effective CTAs use a verb + noun structure and are specific about the outcome. A strong CTA answers: "What happens when I click this?" Weak CTAs — like "Submit" or "Click here" — give no information about the outcome and are a common UX Writing mistake.

    Example: "Start free trial" is stronger than "Sign up". "Download the guide" is stronger than "Click here". "Save changes" is stronger than "OK".

    Note: CTAs are among the highest-impact UX Writing decisions. A/B testing CTA copy is one of the most common and measurable UX Writing experiments.

    See also: Microcopy, Affordance, Copywriting, Friction

D

  • A destructive action warning is a UX Writing pattern used before irreversible or high-stakes actions — such as deleting data or permanently closing an account — to ensure the user acts with full awareness and deliberate intent. The copy must clearly name the action, state its consequences, and offer a way to cancel.

    Example: "Delete workspace? All projects, files, and members will be permanently removed. This cannot be undone." — with buttons "Cancel" and "Delete workspace", not "No" and "Yes".

    Note: The CTA buttons should echo the action ("Delete workspace", not just "Delete") so users cannot click through without reading. Avoid vague phrasing like "Are you sure?"

    See also: Confirmation, Friction, Modal

E

  • An empty state is a UX Writing opportunity that occurs when a section of a product has no content to display — because a user is new, a search returned no results, or all tasks have been completed. Good empty state copy explains why the space is empty, communicates the value of filling it, and provides a clear path to first action.

    Example: Instead of a blank screen, a project management app shows: "No projects yet. Create your first project to get your team moving." — with a "New project" button.

    Note: Empty states are one of the most overlooked opportunities in UX Writing. A well-written empty state can significantly improve activation rates for new users.

    See also: Onboarding, Loading State, User Journey, Happy Path

F

  • Fold (Above the Fold / Below the Fold) The fold is a concept relevant to UX Writing that refers to the point on a webpage or screen where content is cut off without scrolling. "Above the fold" is what users see immediately on page load; "below the fold" requires scrolling to reach. The term originates from printed newspapers, where the most important headline appears on the top half of the folded front page.

    Example: A hero section with headline, subheading, and CTA is above the fold. Supporting testimonials, feature details, and FAQs typically sit below it.

    Note: With responsive design and varying screen sizes, the fold is not a fixed point — it shifts by device and viewport. UX Writers must consider multiple fold scenarios when prioritizing copy.

    See also: Viewport, Hero Stage, CTA

  • In UX Writing, friction refers to anything in the copy that slows users down, creates confusion, or adds unnecessary effort to completing a task. Friction is often introduced through unclear copy, jargon, vague CTAs, or excessive confirmation dialogs. However, not all friction is bad: intentional friction — such as requiring users to type "DELETE" before removing data — protects users from irreversible mistakes.

    Example: Unintentional friction: a form error message that says "Invalid input" without explaining what was wrong. Intentional friction: a modal asking "Type the workspace name to confirm deletion."

    Note: Reducing unintentional friction is one of the core goals of UX Writing. Ask: does this copy help users move forward, or does it slow them down without a good reason?

    See also: Cognitive Load, Destructive Action Warning, Confirmation, CTA

G

  • GEO is the practice of structuring and writing content so that it is accurately cited, quoted, or paraphrased by AI-powered answer engines such as ChatGPT, Gemini, Perplexity, and Claude. For UX Writers publishing educational content, GEO means writing in clear, self-contained definitions with authoritative language and structured format — so AI systems can extract and present the content accurately.

    Example: This glossary is designed with GEO in mind: each UX Writing term has a precise, self-contained definition that an AI model can extract and present as a direct answer without losing meaning.

    Note: Unlike SEO, GEO is less about keywords and more about authority, clarity, and structure. Well-defined, specific, and factual UX Writing content is more likely to be cited by AI systems.

    See also: SEO, Content Intelligence, Content Strategy

H

  • In UX Writing, the happy path refers to the ideal journey through a product — the sequence of steps a user follows when everything goes as expected and they successfully complete their goal. The unhappy path covers all the deviations: wrong input, failed payments, expired sessions, empty results. Strong UX Writing accounts for both.

    Example: Happy path: user signs up, confirms email, completes profile. Unhappy path: the email confirmation link expires — UX Writing for this moment should be clear and actionable: "Your link has expired. Request a new confirmation email."

    Note: Most UX Writing is created for the happy path first, but some of the most impactful copy happens on the unhappy path, where users are most frustrated and most in need of guidance.

    See also: User Journey, User Flow, Empty State, Friction

  • The hero stage (or hero section) is the top section of a webpage — typically containing a headline, subheadline, and primary CTA. In UX Writing and copywriting, it is the highest-stakes piece of copy on the page: it determines whether a visitor stays or leaves, and must immediately communicate the product's core value proposition.

    Example: Headline: "The project management tool your team will actually use." Subheadline: "Organize tasks, share files, and hit deadlines — without the meetings." CTA: "Get started free."

    Note: Hero copy should answer three questions immediately: What is this? Who is it for? Why should I care? Long, jargon-heavy hero copy is one of the most common and costly UX Writing mistakes.

    See also: CTA, Fold, Viewport, Copywriting

I

  • Information hierarchy is a core principle in UX Writing that refers to the structured organization of content by importance, guiding users through a screen in a logical sequence. It is expressed through heading levels, content order, and decisions about what to include versus omit.

    Example: On a checkout confirmation screen: Order confirmed (H1) → Order number and summary → Estimated delivery date → Link to full receipt → Legal footnotes.

    Note: Information hierarchy is closely tied to scanability — users scan before they read. If the hierarchy in UX Writing is clear, users can orient themselves in seconds.

    See also: Scanability, Progressive Disclosure, Cognitive Load, Content Design

  • Internationalization (i18n) Internationalization — abbreviated as i18n — is the process of preparing a product so its UX Writing can be adapted for different languages, regions, and cultures without requiring engineering changes for each market. For UX Writers, i18n means writing copy that is easy to translate and localize: avoiding idioms, culturally specific references, and strings that are difficult to translate without context.

    Example: Writing "Your {plan_name} subscription renews on {date}" instead of hardcoding "Your Pro subscription renews on March 1" makes the UX Writing ready for internationalization.

    Note: Internationalization (i18n) is the technical foundation; Localization (l10n) is the cultural adaptation built on top of it. Translation is the linguistic act that happens within localization.

    See also: Localization, Translation, String, Content Ops

L

  • A loading state is a UX Writing touchpoint that occurs while the system processes a request or retrieves data. Effective loading state copy reduces perceived wait time and sets clear expectations about what is happening — users who receive no feedback during loading may assume the product has crashed.

    Example: "Uploading your file… (34%)" is more reassuring than a spinning wheel with no text. "Analyzing your data — this usually takes about 10 seconds." manages expectations explicitly.

    Note: Loading state UX Writing is especially important for processes that take longer than 3 seconds. Research suggests users begin to feel impatient after about 3 seconds without feedback.

    See also: Empty State, User Experience, Microcopy

  • Localization — abbreviated as l10n — is the process of adapting UX Writing for a specific region, language, and cultural context. It goes far beyond translation: localization includes adjusting date and time formats, currencies, units of measurement, legal copy, tone, and culturally specific references.

    Example: Localizing for the UK means changing "soccer" to "football", date formats from MM/DD to DD/MM, and currency from $ to £ — but also reconsidering whether idioms like "ballpark figure" translate meaningfully.

    Note: Localization (l10n) is the cultural and contextual adaptation of UX Writing for a specific market. Internationalization (i18n) is the technical preparation that makes localization possible. Translation is the linguistic conversion — necessary but not sufficient for effective localization.

    See also: Internationalization, Translation, String, Content Ops

M

  • A mental model is a user's internal representation of how a product works, built from prior experience and learned behavior. In UX Writing, aligning copy with users' mental models means using the vocabulary they already know — not the internal terminology of the development team or company.

    Example: Users expect "Inbox", not "Message Repository". They expect "Settings", not "Configuration Panel". Deviating from established mental models creates unnecessary friction and is a common UX Writing pitfall.

    Note: Mental models are one of the strongest arguments for user research in UX Writing. Before choosing terminology, it is worth testing what words users actually use to describe a feature.

    See also: Consistency, Cognitive Load, User Persona, Affordance

  • Microcopy is the small but high-impact copy that UX Writers create for critical moments in a product — button labels, error messages, helper text, placeholder copy, confirmation messages, and tooltips. Despite its short length, microcopy has an outsized effect on user trust, conversion rates, and task completion. A single well-chosen word can reduce anxiety, increase confidence, or prevent an error.

    Example: Adding "No credit card required" beneath a "Start free trial" CTA is microcopy that directly addresses user hesitation and increases conversion. Changing "Error" to "Check your email address — it looks like it's missing an @" reduces support tickets.

    Note: Microcopy is often the last thing written on a project but has some of the highest measurable impact on user behavior — making it one of the most important skills in UX Writing.

    See also: CTA, Placeholder Text, Tooltip, Affordance

  • A modal is an overlay window used in UX Writing to present confirmations, alerts, or data entry forms on top of the current page, blocking interaction with the content behind it until the user responds. Effective modal UX Writing requires a clear, specific headline, concise body text, and CTA labels that name the action.

    Example: Headline: "Remove team member?" Body: "They will immediately lose access to all projects and files." CTAs: "Cancel" and "Remove member" — not "No" and "Yes".

    Note: Modals should be used sparingly — they interrupt the user's flow. Overuse leads to modal blindness, where users dismiss dialogs without reading the UX Writing inside them.

    See also: Overlay, Confirmation, Destructive Action Warning, Friction

O

  • Onboarding is the process of guiding new users from their first interaction with a product to their first meaningful moment of value — and UX Writing plays a central role in making it work. Onboarding copy includes welcome messages, setup wizards, tooltips, checklists, empty states, and email sequences, all designed to reduce confusion and help users build confidence quickly.

    Example: A SaaS onboarding checklist: "Set up your profile ✓ → Connect your first integration → Invite a teammate → Create your first report." Each step has a short description and a direct action link.

    Note: The goal of onboarding UX Writing is not to explain every feature — it is to help users reach their first "aha moment" as quickly as possible. Shorter, focused copy consistently outperforms comprehensive feature tours.

    See also: Empty State, User Journey, User Flow, Happy Path

  • An overlay is a layer that appears on top of existing content in a product, partially or fully obscuring the page behind it. Overlays include modals, drawers, bottom sheets, lightboxes, and cookie banners. In UX Writing, overlay copy must be immediately scannable — overlays often interrupt users mid-task and demand instant clarity.

    Example: A cookie consent overlay: "We use cookies to improve your experience. You can accept all, manage preferences, or decline non-essential cookies." — with specific, clearly labeled action buttons.

    Note: Vague or manipulative overlay copy ("Yes, I want a better experience / No, I prefer a worse one") is a dark pattern. UX Writing for overlays should keep choices honest and labels specific.

    See also: Modal, Friction, Microcopy

P

  • Plain language is a UX Writing principle that makes copy clear, direct, and immediately understandable to the target audience — on first read. It means using short sentences, active voice, common words, and a logical structure. In UX Writing, plain language is not about dumbing content down — it is about respecting users' time and reducing cognitive load.

    Example: "We were unable to process your payment due to insufficient funds." becomes "Your payment didn't go through — your account may not have enough funds. Please try a different card or check your balance."

    Note: Plain language is legally required in some contexts, such as government communications and financial disclosures. Even expert audiences benefit from plain language UX Writing.

    See also: Cognitive Load, A11y, Microcopy, Scanability

  • Text Placeholder text is the greyed-out hint copy that UX Writers place inside a form field before a user types. It should never replace a proper visible field label — it disappears the moment a user starts typing, leaving them without context if they forget what was asked.

    Example: A field labeled "Work email" (the label) with placeholder text "name@company.com" (the hint). The label stays visible; the placeholder disappears on input.

    Note: Placeholder text in UX Writing should contain only format hints or examples — never instructions or important information. All critical guidance belongs in the label or helper text.

    See also: Microcopy, Cognitive Load

  • Progressive disclosure is a UX Writing strategy that presents only the information relevant to the user's current step — revealing additional complexity only when needed. It prevents cognitive overload by layering content: show the essentials first, offer more detail on demand.

    Example: A settings page shows core options by default with an "Advanced" toggle for additional settings. A product description shows two sentences with a "Read more" link to expand.

    Note: Progressive disclosure is especially valuable in UX Writing for onboarding, complex forms, and settings pages. The goal is to lower the barrier to entry while still making full functionality accessible.

    See also: Cognitive Load, Information Hierarchy, Tooltip, Scanability

S

  • Scanability refers to how easily a user can quickly assess the content of a page or screen without reading every word — and it is a core concern in UX Writing. Users scan before they read: they look for headings, bold text, bullet points, and short paragraphs to orient themselves. UX Writers improve scanability by using clear headings, chunking content into short sections, and removing filler words.

    Example: A 500-word help article becomes scannable when it uses a clear H1, three H2 subheadings, short paragraphs of 2–3 sentences, and a bulleted list of key steps.

    Note: Studies by the Nielsen Norman Group show that users read only about 20–28% of text on a webpage. Writing for scanability is writing for how people actually behave — and it is one of the most practical skills in UX Writing.

    See also: Information Hierarchy, Plain Language, Cognitive Load, Progressive Disclosure

  • SEO is the practice of structuring and writing content so that it ranks highly in search engine results pages for relevant queries. For UX Writers working on web products, SEO intersects with UX Writing in page titles, meta descriptions, headings, and help center articles. The challenge is balancing keyword optimization with the clarity and usability that UX Writing demands.

    Example: A help center article titled "How to reset your password in [Product]" is both user-friendly and search-optimized. A title like "Password Reset Functionality" is neither.

    Note: SEO targets traditional search engines and their ranking algorithms. GEO (Generative Engine Optimization) is the emerging parallel practice for AI-powered answer engines. Both matter for UX Writers publishing educational content.

    See also: GEO, Content Strategy, Alt Text

  • In UX Writing, a string is a piece of copy stored in a content management system or codebase — identified by a unique key. Strings are the units in which UX Writing is managed, handed off to developers, and sent for translation. Understanding how strings work is essential for UX Writers working in cross-functional teams and internationalized products.

    Example: The string key "button.save.label" might have the value "Save changes" in English, "Änderungen speichern" in German, and "Guardar cambios" in Spanish — managed independently in a translation system.

    Note: UX Writers who understand string structure can write copy that is more translation-ready and less likely to cause engineering headaches.

    See also: Localization, Internationalization, Content Ops, Consistency

  • A style guide is a documented set of rules, conventions, and examples that govern how UX Writing is produced across a product. It typically covers voice and tone, terminology, grammar conventions, capitalization rules, and guidance for specific patterns like error messages and CTAs. A style guide is the primary tool for achieving consistency in UX Writing across teams and over time.

    Example: A style guide entry for error messages might specify: always use active voice, name the specific problem, and provide a solution. Example: "Your session has expired. Sign in again to continue." — not "Error 401: Unauthorized."

    Note: A style guide for UX Writing is only useful if it is maintained, accessible, and actually used. Many teams have style guides that are out of date or unknown to new team members — Content Ops helps prevent this.

    See also: Consistency, Copy Audit, Content Ops, Voice, Tone

T

  • In UX Writing, tone is the emotional inflection applied to a brand's consistent voice, adapted to suit the user's context and the nature of the interaction. While voice stays consistent — it is the product's personality — tone shifts: copy can be warm and celebratory when a user succeeds, and calm and reassuring when something goes wrong.

    Example: Success state: "You're all set! Your account is ready to go." Error state: "Something went wrong on our end. We're working on it — please try again in a moment."

    Note: Voice is who you are; tone is how you sound in a given moment. A good voice and tone framework gives UX Writers clear guidance on how to modulate copy across different emotional scenarios.

    See also: Voice, Style Guide, Microcopy

  • A tooltip is a small pop-up text element used in UX Writing to provide additional context about a product feature without permanently occupying screen space. It appears on hover or tap and is best used for explaining abbreviations, technical terms, or non-obvious features. Tooltip copy should be brief — ideally one to two sentences — and written for users who need a hint, not a full tutorial.

    Example: An information icon next to a field labeled "MRR" shows a tooltip: "Monthly Recurring Revenue — the total value of all active subscriptions normalized to a monthly amount."

    Note: Tooltips are invisible until triggered, so they should not contain critical information that all users need to see. For essential context, use visible helper text instead.

    See also: Microcopy, Progressive Disclosure, Placeholder Text, A11y

  • Translation is the process of converting UX Writing from one language to another, preserving meaning, intent, and — ideally — tone. For UX Writers, translation readiness means writing source copy that is unambiguous, context-rich, and free of idioms or wordplay that do not translate.

    Example: The English CTA "Let's go!" may translate awkwardly in some languages. A more translation-friendly UX Writing choice is "Get started" — direct, clear, and culturally neutral.

    Note: Translation should not be confused with Localization (l10n), which adapts UX Writing for a specific cultural context, or with Internationalization (i18n), which is the technical preparation that enables both. Translation is the linguistic component within the broader localization process.

    See also: Localization, Internationalization, String, Content Ops

  • Truncation is the practice of shortening UX Writing copy that exceeds available space, typically indicated by an ellipsis (…). It is used when product constraints prevent displaying the full text — in navigation labels, notification previews, card titles, or table cells. UX Writers need to ensure that truncation does not cut off critical information or create ambiguity.

    Example: A notification preview reads: "Sarah left a comment on Q4 Roadmap Prese…" — the document title is truncated. The full title should be accessible on hover or within the notification detail.

    Note: Truncation should be a last resort in UX Writing. When possible, write copy that fits within the available space. When unavoidable, ensure the full content is accessible through another interaction.

    See also: Scanability, Tooltip, ARIA Label, A11y

U

  • User experience (UX) refers to the overall quality of a person's interaction with a product or service — encompassing usability, accessibility, emotional response, and the degree to which it helps users achieve their goals. UX Writing is a core component of user experience: the words in a product are part of the experience, not an afterthought.

    Example: A user experience can be excellent even if the visual design is simple — if the product is fast, the UX Writing is clear, errors are handled gracefully, and the user achieves their goal without frustration.

    Note: UX is often conflated with UI (User Interface) design, but UX is broader — it encompasses the full journey, including pre- and post-product touchpoints like ads, emails, and customer support.

    See also: UX Writing, User Journey, User Flow, User Persona

  • A user flow is the path a user takes through a product to complete a specific task — from entry point to goal completion. In UX Writing, user flows define which copy is needed at each step, including all branching paths and error states. Unlike a user journey, a user flow is a concrete, task-specific sequence of screens and decisions.

    Example: User flow for password reset: Click "Forgot password" → Enter email → Receive confirmation message → Click email link → Enter new password → See success confirmation. Each step requires specific UX Writing.

    Note: User flows are typically visualized as flowcharts during design. UX Writers should be involved in flow mapping to ensure copy is planned at the structural level, not added after the product is built.

    See also: User Journey, Happy Path, Onboarding, User Experience

  • A user journey maps the full experience of a person interacting with a product or service — from first encounter to goal completion and beyond. It captures touchpoints, emotional states, pain points, and opportunities across multiple channels. For UX Writers, the user journey provides context for every piece of copy: who is reading this, what do they know, and how are they feeling right now?

    Example: A user journey for a health app might include: sees ad → visits landing page → signs up → completes onboarding → logs first workout → receives a weekly summary email → upgrades to premium. Each touchpoint requires UX Writing decisions.

    Note: User journeys are different from user flows: a journey maps the broader experience and emotional arc; a flow maps the specific steps within a single task.

    See also: User Flow, User Persona, Onboarding, Happy Path

  • A user persona is a research-based profile that represents a key segment of a product's users — describing their goals, behaviors, needs, frustrations, and context. In UX Writing, personas help calibrate vocabulary, tone, level of detail, and the assumptions that can safely be made in copy.

    Example: Persona "Alex, 34, Freelance Designer": uses the product primarily on mobile, has low tolerance for onboarding friction, expects a professional tone, and switches off when UX Writing feels too corporate.

    Note: Personas are only useful if they are based on real user research, not internal assumptions. A persona built from data produces better UX Writing than one built from intuition.

    See also: User Journey, Mental Model, Tone, Content Strategy

  • UX Writing is the discipline of crafting all copy within a digital product — buttons, labels, error messages, onboarding flows, tooltips, notifications, empty states, and more — to create experiences that are clear, usable, and human. UX Writers work at the intersection of language, design, psychology, and research. The goal of UX Writing is not to make things sound good, but to help users understand, navigate, and succeed within a product.

    Example: Every word a user reads while using an app is UX Writing: from "Sign in" on the login screen to "Your file was deleted and cannot be recovered" in an error state — and every moment in between.

    Note: UX Writing is sometimes called product writing, interface writing, or content design. While the terms differ slightly in scope and emphasis, they all describe the same core practice: writing for digital product experiences.

    See also: Content Design, Microcopy, Content Strategy, Voice, Tone

V

  • The viewport is the visible area of a screen that a user can see without scrolling — defined by their device, screen size, and browser window. Understanding the viewport is essential for UX Writing because it determines which copy is immediately visible and which requires scrolling to find. On mobile, the viewport is much smaller than on desktop, demanding more concise, prioritized copy.

    Example: A hero section designed for a wide desktop viewport may show headline, subheadline, and CTA above the fold. On a mobile viewport, the subheadline may be pushed below the fold — requiring the UX Writing in the headline to work harder on its own.

    Note: UX Writers should review their copy across multiple viewport sizes. What reads clearly on a wide screen may feel overwhelming or be cut off on mobile.

    See also: Fold, Hero Stage, Scanability

  • In UX Writing, voice is the consistent personality and character expressed across all of a product's written communication. It stays stable regardless of context and answers the question: "Who is this product?" Tone, by contrast, is how that voice adapts to different situations and user emotions.

    Example: Slack's voice is playful and human. Stripe's is precise and trustworthy. Both voices remain consistent whether the UX Writing is confirming a message or displaying a critical error.

    Note: Voice is established at the brand or product level and documented in a style guide or voice and tone framework. It should be distinctive enough to differentiate the product, but not so extreme that it alienates users in serious moments.

    See also: Tone, Style Guide, Content Design