Brand Voice

Brand Voice — How the Brand Speaks

The verbal counterpart to visual identity. While visual identity is how the brand looks, brand voice is how it sounds in every piece of written and spoken communication.

Voice vs Tone

Voice is consistent — it's the brand's personality expressed through language. It doesn't change. Tone modulates — it's how the voice adapts to different contexts. Same personality, different situations.

Defining Voice

The Voice Attributes Framework

Define your voice with 3-4 attributes, each on a spectrum:

Format:

We are [attribute], not [opposite]. This means we [do this], not [that].

Example for a developer tools brand:

• We are precise, not verbose. We say what's needed in the fewest words.
• We are direct, not aggressive. We respect the reader's intelligence without being blunt.
• We are helpful, not patronizing. We explain when useful, not when obvious.
• We are human, not corporate. We use contractions, humor when appropriate, and first-person.

Voice from Brand Personality

The "We'd Never Say" List

Equally important to defining what you sound like is defining what you'd never say:

Tone Modulation

The Tone Matrix

Map tone across two dimensions for each content type:

Error Message Tone (Special Case)

Error messages are where brand voice is tested most. Bad error messages erode trust faster than any marketing can build it.

Framework:

1. Say what happened (not technical jargon)
2. Say why it matters (impact on the user)
3. Say what to do next (actionable step)

Messaging Framework

The Message Hierarchy

Every brand needs messages at different levels of detail:

Value Proposition Formula

For each key benefit:

[Benefit headline] — [One sentence explaining what it means for the user]. [One sentence of proof or specificity].

Example:

Ship faster without breaking things — Our CI/CD pipeline catches errors before they reach production, so your team can deploy with confidence. Teams using our platform deploy 3x more frequently with 60% fewer rollbacks.

Vocabulary Systems

Word Lists

Define preferred and avoided vocabulary:

Jargon Policy

• Internal jargon: Define it on first use, then use freely
• Industry jargon: Use only if your audience uses it daily
• Marketing jargon: Never. "Synergy," "leverage," "best-in-class" — delete on sight.
• Technical jargon: Match the audience's technical level. A developer docs site can say "API endpoint." A consumer app should say "connection."

Content Guidelines

Formatting Conventions

Writing Principles

1. Front-load value — the most important information goes first. Don't bury the lead.
2. One idea per paragraph — if a paragraph has "also" or "additionally," split it.
3. Active voice by default — "We shipped the feature" not "The feature was shipped"
4. Short sentences for clarity — under 25 words. If you need a comma, consider a period.
5. Cut ruthlessly — if removing a word doesn't change the meaning, remove it.

Anti-Patterns

• Voice guidelines nobody reads — if the guide is 40 pages, nobody follows it. Keep to 2-3 pages.
• Tone-deaf consistency — using the same enthusiastic tone in a data breach notification as a product launch
• Copycat voice — sounding like Mailchimp because they're famous for good voice. Your brand isn't Mailchimp.
• No examples — abstract guidelines ("be friendly") without concrete examples ("say X, not Y") are useless
• Voice by committee — when 6 stakeholders edit copy, the voice becomes beige. One voice owner per brand.
• Ignoring internal communications — brand voice that only applies to marketing but not support, docs, or internal comms is incomplete

Cross-Domain Connections

• Writing/sentence-craft/style-dna: Brand voice IS style-dna applied to an organization instead of an author. Both define consistent identity through measurable traits — sentence length, vocabulary range, formality level. Style-dna provides the analytical toolkit; brand-voice provides the strategic framework.