Voice and Tone
Date: 2026-08-17
Voice is constant; tone varies by situation. The distinction is the whole practical value — a brand voice applied at a fixed pitch through a failed payment is why “brand personality” gets a bad name.
Voice is a brand’s consistent character in language — what it always sounds like. Tone is the modulation of that voice for a specific context and emotional state.
VOICE who you are
→ constant
→ "clear, expert, warm,
never patronising"
TONE how you sound right now
→ varies
→ warm when confirming an order
→ plain and direct when payment
fails
A person analogy makes it obvious. You have one personality and you don’t speak at a funeral the way you speak at a party. Voice is the personality; tone is reading the room.
Defining voice usefully
Adjectives alone are useless — everyone claims “friendly, professional, helpful”. Define by contrast:
| We are | But not |
|---|---|
| Expert | Academic |
| Warm | Matey |
| Direct | Blunt |
| Confident | Boastful |
| Plain | Simplistic |
The right-hand column is what makes it operable. “Warm but not matey” tells a writer to reject “Hey you! 👋” in a way “friendly” never will.
Show examples, especially rejected ones:
✓ "We couldn't take payment. Your
card wasn't charged."
✗ "Uh oh! Something went wrong 😬"
✗ "Payment authorisation was
unsuccessful."
Tone varies with emotional state
The framework worth having, because it maps directly to interface moments:
USER STATE TONE
browsing, more personality
relaxed permitted
deciding, plain, informative,
comparing confident
committing reassuring, precise
(checkout) → minimal personality
something plain, direct,
went wrong apologetic, useful
→ NO personality
waiting informative, calm
succeeded warm — this is where
personality belongs
— Peak-End Rule
See: Peak-End Rule
Stress narrows tolerance for tone. The same phrasing reading as friendly on a category page reads as flippant when a payment has failed, and the failure is worse than being bland would have been.
Where personality is a liability
PAYMENT ERRORS none
STOCK PROBLEMS none
DELIVERY DELAYS none
ACCOUNT / SECURITY none
ACCESSIBILITY literal language
CONTENT → Cognitive Accessibility
LEGAL / POLICY plain, not casual
Humour costs comprehension, and the cost is highest exactly where clarity matters most. Idiom and jokes are also disproportionately hard for non-native speakers and for some autistic users — Readability.
Where personality earns its place
EMPTY STATES — Empty States
CONFIRMATIONS and thank-you pages
PACKAGING INSERTS
LIFECYCLE EMAILS
404 PAGES
ONBOARDING
See: Empty States
These share a property: nothing is at stake. The person isn’t blocked, isn’t paying, isn’t anxious — which is what makes room for character.
Consistency across channels
Voice must survive the channel change, and this is where it usually fails:
SITE designed, reviewed
EMAIL often a different team
SMS often a platform default
PACKING SLIP often the warehouse system
SUPPORT REPLIES often individual style
COURIER PAGE not yours at all
The packing slip and the transactional email are where voice most often collapses, because they’re generated by systems nobody in marketing looks at — and they arrive at the emotional peak of the experience — Journey Mapping.
Making it usable
A voice document nobody reads changes nothing. What works:
ONE PAGE, not twenty
CONTRASTS, not adjectives
EXAMPLES, including rejected ones
A WORD LIST
say "delivery" not "P&P"
say "basket" not "cart"
— Taxonomy and Labelling
TONE BY SITUATION
a short table, as above
IN THE DESIGN SYSTEM
next to the components
— Component Documentation
See: Taxonomy and Labelling · Component Documentation
Putting the guidance next to the component is what makes it get used, because that’s where someone is when they need to write a label — Microcopy.