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
Define 3-5 brand concepts
Core principles or values that guide your productExamples:
- Helpful
- Trustworthy
- Efficient
- Innovative
- Human
Add voice characteristics
Descriptive adjectives for each conceptExample for “Helpful”:
- Clear
- Guiding
- Supportive
- Not condescending
See the voice chart template in the UX Writing Skill references folder for a complete framework.
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
Purpose
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)
Context
Context
What is the user trying to do?
- Learning (first-time use)
- Completing task (routine action)
- Recovering from error (troubleshooting)
- Making decision (choosing option)
Emotional state
Emotional state
How does the user likely feel?
- Frustrated (errors, blockers)
- Confused (complex features)
- Confident (routine tasks)
- Cautious (high-stakes actions)
- Successful (completions)
Stakes
Stakes
What’s the impact of this action?
- Low (changing theme color)
- Medium (updating profile)
- High (deleting account, financial transaction)
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
Confused
When: First use, complex features Tone approach:- Patient and explanatory
- Break down steps clearly
- Provide context and guidance
Confident
When: Routine tasks, return visits Tone approach:- Efficient and direct
- Minimal explanation
- Quick confirmation
Cautious
When: High-stakes actions, data loss Tone approach:- Serious and transparent
- Clear consequences
- Respectful of user’s decision
Successful
When: Completions, achievements Tone approach:- Positive and encouraging
- Proportional to achievement
- Brief celebration
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
Success messages
Tone: Positive, specific, encouraging Approach:- Confirm what happened
- Proportional to action importance
- Brief and clear
Instructions
Tone: Clear, direct, helpful Approach:- Front-load key action
- Explain why when needed
- Use simple steps
Onboarding
Tone: Inviting, encouraging, concise Approach:- Welcome without overwhelming
- Focus on value
- Celebrate early wins
Confirmations
Tone: Serious, transparent, respectful Approach:- Clear about consequences
- No manipulation
- Easy to back out
Empty states
Tone: Hopeful, actionable, guiding Approach:- Explain why it’s empty
- Provide clear next action
- Keep encouraging tone
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?