Skip to content
Design Academy My progress

Stage 12 · Lesson 5 of 12

UX writing and content design

Voice, microcopy and content-first design.

  • Advanced
  • 1 h
  • 3 check questions
  • Exercise: 45 min

By the end of this lesson you can

  • Define a voice and tone for a product.
  • Write clear microcopy for buttons, errors and empty states.
  • Apply content-first design.

The idea

UX writing and content design treat words as a core part of the interface. Often the best design improvement is a clearer sentence.

Voice and tone

Voice is the product's consistent personality (for example "clear, warm, direct"). Tone adapts to context: celebratory after success, calm and helpful after an error.

Microcopy

  • Buttons: say what happens ("Send payment", not "Submit").
  • Errors: explain what went wrong and how to fix it, without blame.
  • Empty states: explain what will appear and how to start.
  • Confirmations: state what happened and what comes next.

Content-first design

Start with the content people need, then design the layout around it. Use real content in prototypes instead of placeholder text, which hides problems.

Plain language

Use short sentences, common words and active voice. Front-load key information. Test whether people understand the words.

Why it matters in real projects

Words guide people through every interaction. Unclear labels and errors cause confusion, support calls and abandonment, while clear writing makes products feel easy and trustworthy. Plain language also helps people with cognitive disabilities, those reading in a second language and everyone in a hurry.

A realistic example

Error before: "Invalid input. Error code 4012."

After: "Enter your date of birth in the format DD/MM/YYYY, for example 07/03/1990."

Empty state before: "No data." After: "You have no saved addresses yet. Add one to check out faster next time." with an "Add address" button.

Step by step

  1. Define voice

    Choose three voice qualities with dos and don'ts.

  2. Map tone

    Describe tone for success, errors and warnings.

  3. Audit microcopy

    Review buttons, errors, empty states and confirmations.

  4. Rewrite

    Make each clear, specific and helpful.

  5. Use real content

    Replace placeholder text in prototypes.

  6. Test comprehension

    Ask users to explain key messages.

Common mistakes

  • Mistake Generic buttons like "Submit".

    Instead Say what will happen.

  • Mistake Blaming error messages.

    Instead Explain how to fix the problem.

  • Mistake Designing with placeholder text.

    Instead Use real content early.

Check your understanding

Choose an answer, then check it. There is an explanation either way.

Question 1 of 3Which button label is best?
Show answer

Send payment. Say what happens.

Question 2 of 3What is the difference between voice and tone?
Show answer

Voice is consistent; tone adapts to context. Personality versus mood.

Question 3 of 3Why avoid placeholder text?
Show answer

It hides content problems. Real content reveals issues.

Practice exercise

Exercise · about 45 min

Microcopy rewrite

Rewrite microcopy in a product.

Steps

  1. Define three voice qualities.
  2. Collect ten pieces of microcopy.
  3. Rewrite each using plain language.
  4. Test two rewrites with users.

Deliverable

A before-and-after microcopy table.

Self-assessment

Tick each item when it is true of your exercise. Be honest; this is for you.

4 items

Summary

  • Words are part of the interface.
  • Define voice and adapt tone.
  • Write clear, helpful microcopy.
  • Design content first and test it.

Further reading

Third-party sources, chosen for reliability. They open in a new tab.

Your notes

Marking complete updates your course and roadmap progress.

Back to Advanced and specialised topics Roadmap

PreviousDesign systems at scale Next lessonService design