<?xml version="1.0" encoding="utf-8"?>

UX microcopy or UX copy includes all the little texts accompanying UI elements that help users navigate apps and websites. Some examples are button labels that tell users what will happen when they press it or error messages that explain what's gone wrong and how users can solve it. Writing great microcopy is trickier than it seems. It should be concise and straight to the point, explain what is needed and why, and, of course, respect users.

Big companies like Google and Spotify have specific UX writing positions. In smaller teams, this job usually falls on designers or developers. This can sometimes lead to confusing writing, like in the case of the infamous "Task failed successfully" Windows XP error message. Whether you're a UX writer, a designer, or a developer struggling to find the right words, this lesson will help you understand and improve your microcopy and, in turn, your user experience.

Exercise #1

What’s microcopy

What’s microcopy

Microcopy is those tiny bits of text you see near buttons, in forms, or in instructions on websites or apps, helping users know what to do next. Imagine trying to fill out an online form and not knowing what information to put in each box. Microcopy is there to assist you by providing hints like "Enter your email address here."

These small phrases are more critical than they may appear. They guide users and can even create a more pleasant experience. If done well, microcopy speaks to users in a conversational tone, making them feel comfortable and understood. It helps to remove confusion and encourages them to take the desired action, whether that's signing up for a newsletter, making a purchase, or sharing information.

Exercise #2

Avoid vague commands

Avoid vague commands Bad Practice
Avoid vague commands Best Practice

The clarity of commands is vital in guiding users effectively. When users encounter vague or confusing language, they are often deterred from taking action. Complex words, technical jargon, or niche slang can mystify, especially for non-native speakers, leading them to abandon their task.

The goal is to communicate what users should do in transparent, unambiguous language. Avoid words that might have unclear meanings or that might require extra effort to understand. A helpful trick to ensure clarity is to read the command out loud. If it doesn't sound natural or rolls off the tongue awkwardly, it's a sign that it might need simplification.

Exercise #3

Avoid generic commands

Avoid generic commands Bad Practice
Avoid generic commands Best Practice

Generic commands such as "OK," "Yes," "Cancel," "Submit," and the like can often leave users in the dark about the action they're about to take. While these terms may seem straightforward, they lack context and specificity, leading to potential confusion.

Consider whether users would understand the command without reading the dialog's title or additional description. Will they know what "OK" or "Submit" really means in that specific situation? If the answer is no, it's a sign that the command is too generic.

To enhance user understanding, focus on making commands as descriptive and context-specific as possible. Instead of just "Submit," a button might say "Submit Your Application" or "Submit Payment." By including a bit more information, you clarify the action for users, reducing uncertainty.

Exercise #4

Avoid double negatives

Avoid double negatives Bad Practice
Avoid double negatives Best Practice

Double negatives occur when two negative words appear in the same sentence. Using them in microcopy can create confusion and erode trust. For instance, a prompt like "Don't you want to avoid not receiving our newsletter?" muddles the intended action. Will confirming unsubscribe users or not? Such ambiguity can frustrate users and create suspicion that the interface is misleading them.

To foster transparency and trust, it's essential to use clear, positive language. Instead of employing double negatives, frame your statements or questions in a direct, straightforward manner. A question like "Do you want to continue receiving our newsletter?" is much clearer and encourages a more transparent interaction with users.

Exercise #5

Avoid excessive politeness

Avoid excessive politeness Bad Practice
Avoid excessive politeness Best Practice

In the world of UX copy, brevity and clarity are key. While maintaining a respectful and friendly tone is essential, excessive politeness can become an obstacle to smooth user interaction. Users typically want to get to the point quickly, and overusing terms like "please" and "thank you" can sound unnatural, insincere, and even annoying.

Consider a button that says "Please click here to proceed, thank you." While polite, it's wordy and slows down the user's understanding. A more streamlined version like "Click to Proceed" conveys the same message without unnecessary embellishments.

Remember, every word in UX copy should serve a purpose, and excessive politeness can clutter the interface and hinder efficiency.

Exercise #6

Avoid overusing a brand’s name

Avoid overusing a brand’s name Bad Practice
Avoid overusing a brand’s name Best Practice

In the context of UX design, it's crucial to prioritize user understanding and comfort. While branding is an essential part of marketing, its overuse in UX copy can come across as self-promotional and even confusing.

Imagine users navigating a mobile app. If every button and prompt includes the brand name, it may give the impression of showing off, rather than guiding users effectively. For example, a button labeled "Click here to explore BrandX's features" may cause users to pause and ponder, rather than smoothly progress.

The users are usually aware of the product they're using; they don't need constant reminders. Instead, clear and concise language without the distraction of branding helps them focus on the task at hand.

While branding has its place in marketing materials, UX copy should focus on usability and clarity.

Exercise #7

Use active voice

Use active voice Bad Practice
Use active voice Best Practice

While passive voice has its place in language, active voice often creates a more direct and engaging connection with the reader. Consider the two statements: “You did a great job,” and “A great job was done by you.” Both convey the same message, but the first, written in active voice, is much more natural and easier to read.

Active voice places the subject at the beginning of the sentence, leading the action, whereas passive voice emphasizes the object or the result of the action. In UX copy, the active voice helps create a sense of immediacy and involvement, enhancing the user’s connection with the content.

When you craft instructions, notifications, or any other user-facing text, try to frame them in active voice. It fosters clearer communication and reflects a more conversational tone that resonates with users.

Exercise #8

Use concise language

Use concise language Bad Practice
Use concise language Best Practice

While flowery or poetic language may have its place in literature, it can lead to confusion and frustration in a user interface. Resist the temptation to embellish or overcomplicate your text. Forget about traditional grammar rules that emphasize complete sentences and instead focus on small, scannable phrases. You might even consider omitting articles and prepositions where they don't add clarity.

Compare these two instructions: “Please click on the button to continue” versus “Click to continue.” Both provide the same directive, but the latter is more concise and user-friendly.

Users are often navigating interfaces quickly, seeking information or trying to complete a task. Long paragraphs and complex sentences can overwhelm them, leading to disengagement.

Exercise #9

Use numerals for numbers

Use numerals for numbers Bad Practice
Use numerals for numbers Best Practice

Numbers often play a vital role in UX copy, whether they're representing prices, dates, quantities, or other key information. When including numbers in your text, it's generally best to use numerals rather than spelling out the words for numbers. This approach has several advantages:

  • Numerals are more scannable. They stand out in a block of text, grabbing the reader's attention, and allowing for quick and easy comprehension.
  • Numerals save space. That’s true both in terms of characters and visual layout, which can be especially valuable in confined UI elements or mobile interfaces.
  • Numerals reduce the chance of typos. They can even save time during the development phase of your project. Developers and translators may find it simpler to work with standardized numerical representations.
Exercise #10

Use a consistent case

Use a consistent case Bad Practice
Use a consistent case Best Practice

Attention to detail can enhance user experience, and text case consistency in microcopy is key. Here's how to choose the right case for different scenarios:

  • Title case: Commonly used for main call-to-action buttons or key interactive elements that guide users, like "Add to Cart" or "View Profile."
  • Sentence case: Suitable for subheadings within forms, tooltips, secondary buttons, or instructional text, e.g., "Sign in with your email."
  • All caps: Might appear in image captions or certain specialized contexts where text needs to stand out. Use sparingly.
  • Lowercase: Rarely used in microcopy but may be part of specific branding or design themes.

By selecting a text case and applying it consistently across all similar microcopy elements, you prevent a disjointed appearance and contribute to a seamless user experience.

Complete this lesson and move one step closer to your course certificate