Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Information Architecture & UX Writing/Clarity Over Cleverness: Interface Copy & Microcopy
Level 4 · UX Writing & Actionable Microcopy

Clarity Over Cleverness: Interface Copy & Microcopy

10 min read
3 exercises
250 XP
Start lesson

Ready to test what you learned?

Complete the lesson quiz and earn 250 XP.

Start quiz

Topics in this lesson

The Three Principles of UX WritingButton and CTA Labeling: Verb + Specific NounEmpty States: Turning Dead Ends into Onboarding

From Course

📘
Information Architecture & UX WritingBeginner · 5 lessons
Clarity Over Cleverness: Interface Copy & Microcopy

Lesson

Clarity Over Cleverness: Interface Copy & Microcopy

The Three Principles of UX WritingButton and CTA Labeling: Verb + Specific NounEmpty States: Turning Dead Ends into Onboarding
Start lesson
Complete lesson and earn 250 PX
Exercise #1

The Three Principles of UX Writing

UX writing is not marketing copy. Marketing seeks to persuade and attract attention; UX writing seeks to guide action, reduce cognitive load, and eliminate ambiguity.

  • Clear: Unambiguous vocabulary written in plain language. Eliminate internal company jargon and technical abstractions.
  • Concise: Scannable text stripped of filler words. Users do not read software; they scan it for triggers.
  • Useful: Every phrase must help the user accomplish their immediate task or recover from an impasse.
Exercise #2

Button and CTA Labeling: Verb + Specific Noun

Buttons are the primary levers of software. The most pervasive microcopy defect is using vague, generic labels like 'Submit', 'OK', or 'Proceed'.

The Specific Action Formula: Pair a strong action verb with a specific noun:

  • 'Submit' -> 'Create Organization'
  • 'OK' -> 'Save Changes'
  • 'Delete' -> 'Delete Project Permanently'

When a user scans a dialog, the button label itself should describe the consequence of clicking it without forcing them to re-read the entire body copy.

Exercise #3

Empty States: Turning Dead Ends into Onboarding

An empty state occurs when a screen has no data to display (e.g., a brand-new project board, an empty favorites list, or a clean inbox).

The 3-Part Empty State Framework:

  1. What belongs here? Briefly describe the purpose of the space ('No invoices yet').
  2. Why is it empty? Explain why nothing is showing ('When you bill clients, your sent and paid invoices will appear here').
  3. What should I do next? Provide a single, prominent primary button ('Create First Invoice').

An empty state is the prime moment of user intent; never leave it as a blank screen or a dry '0 items' label.