Brand Voice Guide: A Tone System for Product Websites

A product website should sound like one organisation without sounding identical in every situation. The welcoming language on a homepage may be inappropriate beside a failed payment. A useful voice system defines what stays consistent and what changes when the user's circumstances change.

Separate stable voice from situational tone

Voice is the recognisable character of the organisation's writing. Tone is how that character responds to a particular situation. A brand can stay direct and considerate while becoming more restrained during an outage or more encouraging when someone finishes setup.

Collect a homepage paragraph, signup explanation, validation message and billing notice. Use the word counter to compare length and sentence patterns after editing. It helps expose unnecessary words, but a short sentence can still be confusing, insensitive or misleading. Judge the message by what the reader understands and can do next.

Write one practical purpose for the system: help small teams understand and trust our scheduling product, for example. This creates a better decision standard than sound friendly. When a joke obscures a deadline, clarity should win even if the joke feels on brand.

Keep the system small enough to use during ordinary production. A two-page reference with real examples often helps writers more than a long manifesto about personality.

Translate personality into observable choices

Choose three or four voice principles, each paired with an observable rule and a boundary. Clear might mean naming the action before explaining the benefit. Considerate might mean avoiding blame when a task fails. Confident might mean making specific claims without unsupported superlatives.

For example, helpful but not overfamiliar permits a short explanation and a useful next step. It excludes pet names, forced banter and assumptions about the reader's mood. Expert but not academic permits accurate terminology when needed, followed by a definition where the audience may not know it.

Build paired examples around the same meaning. Replace unlock unparalleled productivity with schedule a team meeting without another message thread. Replace oops, you messed that up with enter a work email address. The improvements are concrete enough for another writer to repeat.

The Nielsen Norman Group voice dimensions offer a vocabulary for discussing formality, respectfulness, enthusiasm and humour. Use dimensions to make disagreements explicit rather than turning them into arbitrary scores. A serious security product may still be warm; it need not sound bureaucratic to sound trustworthy.

Connect the principles to the existing landing page copywriting guidance, but keep the distinction clear: a persuasive structure organises the argument, while brand voice determines how that argument sounds.

Map tone to user circumstances

Create a tone map based on stakes, urgency and user control. A low-stakes feature announcement can show enthusiasm. A destructive action needs precision. A security incident needs restraint, verified facts and practical next steps. The same exclamation mark will not suit all three.

For a successful import, try: Your contacts are ready. Review the list before sending invitations. For a partial failure, try: We imported 84 contacts. Download the 6 rows that need attention. For a complete failure, try: We could not import this file. Check that it is a CSV and try again.

These examples keep the organisation calm without pretending that a problem is delightful. They also avoid blaming the user when the cause is uncertain. Emotional restraint is especially important around money, lost work, exclusion and safety.

For billing, state amount, timing and available action. Your subscription renews on 12 June is more useful than don't miss out on another amazing month. If a charge failed, explain whether access continues and when another attempt will occur, but only if those facts are verified by the product team.

Review Mailchimp's voice and tone guidance as an example of separating character from circumstance. Borrow the method, not its personality: another company's humour or informality may contradict your audience's expectations.

Build terminology and message patterns

Maintain a small terminology list for objects, actions and account states. If a saved item is a workspace, do not call it a project in the help centre and a team in the upgrade flow unless those are genuinely different objects. Familiarity grows through repeated accurate labels.

Record preferred terms, terms to avoid and definitions. Include exact capitalisation for the product name and whether interface labels use sentence case. Specify common message patterns so contributors do not reinvent the structure for every screen.

A failure message can follow three parts: what happened, what remains safe or unchanged, and what the person can do. Do not force all three into every message; sometimes the middle part is irrelevant. The pattern supports judgment rather than replacing it.

Action labels should describe the result. Save changes, send invitation and delete workspace are clearer than generic yes or continue when the consequence matters. Where a destructive action is involved, mention the affected object and explain recovery honestly.

Use GOV.UK's writing guidance as a reference for plain language. Plain language does not erase identity. It removes avoidable decoding work so that the product's useful distinctions can carry the personality.

Review copy as part of the brand system

Assign a writing owner and include copy in design review before layouts become fixed. Late editing often leaves teams choosing between an unclear label and a broken button. Review the actual screen, not just a spreadsheet, because surrounding content can change the meaning of a sentence.

A lightweight review asks whether the facts are correct, the next action is obvious, terminology is consistent and the tone matches the stakes. Then check whether the text sounds like the organisation. Truth before personality is a useful ordering rule: a charming but inaccurate promise still damages trust.

Include localisation notes for humour, metaphors and ambiguous labels. English brevity should not require translations to fit an unrealistically narrow space. Give translators the purpose, screen context and any constraints rather than an isolated string with a character limit.

Store approved patterns beside your design system documentation, and use branding resources for the broader identity context. Revisit the system after support complaints or product changes reveal recurring misunderstandings. Measure comprehension and task completion where possible, not whether colleagues like the prose. A voice guide succeeds when different contributors can produce trustworthy, recognisable messages without asking the original author to rewrite every line.

Key takeaways

• Keep voice consistent while adapting tone to context and stakes.
• Turn personality adjectives into specific writing rules and boundaries.
• Establish shared terminology and reusable message patterns.
• Prioritise accurate facts and clear actions over clever language.
• Review copy in context and update guidance from real misunderstandings.