> ## Documentation Index
> Fetch the complete documentation index at: https://content-designer-ux-writing-skill-26.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Voice and tone

> How to establish consistent brand voice and adapt tone based on user context and emotional state.

Voice and tone work together to create a cohesive user experience. Voice is your product's consistent personality, while tone adapts to context and user emotions.

## Voice vs tone

<CardGroup cols={2}>
  <Card title="Voice" icon="fingerprint">
    **Consistent brand personality**

    The unchanging character of your product. Defined once and applied everywhere.
  </Card>

  <Card title="Tone" icon="masks-theater">
    **Adaptive to context**

    How voice shifts based on user situation and emotional state.
  </Card>
</CardGroup>

## Establishing voice

Voice is the consistent personality of your product. Create a voice framework using:

### Voice framework components

<Steps>
  <Step title="Define 3-5 brand concepts">
    Core principles or values that guide your product

    **Examples:**

    * Helpful
    * Trustworthy
    * Efficient
    * Innovative
    * Human
  </Step>

  <Step title="Add voice characteristics">
    Descriptive adjectives for each concept

    **Example for "Helpful":**

    * Clear
    * Guiding
    * Supportive
    * Not condescending
  </Step>

  <Step title="Create do/don't examples">
    Concrete examples showing voice in action

    **Example for "Helpful":**

    * **Do:** "We'll guide you through it"
    * **Don't:** "It's easy, just follow the steps"
  </Step>
</Steps>

<Note>
  See the voice chart template in the UX Writing Skill references folder for a complete framework.
</Note>

### Example voice framework

| Concept     | Characteristics                 | Do say                           | Don't say                                        |
| ----------- | ------------------------------- | -------------------------------- | ------------------------------------------------ |
| Helpful     | Clear, guiding, supportive      | "We'll guide you through it"     | "It's easy" (minimizes user struggle)            |
| Trustworthy | Transparent, honest, secure     | "This will take about 5 minutes" | "This will be quick" (vague)                     |
| Efficient   | Direct, concise, action-focused | "Save changes"                   | "Would you like to save?" (unnecessary question) |

## Adapting tone

While voice remains constant, tone shifts based on four variables:

### Tone variables

<Accordion title="Purpose">
  **Why is the user seeing this text?**

  * Information (learning about a feature)
  * Action (completing a task)
  * Confirmation (verifying a choice)
  * Recovery (fixing an error)

  Informational content can be more conversational. High-stakes confirmations should be serious and direct.
</Accordion>

<Accordion title="Context">
  **What is the user trying to do?**

  * Learning (first-time use)
  * Completing task (routine action)
  * Recovering from error (troubleshooting)
  * Making decision (choosing option)

  First-time users need more explanation. Return users want efficiency.
</Accordion>

<Accordion title="Emotional state">
  **How does the user likely feel?**

  * Frustrated (errors, blockers)
  * Confused (complex features)
  * Confident (routine tasks)
  * Cautious (high-stakes actions)
  * Successful (completions)

  Match tone to emotion. Be empathetic during errors, encouraging during success.
</Accordion>

<Accordion title="Stakes">
  **What's the impact of this action?**

  * Low (changing theme color)
  * Medium (updating profile)
  * High (deleting account, financial transaction)

  High-stakes actions require serious, transparent tone. Low-stakes can be lighter.
</Accordion>

## Tone by emotional state

Adapt your tone based on the user's likely emotional state:

### Frustrated

**When:** Errors, failures, blockers

**Tone approach:**

* Empathetic and solution-focused
* Acknowledge the problem without blame
* Provide clear recovery path

**Example:**

<CodeGroup>
  ```text Good theme={null}
  Payment failed. Your card was declined. Try a different payment method.
  ```

  ```text Poor theme={null}
  Error: Invalid payment information. Please correct and resubmit.
  ```
</CodeGroup>

### Confused

**When:** First use, complex features

**Tone approach:**

* Patient and explanatory
* Break down steps clearly
* Provide context and guidance

**Example:**

<CodeGroup>
  ```text Good theme={null}
  Connect your bank to see spending insights. We'll guide you through it.
  ```

  ```text Poor theme={null}
  Bank connection required. Complete setup to continue.
  ```
</CodeGroup>

### Confident

**When:** Routine tasks, return visits

**Tone approach:**

* Efficient and direct
* Minimal explanation
* Quick confirmation

**Example:**

<CodeGroup>
  ```text Good theme={null}
  Saved
  ```

  ```text Poor theme={null}
  Great! Your changes have been successfully saved to the database.
  ```
</CodeGroup>

### Cautious

**When:** High-stakes actions, data loss

**Tone approach:**

* Serious and transparent
* Clear consequences
* Respectful of user's decision

**Example:**

<CodeGroup>
  ```text Good theme={null}
  Delete account? You'll lose all data and this can't be undone.
  ```

  ```text Poor theme={null}
  Are you sure you want to delete your account?
  ```
</CodeGroup>

### Successful

**When:** Completions, achievements

**Tone approach:**

* Positive and encouraging
* Proportional to achievement
* Brief celebration

**Example:**

<CodeGroup>
  ```text Good theme={null}
  Profile updated. Your changes are live.
  ```

  ```text Poor theme={null}
  Congratulations! You have successfully updated your profile!
  ```
</CodeGroup>

<Tip>
  Keep celebrations proportional. Overly enthusiastic messages for small actions feel disingenuous.
</Tip>

## Tone by content type

Different UI elements require different tones:

### Error messages

**Tone:** Empathetic, reassuring, solution-focused

**Approach:**

* Never blame user
* Explain what happened
* Provide clear next step

**Example:** "Payment failed. Your card was declined. Try a different payment method."

### Success messages

**Tone:** Positive, specific, encouraging

**Approach:**

* Confirm what happened
* Proportional to action importance
* Brief and clear

**Example:** "Profile updated. Your changes are live."

### Instructions

**Tone:** Clear, direct, helpful

**Approach:**

* Front-load key action
* Explain why when needed
* Use simple steps

**Example:** "Choose a password with at least 8 characters to keep your account secure."

### Onboarding

**Tone:** Inviting, encouraging, concise

**Approach:**

* Welcome without overwhelming
* Focus on value
* Celebrate early wins

**Example:** "Connect your bank to see spending insights. We'll guide you through it."

### Confirmations

**Tone:** Serious, transparent, respectful

**Approach:**

* Clear about consequences
* No manipulation
* Easy to back out

**Example:** "Delete account? You'll lose all data and this can't be undone."

### Empty states

**Tone:** Hopeful, actionable, guiding

**Approach:**

* Explain why it's empty
* Provide clear next action
* Keep encouraging tone

**Example:** "No messages yet. Start a conversation to connect with your team."

## Tone consistency checklist

<Check>Does this match our voice while adapting to context?</Check>
<Check>Is the tone appropriate for the user's emotional state?</Check>
<Check>Does the tone match the stakes of the action?</Check>
<Check>Would this feel natural coming from our product?</Check>
<Check>Is celebration/enthusiasm proportional to the achievement?</Check>

<Warning>
  Avoid drastic tone shifts between screens. Users should feel like they're using the same product throughout their journey.
</Warning>