Patterns / Voice & Tone
One voice, every screen. The tone reads the room.
Every label, empty state, and error is the product talking, and the words are not a coat applied after the design; they are the design. The voice never changes. The tone bends to the moment: warm at a win, calm at a break, plain when it counts.
Every label, hint, and message is the product speaking. Content is a design material, weighed like spacing and color, not poured in last.
People scan, they do not study. Front-load the point, cut the dead words, let someone act on a glance.
The tone that matters most is the one for when something breaks. No blame, no jargon, no dead ends: name it, hand back a step.
Voice Is Constant, Tone Adapts
Voice is who the product is: one personality that never shifts. Tone is how that voice modulates for the situation, warmer at a win, quieter at a failure, plainer under pressure. Get the pair right and the product feels human without ever feeling inconsistent.
Set once, held everywhere. Redact the logo and you should still know it is us.
- Clear before clever, always.
- Human, not corporate or robotic.
- Honest, never hype.
- Plain enough for a nine-year-old.
The dial the voice turns for context. One person, spoken differently mid-win and mid-error.
- Success: brief and glad, then gone.
- Error: calm, specific, pointed at the fix.
- Destructive: slow, plain, no cheer.
- Onboarding: encouraging, never flooding.
We take the goal seriously. Wit is welcome only when it never costs a second of comprehension.
We say "you" and "we", we use contractions, we skip the ceremony. Casual is not sloppy; it is plain.
Never at the user's expense. No sarcasm in errors, no jokes where they are stuck.
Mostly matter-of-fact so the interface stays quiet. Enthusiasm is saved for real moments and spent sparingly.
Three Principles That Never Bend
They hold on every surface and in every state. When a line is hard to write, one of these three is usually being tested. Return to it and the sentence resolves.
Clarity Over Creativity
A clever line that makes someone stop to decode it has already failed. Copy exists to let a person act without thinking about the words. Write for scanning: outcome first, cut every word that does not change what they do, plain term over the impressive one. Label versus joke, the label wins.
In practice: headline the result ("Saved", not "Your changes were successfully saved"), name buttons for what they do ("Delete event", not "Confirm"), and drop filler like "please", "simply", and "in order to".
Human, Not Robotic
Machine copy hides in the passive voice and the system's point of view: "an error occurred". Human copy says "you" and "we", takes responsibility, and prefers the active voice so it is always clear who does what. It sounds like one careful person helping another.
Human does not mean chatty; warmth comes from plainness, not exclamation marks. The test: read the line aloud. If no real person would say it to another across a desk, rewrite it.
Honest, Never Hype
Every number, claim, and countdown on screen must be literally true. No inflation ("the best", "in seconds"), no manufactured urgency, no cost buried in a cheerful phrase. Honesty is completeness too: say what will happen before someone commits, above all when it spends money, shares data, or cannot be undone.
This runs straight into the ethics band below and into Patterns / Persuasion, where the line between honest persuasion and manipulation is drawn technique by technique.
Microcopy, Pattern by Pattern
The small text does the heavy lifting: labels, hints, empty states, errors, confirmations. It sits exactly where a person decides what to do, so it is the highest-leverage writing in the product. Each pattern pairs what to say with what to avoid.
A button names its own action, so the label reads as a promise of what happens next. Verb plus object beats a vague "Submit".
- Create eventNames the exact outcome of the tap.
- Delete eventA destructive action says so, plainly.
- Save changesVerb plus object; no guesswork.
- Send invitesThe user knows what leaves and to whom.
- SubmitSubmit what, to where? A form word, not an action.
- ConfirmOn a delete dialog, hides the consequence.
- OKAgrees to nothing in particular.
- Click hereDescribes the mechanic, not the result.
A label says what the field is; a hint removes doubt before the user types. Keep both short, and put help next to the field, not in a distant tooltip.
- Work emailSpecific enough to prevent the wrong entry.
- Doors open atPlain label paired with an example time.
- We will only use this to send your tickets.Answers the unspoken "why do you need it?".
- Email *Which email, and why? The asterisk is not an answer.
- TimeOf what? Ambiguous on a busy form.
- Enter valid inputTells the user nothing they can act on.
An empty state is not a dead end; it is the first step. Say what will be here, then hand over the one action that fills it.
- No events yet. Create your first one to get started.Names the state, offers the next step.
- Nothing matches "jazz". Try a broader search.Explains the blank and suggests a fix.
- Your story starts now.Evocative, but tells the user nothing to do.
- No results found.A dead end with no way forward.
An error line has one job: get the user unstuck. Say what happened in their words, drop the blame and the codes, point at the fix.
- That email is missing an @. Check and try again.Names the problem and the exact fix.
- This card was declined. Try another card or contact your bank.Says what happened and two ways forward.
- Invalid input.Which input, invalid how, fixed how? Nothing to act on.
- Error 402: transaction failed.A code and blame, no path out.
Confirm in the fewest words that close the loop. State what happened and, if there is one, the next thing the user might want. Then get out of the way.
- Event created. It is now visible to your audience.Confirms and states the consequence.
- Invites sent to 12 people.Specific, verifiable, done.
- Success!Success at what? The exclamation carries no information.
- Your request has been processed.Robotic, and vague about what happened.
Tone by Context
One voice, four registers. The words stay plain throughout; only the temperature changes. The register is set by how the user feels arriving, not how the team feels shipping.
Acknowledge the win, name the result, step aside. A little warmth is earned; a paragraph is not. Confirm, do not celebrate at length.
Stay level. No exclamation, no blame, no code. Name what happened, give the next step. The tone that reassures is a clear path out.
Slow the user with facts, not fear. State the real consequence and label the button "Delete event", not "Confirm". Never cheerful, never coy.
One step at a time, honest about effort, generous with progress. Invite; do not flood.
Writing Errors People Can Act On
Error copy is tested hardest, because the reader is already stuck. A good message answers three questions in the user's words: what happened, why (if it helps), and how to fix it. Everything else, blame, apology theatre, codes, jargon, is noise to wade through.
Name the problem in plain words, from the user's side. "This card was declined", not "Gateway returned 402".
Add a reason only when it guides the fix. "The file is over the 10 MB limit" earns its place; a stack trace does not.
Hand back a next step, ideally more than one. "Try another card or contact your bank." Never leave the user at a wall.
This email is missing an @. It should look like name@example.com.
The field, the error border, and the var(--color-error) token live in Patterns / Form Elements. Voice owns the words, Form Elements owns the field; written well, the user cannot tell where one ends.
Copy Has Ethics
Words persuade, so words can manipulate. The same sentence that helps a person decide can be twisted to trap them. This system draws the line in the copy itself: no dark patterns, no false urgency, no shame. A phrase that only works because the user is rushed, confused, or embarrassed is banned, not discouraged. The technique-by-technique treatment is in Patterns / Persuasion; the language rules are here.
No invented countdowns, no "only 2 left" the data cannot back, no fake "selling fast". Urgency is stated only when it is literally true.
The decline option is neutral. "No thanks" is a valid answer, never "No, I like paying full price". Guilt is not a button label.
Every charge, fee, and commitment is named before the user agrees, in the same breath as the benefit. No cost buried in cheerful phrasing.
Copy never works by being missed. If a line only lands because the user did not read it closely, it is manipulation and it is out.
Rules of the Voice
Each rule stands on its own as an instruction; the reason follows, so you can weigh it whenever a line resists.
RuleLead with the outcome; put the point in the first three words.
WhyPeople scan before they study, so a clever line that must be decoded has already failed.
RuleName every action button with a verb and its object.
Why"Submit", "Confirm", and "OK" hide what happens next; "Delete event" reads as a promise.
RuleWrite in the active voice and speak to the reader as "you".
WhyThe passive voice and the system's point of view sound like a machine, not a person.
RuleKeep every line plain enough to read at a glance.
WhyJargon and filler like "please", "simply", and "in order to" cost comprehension and add nothing.
RuleIn an error, say what happened and how to fix it.
Why"An error occurred" or a raw code leaves the reader stuck at a wall.
RuleMatch the register to the reader's moment, not the team's.
WhyCheer on a destructive step, or a buried consequence, breaks trust exactly where it counts.
RuleKeep every number and claim literally true.
WhyInvented urgency, a shamed decline, or a hidden cost is manipulation, and it stays out.
Before You Ship a Line
Sources
- Mailchimp Content Style Guide, "Voice and Tone". The canonical distinction: one voice, many tones; the voice stays the same, the tone changes with context.
styleguide.mailchimp.com/voice-and-tone - Nielsen Norman Group, "The Four Dimensions of Tone of Voice". Product tone measured on four independent scales: funny to serious, formal to casual, respectful to irreverent, enthusiastic to matter-of-fact.
nngroup.com/articles/tone-of-voice-dimensions - Nielsen Norman Group, reading behavior. "How Users Read on the Web" (79 percent of users always scan, 16 percent read word by word) and "Concise, SCANNABLE, and Objective" (concise, front-loaded copy up to 124 percent more usable).
nngroup.com/articles/how-users-read-on-the-web·nngroup.com/articles/concise-scannable-and-objective-how-to-write-for-the-web - Nielsen Norman Group, microcopy and errors. "The 3 Cs of Microcopy" (clarity, concision, character) and "Error-Message Guidelines" (polite, precise, constructive, blame-free, placed in context).
nngroup.com/articles/3-cs-microcopy·nngroup.com/articles/error-message-guidelines - Nielsen, "10 Usability Heuristics" (H9). Help users recognize, diagnose, and recover from errors: plain language, precise, constructive.
nngroup.com/articles/ten-usability-heuristics - GOV.UK writing standards. Write in plain English for everyone, front-load content, active voice, conversational tone; the reading-age-of-9 target runs across the UK government design ecosystem.
guidance.publishing.service.gov.uk/writing-to-gov-uk-standards·design.homeoffice.gov.uk/accessibility/written-content/readability - U.S. plain language guidance (formerly plainlanguage.gov). Write for your audience, use simple words, active voice, personal pronouns; the basis of the Plain Writing Act.
digital.gov/guides/plain-language - Shopify Polaris, content guidelines. Product voice and tone, actionable and accurate language, and ready patterns for buttons, banners, and empty states.
polaris.shopify.com/content - Deceptive patterns. Brignull's deceptive.design catalogue and NN/g's "Deceptive Patterns" name the harms this system's copy ethics prohibit: false urgency, confirmshaming, hidden cost.
deceptive.design·nngroup.com/articles/deceptive-patterns - Note Exact article URLs may shift as these sites are reorganized; each landing page above resolves to the current version. The four-dial positions chosen for our voice, and the framing of copy ethics as hard prohibitions rather than guidance, are house doctrine, not claims made by the cited authors.