What are the Dimensions of Tone of Voice in UX Writing

The Four Dimensions of Tone of Voice in UX Writing

In literature, tone of voice refers to the author’s feelings towards the subject, expressed through writing. In UX, every scrap of writing on a page – from body copy to button labels – contributes to the tone we use to speak to our users.

Despite its importance, advice about tone tends to be vague: “Be consistent. Be authentic. Be unique.” So we created a manageable, UX‑specific tool: four primary tone‑of‑voice dimensions.

The Four Dimensions

1. Funny vs. Serious – Is the writer trying to be humorous? (Note: trying doesn’t mean succeeding. Jokes can miss.)

2. Formal vs. Informal / Casual – Does the writing use contractions? Slang? Full sentences?

3. Respectful vs. Irreverent – Irreverent tones often aim to set a brand apart, not offend the reader.

4. Enthusiastic vs. Dry / Matter‑of‑fact – Is the writer excited about the product? Or purely neutral?

Same Message, Four Different Tones

Let’s apply these dimensions to a simple error message:
“An error has occurred.”

Version 1 – Serious, Formal, Respectful, Matter of fact

“We apologize, but we are experiencing a problem.”
No humor, no strong emotion. Traditional and straightforward.

Version 2 – Still Serious & Matter of fact, but More Casual

“Sorry, we’re experiencing a problem on our end.”
Changed “we are” to “we’re”, “apologize” to “sorry”, added “on our end”.

Version 3 – Casual + Enthusiastic (emotion, not excitement)

“Oops! We’re sorry, but we’re experiencing a problem on our end.”
“Oops” adds emotion – appropriate for a negative subject.

Version 4 – Humorous + Irreverent

“What did you do!? You broke it!”
Playful, but risky.

How do you choose your position?

Pick one position per dimension and write it down with examples, not adjectives. “Casual” is a debate. Two sample messages — one in, one out — is a decision.

Then stress-test against your three most sensitive screens: the payment failure, the account problem, the irreversible action. If your chosen tone sounds absurd on any of them, note the flex explicitly: “enthusiastic everywhere except transactional states, where we go matter-of-fact.” A tone that can’t survive your worst screen was never chosen.

Which Tone Works Best?

That depends on:

• Your brand personality

• Your users

• The context (e.g., frequency of the error)

If users are already frustrated or see the error often, a humorous tone might be irritating.

The best way to know? Test.

“The way we communicate with our users is just as important as what we’re communicating.”

How does this change for Arabic-English products?

This is where Gulf products most often get it wrong. Tone is defined in English, then the Arabic is produced by translation — and tone doesn’t survive translation, because it lives in word choice, register, and phrasing habits that differ between the languages.

Warmth in Egyptian Arabic is built from different devices than warmth in English: different directness, different levels of religious or formal phrasing, different tolerance for playfulness in transactional contexts. A playful English error message translated literally into Arabic often reads as childish or dismissive. The solution is to define the four dimensions once, then write the expression of them natively in each language — same position, different words.

How do you keep tone consistent as the team grows?

The same way you keep design consistent: a small set of decided examples that people can pattern-match against. For each of your core message types — error, success, empty state, confirmation, notification — write one approved example in each language. Ten examples cover 90% of what anyone will ever need to write, and they end the “this doesn’t sound like us” debates, because now there’s something to point at.

Voice and microcopy are a measurable part of your product, not decoration — we treat them that way in our content writing work. Let’s define your product’s voice →