esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Tone of Voice: How Your Product Sounds on Every Screen

Learn what tone of voice means in a design system, how to define it with traits and examples, and how to test and document it.

In short

Tone of voice is how your product sounds on every screen, and a design system defines it with traits and examples, then tests and documents it.

14 min readFree

What You Will Learn

This lesson explains tone of voice as it works inside a design system. You will learn what the term means, why a shared system needs it, how to write a short definition of your product's tone, and how to check whether a sentence matches that definition. The words on a screen are part of the design, just as much as colors and buttons are. When one screen sounds cheerful and the next sounds cold, users feel like they have opened two different products.

Key words

Voice
The personality of a product's writing. It answers the question of who the product is, and it stays steady.
Tone
How that voice sounds in one moment. A calm tone for an error and a bright tone for a welcome message can both come from the same voice.
Design system
A shared set of parts, rules, and guides that a product team uses to build screens in a consistent way.
Trait
One personality word that describes the voice, such as clear, warm, or confident.
Microcopy
The short words on a screen, such as button labels, hints, and messages. Detailed rules for it are taught in a separate lesson.
Active voice
A sentence where the subject does the action, such as 'We saved your file.' The opposite is passive voice: 'Your file was saved.'
Error message
The text that tells a user something went wrong and what to do next.

Why Does a Design System Need a Tone?

A design system is used by many people: designers, writers, and developers across several product teams. Without a shared tone, each person writes in their own style. One team sounds formal, another sounds jokey, and a third sounds like a manual. Users notice these gaps, even when they cannot name them. A defined tone gives everyone the same starting point. It is one of the main ways a design system makes a product feel like one brand.

  • One brand sound

    The product speaks in the same way on the sign-up page, the settings page, and the help text. Users feel they are dealing with one company, not a patchwork of teams.

  • Trust builds over time

    Trust grows when a product behaves the same way again and again. A steady voice makes the product feel predictable, and predictable products feel safe to use.

  • Faster work for teams

    When the tone is written down, a new designer does not need to guess. They can check the rules and write a message that fits in minutes.

Design system guides often include voice, tone, and microcopy advice next to the visual rules. Writing down the tone early is much easier than fixing thousands of messages later.

Tip

Treat the tone as a part of the system, like a color or a button. If it is not written down and shared, it will drift.

How Are Voice and Tone Different?

Many new writers mix up voice and tone, so it helps to split them. Voice is the fixed part. Tone is the part that moves. Product-writing guides describe it as a question of who the product is, compared with how it should speak right now.

The guide also says that the way you speak should change based on how the other person feels, so a scared or upset reader needs a different tone than a happy one.

A legal notice needs a different tone from a welcome screen, but both must sound like the same product.

Tip

If you find yourself changing the product's personality, you are changing the voice. If you are only changing how calm, serious, or excited a message sounds, you are changing the tone.

How Do You Define a Tone?

A tone definition should be short enough that someone can read it in two minutes and still use it. It has three parts: a few personality traits, a 'we are / we are not' pair for each trait, and a note on how the tone changes in different situations.

Why Pick Three to Four Traits?

A trait is one word that describes how the product speaks. Each trait should be specific enough to guide a choice. Mailchimp's guide gives its voice four words: human, familiar, friendly, and straightforward. Your product might choose clear, warm, and confident, or calm, honest, and helpful.

Choose traits that rule something out. Words like 'fun' or 'great' sound nice, but they do not help a writer decide what to say in an error message. Words like 'calm' and 'direct' do help, because they tell a writer what to leave out.

Tip

Ask your team to pick the trait words without looking at a list. Then remove any word that would fit almost any product, such as 'innovative' or 'smart'.

Write We Are and We Are Not Pairs

A trait word alone can be read in many ways. The fix is a pair. The first half says what the product is. The second half names the wrong version that a writer might drift into. The pair gives a writer a clear edge to stay on.

  • Clear

    We are clear. We are not blunt or technical. We say what happened and what to do next, in short words.

  • Warm

    We are warm. We are not gushing. We speak to 'you' and show we understand the user's situation, but we do not use exclamation marks everywhere.

  • Confident

    We are confident. We are not cocky. We state facts plainly and avoid promises we cannot keep.

That gives a writer a clear rule about what to cut.

Tip

Write at least one real sentence under each pair. A pair without an example is hard to apply.

How Do You Flex the Tone by Context?

Once the traits are set, you decide how the tone shifts in each situation. Most product teams start with four common moments: success, error, onboarding, and legal. A tone guide should say what changes in each one while the voice stays the same.

  • Success

    Keep it short and positive. A small moment of celebration is fine, but the user should quickly see what was saved or completed.

  • Error

    Be calm and empathetic.

  • Onboarding

    Be encouraging and clear. New users need reassurance and one simple next step, not a long list of features.

  • Legal

    Be precise and neutral. The user needs accurate information, so the tone should be serious and plain, without slang or jokes.

Nielsen Norman Group describes four dimensions that can help you set a tone: formal or casual, funny or serious, respectful or irreverent, and enthusiastic or matter-of-fact. You place your product on each scale, then decide how far each message can move. A tone range is often better than a single point, because one product writes many kinds of messages.

The same idea appears in a good example from Product With Mustache. The voice is the constant identity, and tone answers the question of how the product should speak in this moment. A tone matrix can map product moments, such as a failed payment or a first login, against user feelings.

Tip

Write the tone for the user's emotional state, not for the writer's mood. A user who is frustrated at an error does not need a joke.

Worked Example: Rewriting a Generic Error

This example uses Mailchimp's published style guide as the model for tone. The rewritten sentences are our own samples. We did not copy them from a live Mailchimp screen. The goal is to show the method: start with a generic message, test it against a defined tone, and rewrite it.

Mailchimp's guide describes its voice as human, familiar, friendly, and straightforward. It also says the tone is usually informal, that the brand has a sense of humor, but that clarity matters more than entertainment. For this example, we will use a different target tone that is easier to test: friendly, clear, and encouraging.

  1. 1

    Start with the generic message

    Imagine a user tries to open a page they cannot see. The screen says: 'Error 403: Request failed.' The code is correct for a technical team, but most users have no idea what it means. Nielsen Norman Group advises hiding obscure codes unless they are needed for diagnosis.

  2. 2

    Test it against the three traits

    Friendly: the message does not speak to the user at all, so it fails. Clear: it does not say what was blocked or why, so it fails. Encouraging: it gives no next step, so it fails. This is a common result for generic messages, which Nielsen Norman Group describes as lacking context.

  3. 3

    Try a playful version and test it

    A writer might try: 'Whoops! That door is locked.' It is cheerful, but it is not clear about the problem, and a joke can get stale fast when a user sees the same message again. Mailchimp's own guide puts clarity above entertainment, which means the playful line fails the clear trait.

  4. 4

    Rewrite the message

    Try: 'You don't have permission to view this page. If you think you should, ask the account owner to add you. You can also go back to your dashboard.' Use short sentences, the word 'you', and no code in the main text.

  5. 5

    Check the rewrite

    Friendly: it speaks to the user directly and does not blame them. Clear: it says what is blocked and gives the reason. Encouraging: it offers two next steps. The same meaning now sounds like one consistent product.

Tip

Keep the technical code in a small detail area or a support log, not in the main sentence. The user needs the meaning, and your engineers can still find the code.

How Do You Put Tone Into Practice?

A tone is only useful when writers can apply it. The next three parts show how to turn a definition into work: write before and after examples, test each new message, and document the tone so people can use it without guessing.

Write Before and After Examples

Before and after examples make a tone easy to see. Put the first draft next to the improved version, and label which trait the change serves. Good examples are real messages from your product, not made-up sentences.

  • Formal to calm

    Before: 'Your submission was not successful.' After: 'We couldn't save your form. Check the highlighted fields and try again.' The second version is calm, names the problem, and gives a next step.

  • Formal to friendly

    Choose the one that matches your traits.

  • Excited to measured

    Before: 'Congratulations!!! You're officially in!!!' After: 'You're all set. Start by creating your first project.' One exclamation mark can be enough when the moment calls for it.

Uxcel shows how small word changes shift the feeling. 'Hey, let's talk!' and 'Listen, we need to talk' carry the same message but leave very different impressions.

Test Copy Against the Traits

Once a message is written, check it against each trait. Do not rely on a feeling that it 'sounds fine'. A short, repeatable test helps teams agree.

  1. 1

    Read it aloud

    Say the message in a normal speaking voice. If it sounds like a form letter or a joke, the tone is off.

  2. 2

    Check each trait

    Go through each trait word and ask whether the message shows it. If a trait is missing, rewrite the sentence that causes the gap.

  3. 3

    Check the 'we are not' side

    Look for the wrong version of the tone. For example, a calm message should not sound cold, and a warm message should not sound gushing.

  4. 4

    Ask real users

    Nielsen Norman Group used a simple method: ask users to rate their agreement with statements such as 'The website is friendly' and 'The website is formal'. Their answers show how the product's voice is really felt.

  5. 5

    Compare two options

    Pairwise comparison means showing two versions and asking which one fits better. Some teams also track whether users finish the task after each version.

Use them as a quick check, not as the final judge.

Tip

Test the messages that matter most first: errors, payments, and legal text. A tone mistake there costs more trust than a mistake on a settings page.

How Do You Document the Tone?

A tone is only shared if it is written down in a place people can find. A short tone page is often enough for a small team. Product With Mustache suggests five sections that most voice and tone guides need, and they make a good starting outline.

  • Brand personality

    Three to five trait words that describe the voice, with a short note on what each one means.

  • Voice principles

    What each trait means in practical writing terms, including the 'we are / we are not' pairs.

  • Tone by context

    How the tone shifts for success, errors, onboarding, legal text, and other key moments.

  • Examples

    Before and after samples for the important moments, with short notes on why each version works.

  • Owner and updates

    Who approves changes to the tone, and how new writers can ask questions.

Mailchimp also asks writers to stay consistent and follow its copy patterns. That rule matters just as much for a design system. Consistent use of a tone is what lets a shared guide work across teams.

Tip

Put examples in the guide, not only rules. Writers learn faster from a good sentence than from a long list of do's and don'ts.

Check Your Understanding: The Payment Error

Quick check

Your product's tone is 'calm and reassuring'. A user's payment has just failed. Which message fits the tone best?

Common Mistakes to Avoid

  • Jokes in the wrong place

    Humor works for some moments, but a user who arrives frustrated at an error page does not want a joke.

  • Changing the voice

    A writer who makes the product sound like a different company in each team has changed the voice, not the tone. Keep the traits fixed and adjust only the tone.

  • Traits nobody can use

    Words like 'awesome' or 'premium' do not tell a writer what to write. Pick traits with a clear we-are / we-are-not pair.

  • Rules without principles

    A list of banned words cannot cover every new message. Teams need principles that help writers make choices on their own.

Key Takeaways

Tone of voice is the way a product's written personality sounds to users. The voice stays steady across every screen, while the tone changes to fit the moment. A design system needs a written tone so that many writers and teams can make the product sound like one brand. Define three or four traits, write a we-are / we-are-not pair for each, and show how the tone flexes for success, error, onboarding, and legal text.

Then put the tone to work. Write before and after examples, test each message against the traits, and document the tone with examples so that designers and writers can apply it without guessing. The rules for specific words and patterns, such as button labels and error text, come in the next lessons.

Quick check

Your team's voice is 'clear, warm, and confident'. A designer must write a notice about how user data is stored, which is a legal message. Which version best fits the course's approach to tone?

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.