Clarity and Language

That invisibility is the whole craft: every word you cut or align is one less flicker of doubt between a person and the thing they came to do.

When It Matters Most

• First-time and high-friction flows — onboarding, forms, anything where a moment of confusion makes people quit.
• Everyday, repeated actions — the labels users see a hundred times; inconsistency there is a hundred tiny stumbles.
• High-stakes or regulated copy — finance, health, legal — where one vague or ambiguous word quietly costs trust.

Clear, consistent language is a small act of respect for the user's attention — and attention is the scarcest thing they have.

What This Module Covers

Two habits make words disappear: writing so they're instantly scannable — verbs first, no filler — and using one term for one thing, everywhere, so users never have to wonder. The next articles show you how.

Clear and Scannable Writing

Here's the uncomfortable truth about your carefully written interface: almost nobody reads it. People scan, skim, and guess — and the few words that survive that speed-run are the ones doing the real work. So the goal was never to write more; it's to make every word you keep earn its place.

Use Verbs, Not Nouns

Nominalized phrases slow reading and feel bureaucratic. Swap them:

• "Make a payment" → "Pay"
• "Cancellation" → "Cancel"
• "Withdrawal process" → "Withdraw"
• "Send a notification" → "Notify"

Watch for: forms of "be" as main verbs, "make" constructions, words ending in -tion/-sion/-ment/-ance/-ency, and "process" phrases. Each is a candidate for a simpler verb.

Front-Load the Verb

Picking the right verb is only half the job — its position matters just as much. People don't read interfaces, they scan them — the Nielsen Norman Group found users read only about 20–28% of the words on a page, fixating in an F-pattern on roughly the first 11 characters of a line (about the first two words). An action buried at the end of a sentence effectively doesn't exist for a scanner. Put the verb up front:

• "In order to see more details, click here" → "View plan details"
• "You can save your file by clicking here" → "Save file"

This is why warning signs read STOP and EXIT, not "Please bring your vehicle to a complete halt" — and why recipes say "Dice the onions. Heat the pan."

A front-loaded verb carries the message even at a glance. Airbnb swapped vague prompts for "Confirm dates"; Amazon uses "Place your order," not "Finalize your purchase."

Two Words, Not One

Front-loading shouldn't collapse into single-word labels. "OK," "Next," "Send," and "Submit" force users to read and remember the whole screen to know what the button does — and if they're interrupted mid-read, that context is gone. A short, descriptive label gives information scent: it tells users where the trail leads, so they can click confidently even when distracted.

• "Next" → "Set Password"
• "Send" → "Send Invoice"
• "Submit" → "Place Order"

Aim for roughly two words: enough to name the outcome, short enough to scan.

Remove Technical Jargon

Acronyms (OTP, KYC, AML) and specialized terms ("icon," "authorization," "authentication flow") that appear in internal meetings or Jira tickets are jargon for most users. Test by showing interfaces to someone outside your team. If they hesitate, the word is jargon.

Natural AI uses "OTP code" where "6-digit code" is universally understood — same meaning, zero assumed knowledge. The more complex and regulated the product, the more important it is to use the precise plain-language equivalent — legal accuracy and plain language aren't mutually exclusive.

Minimize Negations

Negations require extra cognitive processing — users must decode the negative before understanding the instruction. "Don't use special characters, spaces, or symbols" → "Use only numbers and letters."

Single negatives are particularly risky: users may miss "not" entirely and follow the opposite instruction. Negations in financial products also feel restrictive and damage trust.

Limit Politeness and Filler Words

"Please" and similar politeness markers consume limited UI space without adding meaning. Direct, clear instructions are more respectful of users' time than performative courtesy. "Enter your email" is better than "Please enter your email address below."

Microsoft's UX guide cuts "Please," "You can," and "There is" for the same reason — they delay the value before the user reaches the actual action. Prioritize clarity over formality.

Make It Work Without the Visuals

Clarity isn't only about brevity — it's about copy that still makes sense when the surrounding visuals are gone. Accessibility lives in the words as much as in contrast and screen-reader support.

• Labels that survive out of context. A screen-reader user often hears controls as a bare list. "Click here" tells them nothing; "Download invoice" tells them exactly where they are. Every interactive label should make sense on its own.
• Alt text that adds value. "Image" is wasted breath. "User profile picture — smiling in front of bookshelves" conveys what a sighted user gets at a glance. Describe what matters, not merely that an image exists.
• Concrete timing, not vague promises. "Soon" or "in a bit" disorients without an anchor. Give real timing — "within 24 hours," "in about 2 minutes" — so everyone knows what to expect.