Brand voice discussions usually stop at the logo, palette and typeface, then end on launch day. But the moments people actually remember a brand are rarely the homepage banner. They are the second a card declines, the page where a list is empty, the dialog before deleting something. The words in those places — button labels, error messages, empty states, loading text — are microcopy. It is the last mile where brand voice stops being an adjective and becomes a specification you can sign off. It is also the piece most often skipped. This is about writing it into the acceptance checklist.
Four Real Examples
- Mailchimp turned this into a public asset. Its Content Style Guide separates voice (the brand, constant) from tone (the register, situational), and maps how tone should shift when a user is succeeding, failing, waiting or disappointed. Its best-known rule: when someone has just broken something, it is not the moment for a joke.
- Shopify Polaris mechanises button copy in its content guidelines — verb first, specific over generic, never a label as information-free as "OK." In an admin interface operated dozens of times a day, the hesitation that rule removes is measurable.
- GOV.UK takes the opposite extreme. Its content design guidance targets a reading age of nine and explicitly bans abstract buttons like
Submit, requiring words that describe the actual outcome instead. It is designed for high-stress, low-tolerance, once-in-a-lifetime journeys. - Stripe writes nearly every error message in the same three-part shape: what happened, why, what you can do now. A meaningful share of developer goodwill toward Stripe is accumulated during debugging — which is precisely the peak moment of brand memory.
Why Microcopy Works: Cognitive Load, Not Wordcraft
Three foundations. First, Nielsen Norman Group's long-standing error message guidelines: state the problem clearly, explain the cause, say how to fix it. An error message missing the third part hands responsibility back to the user, and the user's usual response is to leave.
Second, concrete verb buttons lower decision cost. "Submit" makes the user re-check what they are doing; "Create account" does not. That double-take is trivial once and materially expensive across dozens of daily operations in an admin tool.
Third, the peak-end rule: overall judgement of an experience is driven by its emotional peak and its ending, not its average. On a website, the emotional peaks are almost all negative — payment failure, form errors, deletion. Spreading design effort evenly across every page puts the effort where it will not be remembered.
Technical Cost and Limits
The hard part of microcopy is not writing it — it is changing it. Three real costs:
- String externalisation: if copy is scattered across code and templates, changing one word means a full release cycle. Extracting strings into locale files or a content table runs 300 to 800 entries on a mid-sized site, about 16 to 30 hours for the first pass.
- Translation expansion: translating Traditional Chinese into English typically expands character width by 30–40%. Fixed-width buttons and toasts must reserve room, or you discover truncation in the English build after launch.
- Accessibility: button and link text is the accessible name a screen reader announces. Under WCAG link purpose requirements, "click here" is a defect, because screen reader users frequently navigate by links list, where "click here" carries zero information out of context.
- SEO: button and empty-state text is mostly not indexed, so the impact is limited. But 404 and 500 page copy — and the internal links inside it — directly affect crawl efficiency and exit rate. That page is worth writing properly.
Where It Pays Off — And Where It Doesn't
High return:
- SaaS and admin systems — high-frequency use converts microcopy directly into efficiency
- Ecommerce and subscriptions — checkout failure and refund flows are primary churn points
- Finance, insurance, medical booking — high-anxiety contexts where steady tone is itself a trust signal
- Education and online courses — empty states are the best teaching slot you own
Be conservative or skip:
- Legal documents, policy wordings, prescriptions — statutory language cannot be rewritten for tone
- Government and regulated forms — field names often have a legal basis; check before editing
- B2B specification and technical reference pages — readers want precision, not warmth
- Single-page campaign sites — the lifecycle is too short to justify building a microcopy system
How to Apply It: Five Steps
- Step 1 — Inventory the high-emotion moments. List every negative or uncertain instant on the site: payment failure, form validation errors, no search results, delete confirmations, session timeout, loads over three seconds. A mid-sized site usually has 25 to 60. That list is your scope.
- Step 2 — Quantify tone on three axes. Take formal↔friendly, restrained↔enthusiastic, and serious↔playful. Score 1–5 on each for the brand default, then add one more thing: how many notches each axis shifts when something goes wrong. For most brands the answer is "everything moves toward restrained and serious."
- Step 3 — Write 10 golden patterns and 10 banned words. A pattern such as "We couldn't [action] because [reason]. Please [specific next step]." Banned words such as "Oops," "Whoops," "System busy," "Unknown error."
- Step 4 — Build a microcopy register and externalise strings. One table with columns for page, component, state, copy, character limit, and locale key. It serves as both the design deliverable and the development string source, so neither side writes its own version.
- Step 5 — Put it in the acceptance checklist. Three objectively checkable rules: every button label starts with a verb and stays under six words; every error message contains a fix; every empty state contains one primary action button. Check them line by line, not by feel.
Common Mistakes and How to Avoid Them
- Mistake 1: humour in error messages. A quip read during anxiety lands as dismissal. Fix: reserve humour for success and empty states; errors stay restrained.
- Mistake 2: buttons labelled "OK" or "Submit." A loss on both conversion and accessibility. Fix: outcome-describing verb phrases — "Create account," "Submit refund request."
- Mistake 3: empty states that only say "No data." The moment a user is most receptive to guidance, spent on a sentence that teaches nothing. Fix: one line explaining the purpose plus one primary action button.
- Mistake 4: microcopy hard-coded in the codebase. The result is that nobody dares change it, because one word costs a release. Fix: externalise strings so marketing or support can adjust without touching code.
- Mistake 5: writing only the primary language and handing translation off. Tone calibration does not cross languages automatically. Fix: give translators the three-axis scale, and retest button widths in every language.
Further Resources
- Mailchimp Content Style Guide — Voice and Tone: the canonical emotional-state-to-tone mapping, easy to adapt into your own version.
- Shopify Polaris — Content: component-level writing rules for buttons, forms and error messages.
- GOV.UK Content Design: writing standards for high-pressure, low-tolerance journeys.
- NN/g — Error Message Guidelines: the research basis and a usable checklist.
- Atlassian Design System — Writing Style: how a large product portfolio keeps tone consistent across teams.
FAQ
Will a microcopy standard make the site boring?
It will make it consistent, which is not the same thing. Personality belongs in low-risk places — success messages, empty states, onboarding, brand story — and should contract around errors and payments. Spreading personality evenly across an entire site is what actually becomes tiring.
How many hours does this take?
For a mid-sized site: 8–12 hours for the inventory and tone scale, 16–24 hours to write 25–60 high-emotion strings, and 16–30 hours for string externalisation. Add roughly 40% per additional language.
If I can only fix three places, which three?
Payment failure messages, form validation errors, and the 404 page. Those three cover most sites' churn points, usually take under two days, and carry low change risk.
Should microcopy be A/B tested?
Only with enough traffic. Below roughly 30,000 monthly visits, microcopy differences mostly disappear into statistical noise. At that scale, following established accessibility and clarity rules — verb-led buttons, errors that contain a fix — is more reliable than running your own tests.
Want Your Brand Voice as a Signed-Off Specification?
We build microcopy standards: a three-axis tone scale, the high-emotion moment inventory, golden patterns and banned words, and three acceptance-checklist rules — plus help completing string externalisation.
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p