Marcus Andrey Study
Ler em português Library

Design Systems · Step 4 · 6 min read

Content and voice in the system

The words in a component are part of the component. How a design system holds a voice that stays the same and a tone that changes, content rules for buttons, errors and labels, strings stored with keys, translations and length budgets, and who owns them.

People read your interface before they look at it. A button's colour comes from a token, its padding from another, and its label from whoever was in a hurry that day. That's how one product ends up with "Submit", "Send", "OK", "Confirm" and "Done" for the same action. A design system that covers colours and not words covers the part people notice less.

What you'll be able to do after reading:

  • Explain voice and tone, and write a voice for a system in a few lines
  • Write content rules for the components people use most
  • Store strings like tokens: with keys, translations and length budgets
  • Decide who owns the words, and how they change

1. Voice stays, tone moves

Mailchimp's content style guide has the clearest version: "You have the same voice all the time, but your tone changes" (Mailchimp, Voice and tone). Atlassian's design system says the same for its interfaces: its voice is "Bold, Optimistic, Practical, with a wink", and tone "should change depending on the situation the user is in (for example, receiving an error versus successfully completing a project)" (Atlassian, Voice and tone).

NN/g gives you a way to describe tone precisely, with four dimensions: formal or casual, serious or funny, respectful or irreverent, enthusiastic or matter-of-fact (Moran, The Four Dimensions of Tone of Voice, NN/g, 2016).

Booking app · sailing cancelled

Your 09:40 sailing is cancelled

High winds at Mara Island. Your booking is safe: choose another sailing or get a full refund.

Tone: serious, calm, no jokes

Staff console · same event

09:40 Kestrel Bay → Mara Island cancelled, weather

142 passengers to rebook. Notifications sent at 08:52.

Tone: brief and factual; staff are busy

Booking app · booked

You're booked

See you at Kestrel Bay. Boarding closes 15 minutes before departure.

Tone: warm, a little brighter

Off voice: don't

Oops! Mother Nature had other plans

Error WX-409: sailing unavailable.

A joke about a ruined trip, and a code nobody can use

One voice, three tones, and one message off the voice. Harbour's voice is the same everywhere (plain, calm, useful); the tone moves with the person's situation. The staff console is terser because staff read it between tasks, not because it has another voice.

Harbour's voice is three words: plain, calm, useful. Its tone, on NN/g's dimensions: always respectful; casual in the booking app, more matter-of-fact in the console; never funny when something has gone wrong. The fourth message in the figure isn't wrong because it's casual. It's wrong because it jokes about a ruined trip and hands people a code they can't use.


2. Content rules inside components

A voice is too general to write a button. Components need rules, written in their docs next to the props. Harbour's, for the components in this step:

  • Button. A verb for the action, sentence case, two or three words: "Book crossing", "Show ticket". The GOV.UK Design System asks for the same: "Write button text in sentence case, describing the action it performs" (GOV.UK, Button). A confirmation repeats the action ("Cancel booking"), never "Yes" or "OK".
  • Text field. A label that names the thing ("Surname"), a hint for the format, no placeholder in place of either (see Accessible components).
  • Error message. What happened and how to fix it. GOV.UK: "Describe what has happened and tell them how to fix it", in plain English and positive language, and never words like "forbidden", "illegal" or "you forgot" (GOV.UK, Error message). Their label and error pairs are a good model: "How many hours do you work a week?" goes with "Enter how many hours you work a week".
  • Status badge. One or two words, a state not an opinion: "Delayed 20 min", not "Running a bit late!".
  • Empty state. What will be here, and the one action that fills it. See Interface states: empty, loading, error, success.

Each rule should come with a do and a don't from your own product. Abstract rules get agreed with and ignored.


3. Strings are system assets

KeyEnglishPortuguese (Brazil)MaxRule
ticket.action.showShow ticketVer bilhete20Starts with a verb; sentence case
ticket.status.delayedDelayed {minutes} minAtrasado {minutes} min18The number comes from the data, never typed
ticket.status.cancelledCancelledCancelado14Never shown without an action next to it
ticket.departure{time} · {duration} · {date}{time} · {duration} · {date}noneFormatted per locale: "Fri 4 Dec", "sex., 4 de dez."
ticket.error.loadWe couldn't load this ticketNão conseguimos carregar este bilhete40What happened, then what to do
dialog.cancel.confirmCancel bookingCancelar reserva20Repeats the action; never "Yes" or "OK"
The Ticket card's strings, as the system stores them. Each one has a key, its translations, a length budget the layout is tested with, and a rule. Writers change the words here, once, and every product gets them.

If a token is a named design decision, a string with a key is a named content decision. Harbour stores the words of its components and patterns like this:

  • A key that says where and what: ticket.status.delayed, not string_284.
  • The translations, written by people, reviewed in context.
  • Variables, not glued sentences. Delayed {minutes} min, with the number from the data. Gluing "Delayed" + 20 + "min" in code breaks in languages with a different word order.
  • A length budget that the layout is tested with. Short strings grow most in translation: W3C quotes IBM's figures of 200 to 300% for text up to 10 characters (W3C Internationalization, Text size in translation). That's why States and edge cases tests every component with long and translated content.
  • Formats from the locale, not typed: dates, times, prices. JavaScript's Intl.DateTimeFormat gives "Fri 4 Dec" in British English (en-GB) and "sex., 4 de dez." in Brazilian Portuguese (pt-BR) from the same date (MDN, Intl.DateTimeFormat).

The payoff is the same as with tokens: change the words once and every product gets them. When legal asks to rename "refund" to "credit", it's one change, reviewed once.


4. Who owns the words

Words in a system need an owner, just like components. In Harbour:

  • A content designer in the system team owns the voice, the component content rules and the shared strings.
  • Product teams own the words of their own screens, following the rules, and propose new shared strings like any contribution (Contribution models).
  • A style guide settles the small things: numbers, dates, abbreviations, capitals. You don't need to write one from scratch: the GOV.UK A to Z style guide is public and a good model (GOV.UK, Style guides).

Put content in the same review as design. A component isn't ready for release when its words are still "Lorem ipsum" or "Button".


5. Common mistakes

  • A voice written for marketing, with nothing for errors or empty states.
  • Jokes in errors, delays and payment problems.
  • Button labels that don't say the action: "OK", "Submit", "Yes".
  • Strings glued together in code, so translations break.
  • Layouts tested only in English.
  • Content rules that live in one person's head, or in a slide deck nobody opens.

6. Vocabulary

Term Meaning
Voice The personality of the product's words; stays the same everywhere
Tone How the voice adapts to the person's situation
Content rule A written rule for the words in a component, with examples
String A piece of interface text, stored with a key
Length budget The maximum length a layout is designed and tested for
Locale Language and region together, like pt-BR, which set formats for dates and numbers

7. Try it (no tools needed)

  1. Collect every label for the main "go forward" button in a product you know.
  2. Count the different words. Pick the one that best says what happens, and write a rule from it.
  3. Find one error message and rewrite it as what happened plus how to fix it.

Reflection questions: If your product's voice were three words, what would they be? Which screen breaks them today?


8. If you already practise

  • Add a "Content" section to every component doc page: rules, do and don't, length budgets.
  • Move shared strings out of code into a file with keys, and give writers access to it.
  • Test layouts with a pseudo-localised build (longer, accented text) before real translations arrive.
  • Include a content designer in component reviews from the first sketch.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

From components to patterns · Icons and illustration in the system · Content first · Accessible components · States and edge cases · Interface states: empty, loading, error, success · Contribution models

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close