Skip to main content
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

Voice

Consistent brand personalityThe unchanging character of your product. Defined once and applied everywhere.

Tone

Adaptive to contextHow voice shifts based on user situation and emotional state.

Establishing voice

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

Voice framework components

1

Define 3-5 brand concepts

Core principles or values that guide your productExamples:
  • Helpful
  • Trustworthy
  • Efficient
  • Innovative
  • Human
2

Add voice characteristics

Descriptive adjectives for each conceptExample for “Helpful”:
  • Clear
  • Guiding
  • Supportive
  • Not condescending
3

Create do/don't examples

Concrete examples showing voice in actionExample for “Helpful”:
  • Do: “We’ll guide you through it”
  • Don’t: “It’s easy, just follow the steps”
See the voice chart template in the UX Writing Skill references folder for a complete framework.

Example voice framework

ConceptCharacteristicsDo sayDon’t say
HelpfulClear, guiding, supportive”We’ll guide you through it""It’s easy” (minimizes user struggle)
TrustworthyTransparent, honest, secure”This will take about 5 minutes""This will be quick” (vague)
EfficientDirect, 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

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.
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.
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.
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.

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:
Payment failed. Your card was declined. Try a different payment method.

Confused

When: First use, complex features Tone approach:
  • Patient and explanatory
  • Break down steps clearly
  • Provide context and guidance
Example:
Connect your bank to see spending insights. We'll guide you through it.

Confident

When: Routine tasks, return visits Tone approach:
  • Efficient and direct
  • Minimal explanation
  • Quick confirmation
Example:
Saved

Cautious

When: High-stakes actions, data loss Tone approach:
  • Serious and transparent
  • Clear consequences
  • Respectful of user’s decision
Example:
Delete account? You'll lose all data and this can't be undone.

Successful

When: Completions, achievements Tone approach:
  • Positive and encouraging
  • Proportional to achievement
  • Brief celebration
Example:
Profile updated. Your changes are live.
Keep celebrations proportional. Overly enthusiastic messages for small actions feel disingenuous.

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

Does this match our voice while adapting to context?
Is the tone appropriate for the user’s emotional state?
Does the tone match the stakes of the action?
Would this feel natural coming from our product?
Is celebration/enthusiasm proportional to the achievement?
Avoid drastic tone shifts between screens. Users should feel like they’re using the same product throughout their journey.